Azure Data Lake U-SQL March 9 2017 Updates: Deprecations turn into errors, PIVOT/UNPIVOT, cross ADLS account U-SQL catalog sharing, nuget packages and more!

After mainly internal service updates after our general availability, we released several new U-SQL features in our release last week. Note that these updates are now available in all regions, including the new Europe North region.

Here are the March 9 2017 Updates for Azure Data Lake U-SQL and Developer Tooling!

The main take away is that we continue the deprecation of items that we changed during the preview phase and introduce a lot of new capabilities including PIVOT/UNPIVOT more catalog sharing and much more!

Thanks to all of you who continue to volunteer to test the new version of the more scalable file set. Please contact us if you want to try it and help us validate it or want to explore the new flexible-schema feature preview for TVF parameters.

Here is the list of topics with links to the detailed release notes:

If you want to use the above preview capabilities, please request access by contacting us.

In order to get access to the new syntactic features and new tool capabilities on your local environment, you will need to refresh your ADL Tools. Otherwise you will not be able to use them during local run and submission to the cluster will give you syntax warnings for the new language features.

You can find more details with examples in the March 9 2017 release notes (or by clicking on the items above) on our GitHub site, where you also can find our previous release notes.

Comments (2)
  1. Jon Kennerly says:

    I’m not seeing any SSIS extensions other than the “Azure Data Lake Store” source and destination DFTs. In contrast HDInsight has a few Pig, Hive execution SSIS tasks and REST APIs.


    What is the typical goto method for executing a series U-SQL jobs, either in series or asynchronously? I see sample projects show order system with a number prepended to individual U-SQL script files.

    Sorry for the duplicate, but also asked here:

    1. MRys says:

      Hi Jon to answer here too: The SSIS team is working on SSIS integration and have forwarded the user requests to them. Other alternatives are: Azure Data Factory, Powershell scripts using the Azure SDK, writing your own orchestration using one of the ADL SDKs (Python, node.js, .Net, Java).

Comments are closed.

Skip to main content