-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[BEAM-6558] Add IWYU plugin, activate for Beam SQL, fix errors #7700
Conversation
If |
I didn't dig deep, but I see a similar problem with I'm wondering if it's the same kind of problem as we have with |
@kennknowles liked the idea to add end-to-end tests. I noticed that there are some user example project such as word-count-example that are generated as part of the build. It would be nice to add some SQL example projects their as well, and make sure the release validation process actually builds and runs those example applications. I can create a JIRA to add BeamSQL example project, if it is not there yet. |
@amaliujia yes, one of the dependencies (actually lots of them) depend on commons-codec. Since they probably depend on it in |
a8cc8a7
to
8051be2
Compare
OK, got past legit failures. Deflaking time. |
Run java precommit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Beam SQL was successfully compiling and passing tests even though it had a totally straightforward compile-time dependency on commons-codec, which it did not declare.
I had thought that Gradle made this issue a thing of the past, but it is not so. This adds the capability that we got from
mvn dependency:analyze
plugin. It found the known error and a couple other issues, which may or may not be spurious.This needs to be cherrypicked for 2.10.0 as Beam SQL was nonfunctional for 2.9.0. We can advise on a workaround to simply add the necessary dependency. We also need an end-to-end test that will ensure our shipped artifact works for users.
Follow this checklist to help us incorporate your contribution quickly and easily:
[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.It will help us expedite review of your Pull Request if you tag someone (e.g.
@username
) to look at it.Post-Commit Tests Status (on master branch)