[ADLA] - Support catalog list table fragments

[idear1203]

Description

Swagger PR Links

• Azure/azure-rest-api-specs#2869
• Azure/azure-rest-api-specs#2944

Changes in 3.4.0-preview

• Azure/azure-rest-api-specs#2869
  1. There are no functional changes here just code refactor to make it more readable
• Azure/azure-rest-api-specs#2944
  1. Regenerate ADLA SDK to support list table fragments. Relevant files include:
     • CatalogOperations.cs
     • CatalogOperationsExtensions.cs
     • ICatalogOperations.cs
     • New file: USqlTableFragment.cs
  2. Add test for the included change. Relevant files include:
     • DataLakeAnalyticsManagementHelper.cs: Update script to create table fragments
     • CatalogOperationTests.cs: Add test for listing table fragments
     • Remove the following folder since they are obsolete and already has replacement now.
       • DataLakeAnalyticsCatalog.Tests.CatalogOperationTests
       • DataLakeAnalyticsCatalog.Tests.CommonTestFixture
       • DataLakeAnalyticsJob.Tests.JobOperationTests
     • Update SessionRecords
  3. Update version. Relevant files include:
     • AssemblyInfo.cs
     • changelog.md
     • DataLakeAnalyticsCustomizationHelper.cs
     • datalake-analytics_data-plane.txt
     • datalake-analytics_resource-manager.txt
     • Microsoft.Azure.Management.DataLake.Analytics.csproj

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• Please add REST spec PR link to the SDK PR
• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

General Guidelines

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

SDK Generation Guidelines

• If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
• The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

[dsgouda]

LGTM

[dsgouda]

Please run msbuild build.proj /t:build /p:Scope=SDKs\DataLake.Analytics
and commit any changes to the .props file

[dsgouda]

Not sure why this file is being updated, @idear1203 which generate.cmd was run to generate the code

[idear1203]

I use this generate.cmd: src/SDKs/DataLake.Analytics/Management.DataLake.Analytics/generate.cmd.

This file seems updating frequently.

[dsgouda]

This file is updated every time we run the code generation script to log some essential code generation details.

[dsgouda]

Please update the branch with upstream

[idear1203]

The branch has been updated with upstream as request.

[idear1203]

I have run the command msbuild build.proj /t:build /p:Scope=SDKs\DataLake.Analytics, but I cannot see any new changes.

BTW, it seems there is no such .props file under src\SDKs\DataLake.Analytics.

[dsgouda]

LGTM