-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Wrong inference of azure storage table entity value type #15576
Comments
add to S178 |
@tunz I could reproduce your issue but we send the request as you provided and cosmosdb changes the type. |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage. Issue DetailsDescribe the bug If I insert an entity value "123_456.1" using To Reproduce
Expected behavior
Environment summary
Additional context looks like this might be related to #8032 .
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @wmengmsft, @MehaKaushik, @shurd, @anfeldma-ms. Issue DetailsDescribe the bug If I insert an entity value "123_456.1" using To Reproduce
Expected behavior
Environment summary
Additional context looks like this might be related to #8032 .
|
I have removed "cosmos" label. This label indicates that the issue is related to az cli cosmosdb. We are tracking these issues and since this issue is not related to cosmosdb cli, I am removing the label. |
I have the same issue but with a Guid based value which get converted as a string instead.... |
Describe the bug
If I insert an entity value "123_456.1" using
az storage entity insert
, "123456.1" is actually inserted. I think az cli infers the type, and converts it to a numeric type.To Reproduce
Expected behavior
123_456.1
should be inserted.Environment summary
Additional context
looks like this might be related to #8032 .
The text was updated successfully, but these errors were encountered: