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
[WIP][BEAM-9379] Update calcite to 1.26 #12962
Conversation
R: @amaliujia |
Codecov Report
@@ Coverage Diff @@
## master #12962 +/- ##
==========================================
- Coverage 82.72% 82.69% -0.03%
==========================================
Files 466 466
Lines 57518 57518
==========================================
- Hits 47582 47567 -15
- Misses 9936 9951 +15
Continue to review full report at Codecov.
|
Can you publish a build scan by running your second step with |
It might be a huge amount of work. We can just add the new vendored module and then release it, but we will want to know that we have enough people available to also port to it. |
agree on this. we could vendor module first and use released library for porting work. last few weeks. I did a testing on my branch https://github.com/vectorijk/beam/tree/calcite-1-25 and run |
|
Looks like Calcite switched to |
this one looks easier - just a change of capital to lowercase CC @robinyqiu |
Seems there is something special and missing from |
This is just a bad test. It checks the exact string instead of the key elements of the string so it is sensitive to irrelevant changes. |
Can we consider moving this one to 1.26 because of https://lists.apache.org/thread.html/r0b0fbe2038388175951ce1028182d980f9e9a7328be13d52dab70bb3%40%3Cannounce.apache.org%3E Probably Beam's use case of Calcite is not impacted by this but I can envision the automatic vulnerability tools complaining on this soon. |
19d11b7
to
38e8111
Compare
8f79ca3
to
c7b4b7f
Compare
I am in need of advice / assistance. What I ran into is that some tests in the current state of this pull request fail over a change in Calcite. I tracked the source of this exception back to Calcite where a few months ago this default method was added in Calcite by @julianhyde : https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/sql/parser/SqlParserImplFactory.java#L58 This default implementation simply returns a The problem I have is that my knowledge is lacking how to correctly override this method to return the implementation for Beam that makes it possible to do a A pointer on how I should fix this correctly is highly appreciated. I found in the generated code of BeamSqlParserImpl this code (I shortened it a bit)
which is generated from a template in Calcite itself and (as far as I have been able to find so far) does not have a way of implementing a non-default method for |
@tysonjh @amaliujia @kennknowles - Who could help on this PR? |
Yes please. At this point I see these
|
eec087e
to
de8ff95
Compare
Thanks for all the work you've done on this so far! Hopefully you saw my response to your email to dev@ about about the DDL issues. The other two things you are seeing are probably around changes that need to be made to the type translation code in BeamCalcRel.java. I don't have time to pick this up right now, but I do have time planned for this in Late January/Early February. |
@apilloud Yes, I read and followed the links from your email. |
All of this was fixed in #14729 |
Thanks for all the work you did to make this happen! |
In these commits I have done the following:
To test this I have run these to install the new calcite locally
Current state of this initial pull request:
R:@amaliujia
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).[BEAM-XXX] Fixes bug in ApproximateQuantiles
, where you replaceBEAM-XXX
with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.