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
Incorrect result
Standalone mode, Frontend
The recently added json_path_exists behaves wrongly when json param is null. For example:
json_path_exists
SELECT json_path_exists(parse_json('null'), '$.a') SELECT json_paht_exists(parse_json('{}'),'null') OUTPUT: false false
According to JSON_PATH_MATCH, the result should be null.
Error.
macOS 15.0.1
0.9.5
No response
The text was updated successfully, but these errors were encountered:
I'm already working on it.
Sorry, something went wrong.
As discussed at here, we will keep the param non-nullable but return null when json is parse_json('null').
parse_json('null')
Successfully merging a pull request may close this issue.
What type of bug is this?
Incorrect result
What subsystems are affected?
Standalone mode, Frontend
Minimal reproduce step
The recently added
json_path_exists
behaves wrongly when json param is null.For example:
What did you expect to see?
According to JSON_PATH_MATCH, the result should be null.
What did you see instead?
Error.
What operating system did you use?
macOS 15.0.1
What version of GreptimeDB did you use?
0.9.5
Relevant log output and stack trace
No response
The text was updated successfully, but these errors were encountered: