-
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-5729] added database/sql reader/writer #6676
Conversation
passed initial chec |
R: @lostluck |
Sorry about the delay. Adding Robert as a reviewer. Any idea about the test failures ? |
The RAT failures are because the license text needs to be at the top of every file. The go failure appears to be this test: From the full jenkins output: 06:06:40 === RUN Test_queryRecordMapperProvider |
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.
I love how complete this CL is. Once we get the tests passing, we should get this in.
There are opportunities to reduce overhead, either in connections to the DB or in reducing work done per element, but that can be done later as needed.
I tried to figure out what's going wrong with the test, but nothing is jumping out at me, it appears the mapping should work as expected. I assume that the test passes locally for you.
Consider editing the title of this PR to be prefixed with [BEAM-5729] so it gets linked to the Jira you filed before. https://issues.apache.org/jira/browse/BEAM-5729 Consider also requesting contributor status to the Beam jira, so we can correctly assign the JIRA to you. Afterall, you did all this work! |
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.
Thanks for your patience. I have a few small comments, but otherwise LGTM.
Thanks again! Edit: Though you could prefix the github PR title with [BEAM-5729], that would be ideal. |
Thanks. @adranwit could you fix up to a single (or few) commits(s) for merging ? |
@chamikaramj not sure what the ask is "could you fix up to a single (or few) commit (s)", what exactly needs to be fixed ? |
Sorry, could you fix up your commits (currently 11) to one or few commits that you would like to appear in Beam commit history as per https://beam.apache.org/contribute/committer-guide/. |
@chamikaramj not sure if you can remove existing comments, all that said I have added the extra one summarizing the changes: [BEAM-5729] added database/sql based reader and writer |
You can use "git rebase" to fixup commits. See https://help.github.com/articles/about-git-rebase/. |
Looks like commit history got messed up somehow ? Usually I perform following to fixup all my commits. (1) git rebase -i HEAD~<number of my commits> |
@@ -38,6 +38,14 @@ def test_assert_that_passes(self): | |||
with TestPipeline() as p: | |||
assert_that(p | Create([1, 2, 3]), equal_to([1, 2, 3])) | |||
|
|||
def test_assert_that_passes_order_does_not_matter(self): | |||
with TestPipeline() as p: |
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.
Are these changes (to util_test.py) intended ? Looks like a merge issue.
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.
Everything else looks good. Thanks.
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.
not sure how to get that removed
Thanks. Merged. |
BEAM-5728 Adds database/sql reader/writer in go sdk
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)