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

chore(cubesql): Do not call async Node functions while planning #8793

Merged
merged 1 commit into from
Dec 3, 2024

Conversation

MazterQyou
Copy link
Member

Check List

  • Tests has been run in packages where changes made if available
  • Linter has been run for changed code
  • Tests for the changes have been added if not covered yet
  • Docs have been added / updated if required

Description of Changes Made

This PR restructures the way compiler cache works, removing the need to call async Node functions while planning, at the cost of passing around compiler_id.

@MazterQyou MazterQyou requested a review from a team as a code owner October 9, 2024 13:10
@MazterQyou MazterQyou force-pushed the cubesql/no-async-node-within-planning branch from f7b05e7 to 5118b3d Compare October 9, 2024 13:11
Copy link

vercel bot commented Oct 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

8 Skipped Deployments
Name Status Preview Comments Updated (UTC)
examples-angular-dashboard ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 5:16pm
examples-react-d3 ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 5:16pm
examples-react-dashboard ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 5:16pm
examples-react-data-table ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 5:16pm
examples-react-highcharts ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 5:16pm
examples-react-material-ui ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 5:16pm
examples-react-pivot-table ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 5:16pm
examples-vue-query-builder ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 5:16pm

Copy link

codecov bot commented Oct 9, 2024

Codecov Report

Attention: Patch coverage is 91.17647% with 9 lines in your changes missing coverage. Please review.

Project coverage is 82.68%. Comparing base (d1b07f1) to head (d810695).
Report is 9 commits behind head on master.

Files with missing lines Patch % Lines
rust/cubesql/cubesql/src/compile/query_engine.rs 88.23% 6 Missing ⚠️
rust/cubesql/cubesql/src/sql/compiler_cache.rs 90.32% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #8793      +/-   ##
==========================================
- Coverage   82.69%   82.68%   -0.01%     
==========================================
  Files         221      221              
  Lines       78472    78474       +2     
==========================================
- Hits        64890    64889       -1     
- Misses      13582    13585       +3     
Flag Coverage Δ
cubesql 82.68% <91.17%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@MazterQyou MazterQyou force-pushed the cubesql/no-async-node-within-planning branch from 5118b3d to 81edfd1 Compare October 9, 2024 18:43
Copy link
Member

@mcheshkov mcheshkov left a comment

Choose a reason for hiding this comment

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

LGTM

@MazterQyou MazterQyou force-pushed the cubesql/no-async-node-within-planning branch from 81edfd1 to 23315a0 Compare November 20, 2024 17:16
@MazterQyou MazterQyou force-pushed the cubesql/no-async-node-within-planning branch from 23315a0 to d810695 Compare December 3, 2024 02:28
@MazterQyou MazterQyou merged commit 3e203e8 into master Dec 3, 2024
78 checks passed
@MazterQyou MazterQyou deleted the cubesql/no-async-node-within-planning branch December 3, 2024 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants