-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Tables] Fix tables livetest #14797
[Tables] Fix tables livetest #14797
Conversation
128243f
to
ae88645
Compare
f618bc9
to
7a9c189
Compare
ac250bc
to
19acd89
Compare
sdk/tables/azure-data-tables/src/test/java/com/azure/data/tables/CosmosThrottled.java
Outdated
Show resolved
Hide resolved
718971b
to
d64917d
Compare
// Act & Assert | ||
if (mode == UpdateMode.MERGE && tableClient.getTableUrl().contains("cosmos.azure.com")) { | ||
// This scenario is currently broken when using the CosmosDB Table API | ||
StepVerifier.create(tableClient.updateEntityWithResponse(createdEntity, true, mode)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we split this into another test case and disable it? I feel it'll get lost as a comment since there is no issue or TODO tracking this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, once support is merged for multiple tests with the same name (#14801) I will separate these into two test classes, one for Cosmos and one for Storage, each with their own recordings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tracking this work in #14930
serviceClient.createTable(tableName3) | ||
).block(TIMEOUT); | ||
|
||
serviceClient.createTable(tableName).block(TIMEOUT); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason for splitting this into three sequential blocks rather than running them concurrently?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was having intermittent 429 issues with failures when using Mono.when
with multiple streams against the CosmosDB API.
d64917d
to
582c6db
Compare
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
/azp run java - tables - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
[Hub Generated] Review request for Microsoft.HybridCompute to add version preview/2021-06-10-preview (Azure#14797) * Adds base for updating Microsoft.HybridCompute from version preview/2021-05-17-preview to version 2021-06-10-preview * Updates readme * Updates API version in new specs and examples * updated the swagger * added the missing bracket * removed type object * removed PatchSettings ref * used x-ms-client-flatten * fixed an issue * added osProfile to the machineUpdateProperties * removed the extra space * fixed by npm run prettier
Fixes: #14798