Ask Learn
Preview
Please sign in to use this experience.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
In this month's refresh of the Azure Data Lake Store and Azure Data Lake Analytics portal, we've added a set of features focused on giving our users more control over their accounts.
Simple data cleanup using File Retention
Often, there is a time after which data can become stale or redundant - for example you may be generating a lot of temporary data that's only useful for testing. In a big data system, when you're dealing with a lot of data it can be hard to track when to clean up this data. The new File Expiry feature will help you clean up stale/old data you don't want to keep around anymore. When you set a File Expiration Time on a file and when that expiry date is reached, the file will automatically be deleted by the Data Lake Store service.
To do this from the Azure Portal:
Control how much compute capacity your Data Lake Analytics accounts have access to
When a new Data Lake Analytics account is created, there is a set value for the maximum number of parallelism that can be assigned to a job and the number of jobs that can run concurrently. You can now freely update these numbers yourself. We will have a follow up post with more details about this update in general. Keep an eye out for it!
To update the Parallelism and Concurrency:
Use Custom Delimiters when Previewing Files
Previously, we had supported comma, colon, space, tab, ampersand, and bar delimiters. With the many different kinds of files used in Azure Data Lake Store and Azure Storage, we've added a "Custom" delimiter options for you to define your own delimiter.
To change the delimiter on the Azure Portal:
Extending Data Lake Store super-users to manage the U-SQL Catalog ACLs
The U-SQL Catalog keeps the data it uses in Azure Data Lake Store. Previously, super-users of Azure Data Lake Store were not able to update (button would be disabled) the U-SQL Catalog's ACLs even though they have full access to where the data is stored. With this refresh, we've extended the super-user relationship to the U-SQL Catalog as well. Now, when an ADLS super-user tries to modify permission on the U-SQL Catalog, the operation will succeed.
Please sign in to use this experience.
Sign in