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

fix: json_path_exists null results #4881

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

Kev1n8
Copy link
Contributor

@Kev1n8 Kev1n8 commented Oct 25, 2024

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

Closes #4865.

What's changed and what's your intention?

As explained in referred issue, the result should be null if any of the parameters is null .

Checklist

  • I have written the necessary rustdoc comments.
  • I have added the necessary unit tests and integration tests.
  • This PR requires documentation updates.

@Kev1n8 Kev1n8 requested a review from a team as a code owner October 25, 2024 07:43
Copy link
Contributor

coderabbitai bot commented Oct 25, 2024

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the docs-not-required This change does not impact docs. label Oct 25, 2024
Copy link

codecov bot commented Oct 25, 2024

Codecov Report

Attention: Patch coverage is 93.97590% with 5 lines in your changes missing coverage. Please review.

Project coverage is 83.98%. Comparing base (4e9c251) to head (e62fcd3).
Report is 34 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4881      +/-   ##
==========================================
- Coverage   84.18%   83.98%   -0.20%     
==========================================
  Files        1136     1137       +1     
  Lines      208585   210255    +1670     
==========================================
+ Hits       175597   176592     +995     
- Misses      32988    33663     +675     

@WenyXu
Copy link
Member

WenyXu commented Oct 28, 2024

Thanks @Kev1n8 ❤️

Comment on lines 73 to 74
match json.data_type() {
ConcreteDataType::Binary(_) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should use jsons.data_type() because the data type of ValueRef::Null isn't Binary. But we can match json and handle ValueRef::Binary and ValueRef::Null.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see your point, but I’m curious about how we would handle cases where some items in the array are ValueRef::Null while others are not. Or, all items' datatype are supposed to be the same?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Items in an array have the same data type. You can treat null as the same data type as other items in this array. Like None::<String>. But ValueRef itself doesn't carry the type information now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I'll update the code.

tests/cases/standalone/common/function/json/json.result Outdated Show resolved Hide resolved
@Kev1n8
Copy link
Contributor Author

Kev1n8 commented Oct 28, 2024

To be clear, I'd like to specify the expected results of all SQLs below:

SELECT json_path_exists(NULL, '$.a');
NULL

SELECT json_path_exists(parse_json('{}'), NULL);
NULL

SELECT json_path_exists(parse_json('null'), '$.a');
false

SELECT json_path_exists(parse_json('{}'), 'null');
false

Please let me know if anything is incorrect.

@WenyXu
Copy link
Member

WenyXu commented Oct 28, 2024

To be clear, I'd like to specify the expected results of all SQLs below:

SELECT json_path_exists(NULL, '$.a');
NULL

SELECT json_path_exists(parse_json('{}'), NULL);
NULL

SELECT json_path_exists(parse_json('null'), '$.a');
false

SELECT json_path_exists(parse_json('{}'), 'null');
false

Please let me know if anything is incorrect.

looks good

Comment on lines +131 to +134
// Any null args existence causes the result to be NULL.
(ConcreteDataType::Null(_), ConcreteDataType::String(_)) => results.push_nulls(size),
(ConcreteDataType::Binary(_), ConcreteDataType::Null(_)) => results.push_nulls(size),
(ConcreteDataType::Null(_), ConcreteDataType::Null(_)) => results.push_nulls(size),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to the sqlness tests, this should be the only change that needs to be done?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are 2 major changes: function signatures and datatype cases.

  1. I believe function signature changes matter for accepting null type. I've tested if, with only Exact(vec![Json, String]), system will throw error when the signature does not match.
  2. Apart from "this" change, I think the error handlers also make sense, while the original simply push a None into results when there's a parsing or casting error.

@Kev1n8
Copy link
Contributor Author

Kev1n8 commented Nov 5, 2024

Reduced some unnecessary checks. Please check out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-not-required This change does not impact docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

json_path_exists can't deal with null json
5 participants