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

[BEAM-22] Use an explicit coder in XmlSourceTest #112

Closed

Conversation

tgroh
Copy link
Member

@tgroh tgroh commented Apr 1, 2016

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

  • Make sure the PR title is formatted like:
    [BEAM-<Jira issue #>] Description of pull request
  • Make sure tests pass via mvn clean verify. (Even better, enable
    Travis-CI on your fork and ensure the whole test matrix passes).
  • Replace "<Jira issue #>" in the title with the actual Jira issue
    number, if there is one.
  • If this contribution is large, please file an Apache
    Individual Contributor License Agreement.

The standard coder for an XML source is the JAXBCoder, which is not
suitable as part of a composite coder.

This is required for [BEAM-22], due to the implementation of
CreatePCollectionView.

The standard coder for an XML source is the JAXBCoder, which is not
suitable as part of a composite coder.
@tgroh
Copy link
Member Author

tgroh commented Apr 1, 2016

R: @bjchambers

@bjchambers
Copy link
Contributor

@dhalperi for discussion. If XmlCoder is not suitable for intermediate usage, should we really have XmlSource set that as the coder for its output?

@bjchambers
Copy link
Contributor

LGTM, will merge pending discussion.

PCollection<Train> output = p.apply(Read.from(source).named("ReadFileData"));
AvroCoder<Train> intermediateCoder = AvroCoder.of(Train.class);
PCollection<Train> output =
p.apply(Read.from(source).named("ReadFileData")).setCoder(intermediateCoder);
Copy link
Contributor

Choose a reason for hiding this comment

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

please update to the happy apply syntax (aka, drop 'named').

@dhalperi
Copy link
Contributor

dhalperi commented Apr 4, 2016

R: @dhalperi so the scripts pick it up.

@dhalperi
Copy link
Contributor

dhalperi commented Apr 4, 2016

Please put [BEAM-22] in the PR/commit description?

@tgroh tgroh changed the title Use an explicit coder in XmlSourceTest [BEAM-22] Use an explicit coder in XmlSourceTest Apr 4, 2016
@dhalperi
Copy link
Contributor

dhalperi commented Apr 4, 2016

My main comment is that we should probably fix JAXBCoder to behave correctly in inner context. That is backwards-incompatible, but it fixes a bug that is probably causing crashes if users are using it this way.

@dhalperi
Copy link
Contributor

dhalperi commented Apr 4, 2016

R: @davorbonaci to comment on backwards-incompatible change.

@tgroh
Copy link
Member Author

tgroh commented Apr 4, 2016

Replaced by #116

@tgroh tgroh closed this Apr 4, 2016
iemejia referenced this pull request in iemejia/beam Jan 12, 2018
mareksimunek pushed a commit to mareksimunek/beam that referenced this pull request May 9, 2018
apache#13 [euphoria-flink] Batch executor uses hash code as a key in shufflles
pl04351820 pushed a commit to pl04351820/beam that referenced this pull request Dec 20, 2023
* refactor: remove async unit test nox session

* refactor: remove async unit test directory

* fix: noxfile unit test imports and arglist
xinyuiscool pushed a commit to xinyuiscool/beam that referenced this pull request Feb 28, 2024
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