u-sql

Will USQL support to Compress and Decompress a file.? I would like decompress a compressed file to perform some validations and once they are passed, would like to compress the data to new file. In addition, doing automatic compression on OUTPUT is on the roadmap. Please add your vote to https://feedback.azure.com/forums/327234-data-lake/suggestions/13418367-support-gzip-on-output-as-well According to the main EXTRACT article, U-SQL EXTRACT method automatically recognises the GZip format, so you don't need to do anything special. Extraction from compressed data In general, the files are passed

I am getting following error while running a USQL Activity in the pipeline in ADF: Error in Activity: {"errorId":"E_CSC_USER_SYNTAXERROR","severity":"Error","component":"CSC", "source":"USER","message":"syntax error. Final statement did not end with a semicolon","details":"at token 'txt', line 3\r\nnear the ###:\r\n**************\r\nDECLARE @in string = \"/demo/SearchLog.txt\";\nDECLARE @out string = \"/scripts/Result.txt\";\nSearchLogProcessing.txt ### \n", "description":"Invalid syntax found in the script.", "resolution":"Correct the script syntax, using expected token(s) as a guide.",

Already tried the suggested JSONPath option, but it seems the JSONExtractor only recognizes root level. In my case I have to deal with a nested json-structure, with an array as well (see example below). Any options for extracting this without multiple intermediate files? "relation": { "relationid": "123456", "name": "relation1", "addresses": { "address": [{ "addressid": "1", "street": "Street 1", "postcode": "1234 AB", "city": "City 1" }, { "addressid": "2", "street": "Street 2", "postcode": "5678 CD", "city": "City 2" }] }} SELECT relationid, addressid, street, postcode, city ? Michael Rys

In U-SQL custom code (code behind or Assemblies) can external services be called e.g. bing search or map. Thanks, Nasir This is currently not supported for the following reason: Imagine that you write a UDF or UDO (e.g., an extractor) that calls a REST endpoint of a service that is used to get a few calls per minute from the same originating IP address. But now you execute this user code in a U-SQL job that is scaled out over millions of rows, running possibly on hundreds of vertices concurrently. This is a - hopefully unintended - distributed denial of service attack against that service. And