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

[BUG] UpdateEntity and UpsertEntity from azure-data-tables sdk fail with TableServiceException - COSMOS DB with Table API in GOV Cloud #44308

Open
3 tasks done
shailesh91 opened this issue Feb 21, 2025 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Tables

Comments

@shailesh91
Copy link

shailesh91 commented Feb 21, 2025

Describe the bug
UpdateEntity and UpsertEntity from azure-data-tables sdk fail with TableServiceException when a call is made against COSMOS DB with Table API in GOV Cloud.

Exception or Stack Trace

com.azure.data.tables.models.TableServiceException: Status code 400, "{"odata.error":{"code":"InvalidInput","message":{"lang":"en-us","value":"One of the input values is invalid.\r\nActivityId: 0d011965-3ec8-454c-92f9-8694f1db8400, documentdb-dotnet-sdk/2.14.0 Host/64-bit MicrosoftWindowsNT/10.0.20348.0\nRequestID:0d011965-3ec8-454c-92f9-8694f1db8400\n"}}}
        at com.azure.data.tables.implementation.TableUtils.toTableServiceException(TableUtils.java:87)
        at com.azure.data.tables.implementation.TableUtils.mapThrowableToTableServiceException(TableUtils.java:99)
        at com.azure.data.tables.implementation.TableUtils.callWithOptionalTimeout(TableUtils.java:348)
        at com.azure.data.tables.implementation.TableUtils.callWithOptionalTimeout(TableUtils.java:340)
        at com.azure.data.tables.TableClient.upsertEntityWithResponse(TableClient.java:709)
        at com.esri.cosmostableapi.Main.main(Main.java:74)

To Reproduce
Steps to reproduce the behavior:

Code Snippet

TableServiceClient tableServiceClient = new TableServiceClientBuilder()
                                .connectionString(connectionString)
                                .buildClient();
TableClient tableClient = tableServiceClient.createTableIfNotExists("Tabl2");
tableClient.upsertEntity(new TableEntity("1","13"));

Expected behavior
Upsert or update to complete successfully

Screenshots
If applicable, add screenshots to help explain your problem.

Setup (please complete the following information):

  • OS: Windows
  • IDE: vscode
  • Library/Libraries: azure-data-tables:12.5.0, azure-data-tables:12.5.1
  • Java version: 17
  • App Server/Environment: Command Line

Additional context

  • UpsertEntitiyWithResponse and UpdateEntityWithResponse with TableEntityUpdateMode set to REPLACE works.

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Bug Description Added
  • Repro Steps Added
  • Setup information Added
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Tables labels Feb 21, 2025
Copy link
Contributor

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@jairmyree
Copy link
Member

@shailesh91 Thank you for reaching out. I'll look into this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Tables
Projects
None yet
Development

No branches or pull requests

2 participants