Skip to content

Conversation

@youngoli
Copy link
Contributor

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

This PR is attempting to make sure the Python SDK Harness can handle receiving flattens in bundles to process (specifically pTransforms with the URN for flattens).

I'm posting this without running mvn clean verify because I couldn't get the build to work on my local machine (I think I set up the environment incorrectly) and it's a relatively small change, so I'm hoping that Jenkins will catch any issues.

Added the flatten URN to the URNs registered with the
BeamTransformFactory.
@asfgit
Copy link

asfgit commented Jan 13, 2018

SUCCESS

--none--

@youngoli
Copy link
Contributor Author

R: @robertwb

Copy link
Contributor

@robertwb robertwb left a comment

Choose a reason for hiding this comment

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

LGTM

consumers)


@BeamTransformFactory.register_urn(urns.FLATTEN_TRANSFORM, None)
Copy link
Contributor

Choose a reason for hiding this comment

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

Did "urns.FLATTEN_TRANSFORM" need to be updated to match Java?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, right now it differs from the one being used in Java. Since PR #4310 is being worked on to solve the discrepancies, we can wait to merge this PR until after that one is merged, or I can just make a new PR later to fix the URN. What do you think would be better? I'm leaning towards the second option.

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, let's get this one in and hopefully #4310 will be merged soon.

@robertwb robertwb merged commit 70a520c into apache:master Jan 17, 2018
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