[jira] [Comment Edited] (BEAM-469) NullableCoder should encode using the context given and not always use the nested context

[ https://issues.apache.org/jira/browse/BEAM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423190#comment-15423190 ] Mariusz Wojakowski edited comment on BEAM-469 at 8/16/16 6:22 PM: --

Jenkins build became unstable: beam_PostCommit_MavenVerify » Apache Beam :: Examples :: Java #1133

See

[jira] [Updated] (BEAM-555) Documentation in BiqQueryIO.java has awkward cut-and-paste error.

[ https://issues.apache.org/jira/browse/BEAM-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frances Perry updated BEAM-555: --- Assignee: Frank Yellin (was: Davor Bonaci) > Documentation in BiqQueryIO.java has awkward

Jenkins build is back to stable : beam_PostCommit_MavenVerify » Apache Beam :: Examples :: Java #1134

See

Jenkins build is back to stable : beam_PostCommit_MavenVerify #1134

See

[GitHub] incubator-beam pull request #537: [BEAM-378] integrate setuptools in Maven b...

Github user wikier closed the pull request at: https://github.com/apache/incubator-beam/pull/537 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[1/2] incubator-beam git commit: ByteKeyRangeTracker: synchronize toString

Repository: incubator-beam Updated Branches: refs/heads/master f1935d5d1 -> 9b4a464a3 ByteKeyRangeTracker: synchronize toString It's the only unsynchronized function, and it could potentially produce bad data. Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit:

[2/2] incubator-beam git commit: Closes #837

Closes #837 Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam/commit/9b4a464a Tree: http://git-wip-us.apache.org/repos/asf/incubator-beam/tree/9b4a464a Diff:

[GitHub] incubator-beam pull request #837: ByteKeyRangeTracker: synchronize toString

Github user asfgit closed the pull request at: https://github.com/apache/incubator-beam/pull/837 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Updated] (BEAM-556) typo in documentation

[ https://issues.apache.org/jira/browse/BEAM-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frances Perry updated BEAM-556: --- Assignee: Frank Yellin (was: Frances Perry) > typo in documentation > - > >

[GitHub] incubator-beam pull request #830: Improve error handling in gcsio.py

Github user charlesccychen closed the pull request at: https://github.com/apache/incubator-beam/pull/830 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[GitHub] incubator-beam pull request #838: Add example pipeline using runtime display...

GitHub user swegner opened a pull request: https://github.com/apache/incubator-beam/pull/838 Add example pipeline using runtime display data aggregators Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the

[jira] [Updated] (BEAM-440) Create.values() returns a type-unsafe Coder

[ https://issues.apache.org/jira/browse/BEAM-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manu Zhang updated BEAM-440: Assignee: (was: Manu Zhang) > Create.values() returns a type-unsafe Coder >

[1/2] incubator-beam git commit: Fixing the juliaset example

Repository: incubator-beam Updated Branches: refs/heads/python-sdk 3b40945e9 -> 600684865 Fixing the juliaset example Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam/commit/7f842f23 Tree:

[GitHub] incubator-beam pull request #839: Fixing the juliaset example

Github user asfgit closed the pull request at: https://github.com/apache/incubator-beam/pull/839 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Issue Comment Deleted] (BEAM-469) NullableCoder should encode using the context given and not always use the nested context

[ https://issues.apache.org/jira/browse/BEAM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Cwik updated BEAM-469: --- Comment: was deleted (was: That doesn't work with nesting. Imagine I have a KV coder with both the key and

[jira] [Comment Edited] (BEAM-469) NullableCoder should encode using the context given and not always use the nested context

[ https://issues.apache.org/jira/browse/BEAM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422979#comment-15422979 ] Daniel Halperin edited comment on BEAM-469 at 8/16/16 4:24 PM: --- I think there

[jira] [Commented] (BEAM-469) NullableCoder should encode using the context given and not always use the nested context

[ https://issues.apache.org/jira/browse/BEAM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423000#comment-15423000 ] Luke Cwik commented on BEAM-469: That doesn't work with nesting. Imagine I have a KV coder with both the key

[jira] [Reopened] (BEAM-469) NullableCoder should encode using the context given and not always use the nested context

[ https://issues.apache.org/jira/browse/BEAM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Cwik reopened BEAM-469: Assignee: (was: Luke Cwik) Re-opening because I believe Dan is correct about passing contexts around.

[jira] [Issue Comment Deleted] (BEAM-469) NullableCoder should encode using the context given and not always use the nested context

[ https://issues.apache.org/jira/browse/BEAM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Cwik updated BEAM-469: --- Comment: was deleted (was: Re-opening because I believe Dan is correct about passing contexts around.) >