Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync-Stack: Tables #33143

Merged
merged 28 commits into from
Mar 3, 2023
Merged

Sync-Stack: Tables #33143

merged 28 commits into from
Mar 3, 2023

Conversation

jairmyree
Copy link
Member

Introducing a fully synchronous implementation of the Tables synchronous clients, replacing the sync-over-asynchronous implementation.

Includes test improvements and updated code generation to fix failing live tests for both synchronous and asynchronous clients.

@jairmyree jairmyree changed the title Jairmyree/tables sync stack Sync-Stack: Tables Jan 23, 2023
@azure-sdk
Copy link
Collaborator

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-data-tables

@vcolin7
Copy link
Member

vcolin7 commented Jan 26, 2023

If I'm not mistaken, we also added a way of creating an asserting client for both our sync and async tests like in this commit. @g2vinay what's the reason for this? Is it required by all libraries that now support the new sync stack?

@vcolin7 Yes, it is required for all libs moving to sync stack integration. The asserting clients help ensure that the call stack for sync and async APIs is completely synchronous or asynchronous in nature respectively.

You'll need to add this to the PR as well then @jairmyree.

@g2vinay
Copy link
Member

g2vinay commented Jan 30, 2023

  1. Adding Asserting Client to Sync and Async Tables client setup.
  2. Run Performance tests both sync and async for this PR against last stable release version.

Copy link
Member

@vcolin7 vcolin7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have yet to review the batch operations code, but added comments for everything else :)

@vcolin7
Copy link
Member

vcolin7 commented Feb 11, 2023

I reviewed the sync submitTransactionWithResponse() code and the logic looks good to me :)

Copy link
Member

@samvaity samvaity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sync stack changes lgtm!
Left some comments for code refactoring. (can be addressed in a separate PR).
Make sure to run Live tests before merging the PR.

AzureNamedKeyCredential azureNamedKeyCredential = TableSasUtils.extractNamedKeyCredential(getHttpPipeline());

if (azureNamedKeyCredential == null) {
throw logger.logExceptionAsError(new IllegalStateException("Cannot generate a SAS token with a client that"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider putting these strings into util.Constants so they can be shared with asyn client.

@jairmyree
Copy link
Member Author

/azp run java - tables - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jairmyree
Copy link
Member Author

/azp run java - tables - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@vcolin7 vcolin7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@jairmyree jairmyree merged commit 8130060 into main Mar 3, 2023
@jairmyree jairmyree deleted the jairmyree/tables-sync-stack branch March 3, 2023 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants