[jira] [Created] (BEAM-2103) Missing remark about Beam being incompatible to Python 3 in the documentation

Tobias Feldhaus created BEAM-2103: - Summary: Missing remark about Beam being incompatible to Python 3 in the documentation Key: BEAM-2103 URL: https://issues.apache.org/jira/browse/BEAM-2103 Project:

[jira] [Created] (BEAM-2102) deprecated use of pip --download command

Tobias Feldhaus created BEAM-2102: - Summary: deprecated use of pip --download command Key: BEAM-2102 URL: https://issues.apache.org/jira/browse/BEAM-2102 Project: Beam Issue Type: Bug

[jira] [Resolved] (BEAM-1716) Using Instant type in TableRow should map to the right output format for TIMESTAMP in BigQuery

[ https://issues.apache.org/jira/browse/BEAM-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus resolved BEAM-1716. --- Resolution: Invalid > Using Instant type in TableRow should map to the right output format for

[jira] [Commented] (BEAM-1716) Using Instant type in TableRow should map to the right output format for TIMESTAMP in BigQuery

[ https://issues.apache.org/jira/browse/BEAM-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982824#comment-15982824 ] Tobias Feldhaus commented on BEAM-1716: --- Example to reproduce:

[jira] [Resolved] (BEAM-1997) Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit)

[ https://issues.apache.org/jira/browse/BEAM-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus resolved BEAM-1997. --- Resolution: Invalid Fix Version/s: 0.6.0 > Scaling Problem of Beam (size of the

[jira] [Commented] (BEAM-1997) Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit)

[ https://issues.apache.org/jira/browse/BEAM-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974777#comment-15974777 ] Tobias Feldhaus commented on BEAM-1997: --- Mea culpa, it seems like I've had more than one file per

[jira] [Comment Edited] (BEAM-1997) Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit)

[ https://issues.apache.org/jira/browse/BEAM-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973245#comment-15973245 ] Tobias Feldhaus edited comment on BEAM-1997 at 4/18/17 6:33 PM: You are

[jira] [Comment Edited] (BEAM-1997) Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit)

[ https://issues.apache.org/jira/browse/BEAM-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973245#comment-15973245 ] Tobias Feldhaus edited comment on BEAM-1997 at 4/18/17 6:31 PM: You are

[jira] [Commented] (BEAM-1997) Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit)

[ https://issues.apache.org/jira/browse/BEAM-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973245#comment-15973245 ] Tobias Feldhaus commented on BEAM-1997: --- You are correct, I've posted the wrong screenshots, sorry. I

[jira] [Updated] (BEAM-1997) Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit)

[ https://issues.apache.org/jira/browse/BEAM-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus updated BEAM-1997: -- Description: After switching from Dataflow SDK 1.9 to Apache Beam SDK 0.6 my pipeline does no

[jira] [Updated] (BEAM-1997) Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit)

[ https://issues.apache.org/jira/browse/BEAM-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus updated BEAM-1997: -- Description: After switching from Dataflow SDK 1.9 to Apache Beam SDK 0.6 my pipeline does no

[jira] [Created] (BEAM-1997) Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit)

Tobias Feldhaus created BEAM-1997: - Summary: Scaling Problem of Beam (size of the serialized JSON representation of the pipeline exceeds the allowable limit) Key: BEAM-1997 URL:

[jira] [Commented] (BEAM-1714) Null Pointer Exception when outputting a TableRow with a Null value for a key

[ https://issues.apache.org/jira/browse/BEAM-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15960467#comment-15960467 ] Tobias Feldhaus commented on BEAM-1714: --- Sorry that I didn't manage to come up with a testcase and

[jira] [Commented] (BEAM-1718) Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow

[ https://issues.apache.org/jira/browse/BEAM-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932974#comment-15932974 ] Tobias Feldhaus commented on BEAM-1718: --- This is good to know, thank you! Then, maybe, I have another

[jira] [Comment Edited] (BEAM-1718) Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow

[ https://issues.apache.org/jira/browse/BEAM-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931216#comment-15931216 ] Tobias Feldhaus edited comment on BEAM-1718 at 3/18/17 1:17 PM: When

[jira] [Commented] (BEAM-1718) Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow

[ https://issues.apache.org/jira/browse/BEAM-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931216#comment-15931216 ] Tobias Feldhaus commented on BEAM-1718: --- When batch-processing, shifting back in time is normal and

[jira] [Commented] (BEAM-1718) Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow

[ https://issues.apache.org/jira/browse/BEAM-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927915#comment-15927915 ] Tobias Feldhaus commented on BEAM-1718: --- This is the triggering method in a class extending DoFn:

[jira] [Created] (BEAM-1718) Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow

Tobias Feldhaus created BEAM-1718: - Summary: Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow Key: BEAM-1718 URL:

[jira] [Created] (BEAM-1716) Using Instant type in TableRow should map to the right output format for TIMESTAMP in BigQuery

Tobias Feldhaus created BEAM-1716: - Summary: Using Instant type in TableRow should map to the right output format for TIMESTAMP in BigQuery Key: BEAM-1716 URL: https://issues.apache.org/jira/browse/BEAM-1716

[jira] [Updated] (BEAM-1714) Null Pointer Exception when outputting a TableRow with a Null value for a key

[ https://issues.apache.org/jira/browse/BEAM-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus updated BEAM-1714: -- Fix Version/s: First stable release > Null Pointer Exception when outputting a TableRow with a

[jira] [Updated] (BEAM-1714) Null Pointer Exception when outputting a TableRow with a Null value for a key

[ https://issues.apache.org/jira/browse/BEAM-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus updated BEAM-1714: -- Component/s: (was: beam-model) sdk-java-gcp > Null Pointer Exception when

[jira] [Created] (BEAM-1714) Null Pointer Exception when outputting a TableRow with a Null value for a key

Tobias Feldhaus created BEAM-1714: - Summary: Null Pointer Exception when outputting a TableRow with a Null value for a key Key: BEAM-1714 URL: https://issues.apache.org/jira/browse/BEAM-1714 Project: