We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is an epic to fix all of the bugs with GetJsonObject, and see if there are any more that we can find.
Issues that must be fixed (P0):
'
Issues where we could fall back to the CPU if needed:
Testing:
Review this issue to see if it can be closed in favor of #10196 :
The text was updated successfully, but these errors were encountered:
Verified the following issues successfully against unmerged PR: #10537 #10217 #10216 #10196 #10194 #9033
#10218: 3/4 pass 1/4 fail, haoyang will fix #10212: Haoyang will fix in Plugin PR
Sorry, something went wrong.
[BUG] GetJsonObject does not validate the input is JSON in the same way as Spark #10194, [BUG] GetJsonObject does not process escape sequences in returned strings or queries #10196, [BUG] GetJsonObject throws exception when json path contains a name starting with ' #10537, [BUG] GetJsonObject fails at spark unit test $.store.basket[0][*].b #10217, [BUG] GetJsonObject fails at spark unit test $.store.book[*].reader #10216, [BUG] GpuGetJsonObject does not expand escaped characters #9033
Will be fixed by PRs:
[BUG] GetJsonObject should return null for invalid query instead of throwing an exception #10212 will be fixed, @thirtiseven please double confirm.
And for [BUG] GetJsonObject does not normalize non-string output #10218, 3/4 sub-items are done, and sub-item number normalization is postphoned.
For testing [BUG] Fuzz test/stress test GetJsonObject #10226 did not plan in Release 24.04.
thirtiseven
res-life
GaryShen2008
SurajAralihalli
No branches or pull requests
This is an epic to fix all of the bugs with GetJsonObject, and see if there are any more that we can find.
Issues that must be fixed (P0):
'
#10537Issues where we could fall back to the CPU if needed:
Testing:
Review this issue to see if it can be closed in favor of #10196 :
The text was updated successfully, but these errors were encountered: