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(ingestion/lookml): fix for sql parsing error #11079

Merged
merged 9 commits into from
Aug 9, 2024

Conversation

sid-acryl
Copy link
Collaborator

@sid-acryl sid-acryl commented Aug 2, 2024

It has fix for error AttributeError: 'NoneType' object has no attribute 'replace'

Summary by CodeRabbit

  • New Features
    • Updated the library dependency for enhanced performance and potential new features.
  • Bug Fixes
    • Upgraded to a newer version that may address previous issues in the library.
  • Tests
    • Modified query fingerprints for improved identification and caching.
    • Adjusted SQL query references for better accuracy in test evaluations.

Copy link
Contributor

coderabbitai bot commented Aug 2, 2024

Walkthrough

The recent updates to the metadata-ingestion project include an upgrade to the acryl-sqlglot library and refinements in various test files. The setup.py now specifies the newer version 25.8.2.dev9, promising enhanced functionality. Additionally, modifications in the test files enhance SQL query clarity and accuracy, ensuring more reliable testing outcomes.

Changes

File Change Summary
.../setup.py Updated acryl-sqlglot dependency version from 25.3.1.dev3 to 25.8.2.dev9.
.../tests/unit/sql_parsing/goldens/test_bigquery_information_schema_query.json,
.../tests/unit/sql_parsing/goldens/test_merge_from_union.json
Updated query_fingerprint values and modified JSON structure for clarity and accuracy in SQL parsing.
.../tests/unit/sql_parsing/test_sqlglot_lineage.py Refined SQL query by adjusting the reference to cfp.field_path for improved context.

Poem

🐰 In the garden where code does bloom,
A new version arrives, dispelling the gloom.
With sqlglot spruced up, it hops with delight,
Bug fixes and features make everything bright.
So let’s cheer for the change, with a joyful little dance,
For progress in code gives our project a chance! 🎉


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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 ingestion PR or Issue related to the ingestion of metadata label Aug 2, 2024
@sid-acryl sid-acryl marked this pull request as ready for review August 2, 2024 12:57
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f78b6c0 and 9c7581d.

Files selected for processing (1)
  • metadata-ingestion/setup.py (1 hunks)
Additional comments not posted (1)
metadata-ingestion/setup.py (1)

102-102: Dependency Update Approved. Verify compatibility with the new version.

The version of the acryl-sqlglot library has been updated from 25.3.1.dev3 to 25.8.2.dev9. Ensure that the new version does not introduce any breaking changes or compatibility issues.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9c7581d and 2aee5f7.

Files selected for processing (2)
  • metadata-ingestion/tests/unit/sql_parsing/goldens/test_bigquery_information_schema_query.json (1 hunks)
  • metadata-ingestion/tests/unit/sql_parsing/goldens/test_merge_from_union.json (2 hunks)
Files skipped from review due to trivial changes (1)
  • metadata-ingestion/tests/unit/sql_parsing/goldens/test_bigquery_information_schema_query.json
Additional comments not posted (2)
metadata-ingestion/tests/unit/sql_parsing/goldens/test_merge_from_union.json (2)

4-4: Query fingerprint update is appropriate.

The change in query_fingerprint reflects an update to the SQL query structure, which is expected when the query changes.


15-15: Generalized statement modification is acceptable.

The change in the case of the timestamp function likely aligns with style guidelines or consistency preferences. Ensure compatibility with the SQL dialect in use, as case sensitivity can vary.

@hsheth2 hsheth2 added the merge-pending-ci A PR that has passed review and should be merged once CI is green. label Aug 9, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2aee5f7 and 1a08825.

Files selected for processing (2)
  • metadata-ingestion/tests/unit/sql_parsing/goldens/test_bigquery_information_schema_query.json (2 hunks)
  • metadata-ingestion/tests/unit/sql_parsing/test_sqlglot_lineage.py (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • metadata-ingestion/tests/unit/sql_parsing/goldens/test_bigquery_information_schema_query.json
Additional comments not posted (1)
metadata-ingestion/tests/unit/sql_parsing/test_sqlglot_lineage.py (1)

1191-1191: Verify the context and aliasing for cfp.field_path.

The change from field_path to cfp.field_path in the CASE statement should be verified to ensure it aligns with the intended data structure or aliasing. This change might affect how data_type is evaluated and could impact the test's accuracy.

Verification successful

Verification Successful: Consistent Use of cfp.field_path

The change to use cfp.field_path in the test file aligns with the source file's SQL query structure, ensuring consistency in aliasing and data structure. No issues are found with this modification.

  • The change is consistent with the usage in metadata-ingestion/src/datahub/ingestion/source/bigquery_v2/queries.py.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage and context of `cfp.field_path` in the codebase.

# Test: Search for the usage of `cfp.field_path`. Expect: Correct context and aliasing in SQL queries.
rg --type python -A 5 $'cfp.field_path'

Length of output: 69


Script:

#!/bin/bash
# Description: Verify the usage and context of `cfp.field_path` in the codebase.

# Test: Search for the usage of `cfp.field_path`. Expect: Correct context and aliasing in SQL queries.
rg -t py -A 5 $'cfp.field_path'

Length of output: 3891