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-121] Add DisplayData for IO transforms #123

Closed
wants to merge 2 commits into from

Conversation

swegner
Copy link
Contributor

@swegner swegner commented Apr 5, 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.

@swegner
Copy link
Contributor Author

swegner commented Apr 5, 2016

R=@dhalperi @bjchambers

@@ -326,6 +327,14 @@
}

@Override
public void populateDisplayData(DisplayData.Builder builder) {
builder.add("schema", type);
Copy link
Contributor

Choose a reason for hiding this comment

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

What happens here? type is a Class. Will it just get automatically converted to a String?

I would probably just drop the type. We aren't planning to specify the Coder for each transform as static metadata, are we?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Class ends up being a common metadata type, so we support it first-class for display metadata. We'll use the class name (and shortName) for UI.

No, we aren't specifying a coder for each transform.

I had assumed the schema information is important-- is that true? If so, is this the best way to capture it?

Copy link
Contributor

Choose a reason for hiding this comment

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

In this case, the schema is effectively the Coder. I would not include it unless you plan to include the coder.

@swegner swegner force-pushed the displaydata-io branch 3 times, most recently from 1c4f9c4 to 1ecbe63 Compare April 11, 2016 16:09
@swegner
Copy link
Contributor Author

swegner commented Apr 11, 2016

Ok, I believe I've addressed the feedback thusfar. @dhalperi, mind taking another look?

@swegner swegner force-pushed the displaydata-io branch 2 times, most recently from b817a25 to 56306dd Compare April 14, 2016 18:11
@asfgit asfgit closed this in a05bd74 Apr 23, 2016
@swegner swegner deleted the displaydata-io branch April 23, 2016 00:23
@swegner
Copy link
Contributor Author

swegner commented May 16, 2016

Backported via GoogleCloudPlatform/DataflowJavaSDK#218

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
#! [euphoria-examples] Provide some more explanatory comments
@robertwb robertwb mentioned this pull request Jun 9, 2022
4 tasks
@kw2542 kw2542 mentioned this pull request Jun 9, 2022
4 tasks
@yeandy yeandy mentioned this pull request Jun 10, 2022
4 tasks
@AnandInguva AnandInguva mentioned this pull request Jun 10, 2022
4 tasks
pl04351820 pushed a commit to pl04351820/beam that referenced this pull request Dec 20, 2023
* refactor: move generated client instantiation out of base class

* feat: integrate microgen async client to client

* feat: make collections call backed by async

* fix: failing asyncmock assertion

* refactor: remove unused install

* fix: lint

* refactor: shared functionality in client to base class

* refactor: move AsyncMock to test helpers

* fix: return type in client docs

* feat: integrate microgen async client to collection

* fix: lint

* feat: integrate microgen async client to document

* feat: integrate microgen async client to batch

* fix: use AsyncMock for batch async tests:

* fix: collection and document testing batch

* feat: integrate microgen async client to transaction

* fix: remove unused imports
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.

2 participants