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

feat: add respective get_by_path UDFs for JSON type #4720

Merged
merged 4 commits into from
Sep 11, 2024

Conversation

CookiePieWw
Copy link
Collaborator

@CookiePieWw CookiePieWw commented Sep 10, 2024

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

#3686 #4515 #4230

What's changed and what's your intention?

Add respective get_by_path for json type. see https://github.com/datafuselabs/jsonb?tab=readme-ov-file#operators for the supported operators in the path.

Checklist

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

@CookiePieWw CookiePieWw requested a review from a team as a code owner September 10, 2024 16:43
Copy link
Contributor

coderabbitai bot commented Sep 10, 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 Sep 10, 2024
Copy link
Member

@WenyXu WenyXu left a comment

Choose a reason for hiding this comment

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

Nice work! 🤩 Rest LGTM

src/common/function/src/scalars/json/get_by_path.rs Outdated Show resolved Hide resolved
src/common/function/src/scalars/json/get_by_path.rs Outdated Show resolved Hide resolved
src/common/function/src/scalars/json/get_by_path.rs Outdated Show resolved Hide resolved
src/common/function/src/scalars/json/get_by_path.rs Outdated Show resolved Hide resolved
src/common/function/src/scalars/json/get_by_path.rs Outdated Show resolved Hide resolved
tests/cases/standalone/common/function/json.sql Outdated Show resolved Hide resolved
@WenyXu WenyXu changed the title feat: add respectiv get_by_path udf for json type feat: add respective get_by_path UDFs for JSON type Sep 10, 2024
Copy link

codecov bot commented Sep 10, 2024

Codecov Report

Attention: Patch coverage is 89.43894% with 32 lines in your changes missing coverage. Please review.

Project coverage is 84.53%. Comparing base (ff40d51) to head (b3b268a).
Report is 18 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4720      +/-   ##
==========================================
- Coverage   84.81%   84.53%   -0.29%     
==========================================
  Files        1114     1115       +1     
  Lines      200739   201197     +458     
==========================================
- Hits       170250   170072     -178     
- Misses      30489    31125     +636     

@killme2008
Copy link
Contributor

I really dislike the name "get_by_path_xxx" because it doesn't reflect any JSON-related meaning and could potentially conflict or be associated with other function names. Perhaps we could change it to "json_path_xxx"?

What do you think? @WenyXu @CookiePieWw

@WenyXu
Copy link
Member

WenyXu commented Sep 11, 2024

I really dislike the name "get_by_path_xxx" because it doesn't reflect any JSON-related meaning and could potentially conflict or be associated with other function names. Perhaps we could change it to "json_path_xxx"?

What do you think? @WenyXu @CookiePieWw

How about json_get_xxx?👀

@killme2008
Copy link
Contributor

I really dislike the name "get_by_path_xxx" because it doesn't reflect any JSON-related meaning and could potentially conflict or be associated with other function names. Perhaps we could change it to "json_path_xxx"?
What do you think? @WenyXu @CookiePieWw

How about json_get_xxx?👀

LGTM

@paomian
Copy link
Contributor

paomian commented Sep 11, 2024

LGTM, but we should add some test for this udf in the where clause in the next pr.

@WenyXu WenyXu added this pull request to the merge queue Sep 11, 2024
Merged via the queue into GreptimeTeam:main with commit 67fb3d0 Sep 11, 2024
32 checks passed
CookiePieWw added a commit to CookiePieWw/greptimedb that referenced this pull request Sep 17, 2024
* feat: add respectiv get_by_path udf for json type

* Apply review comments

Co-authored-by: Weny Xu <[email protected]>

* fix: fix compile error

* refactor: change name of UDFs, add some tests

---------

Co-authored-by: Weny Xu <[email protected]>
@github-actions github-actions bot added docs-required This change requires docs update. and removed docs-not-required This change does not impact docs. labels Sep 19, 2024
@CookiePieWw CookiePieWw deleted the get_by_path branch September 26, 2024 05:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-required This change requires docs update.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants