[jira] [Assigned] (BEAM-1304) NPE if trying to get value of Aggregator that does not exist.

[ https://issues.apache.org/jira/browse/BEAM-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-1304: Assignee: Stas Levin (was: Amit Sela) > NPE if trying to get value of Aggregator that does not

[jira] [Resolved] (BEAM-1304) NPE if trying to get value of Aggregator that does not exist.

[ https://issues.apache.org/jira/browse/BEAM-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-1304. -- Resolution: Fixed Fix Version/s: 0.6.0 > NPE if trying to get value of Aggregator that does not

[jira] [Commented] (BEAM-1223) Replace public constructors with static factory methods for Sum.[*]Fn classes

[ https://issues.apache.org/jira/browse/BEAM-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853651#comment-15853651 ] Stas Levin commented on BEAM-1223: -- Hi [~dhalp...@google.com], Sure thing, I was not aware of this label.

[jira] [Commented] (BEAM-1223) Replace public constructors with static factory methods for Sum.[*]Fn classes

[ https://issues.apache.org/jira/browse/BEAM-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853671#comment-15853671 ] Stas Levin commented on BEAM-1223: -- Thanks! > Replace public constructors with static factory methods for

[jira] [Commented] (BEAM-1295) Annotations are not properly rendered in JavaDoc when using {@code}

[ https://issues.apache.org/jira/browse/BEAM-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833533#comment-15833533 ] Stas Levin commented on BEAM-1295: -- I'm afraid my suggestion does not entirely work, while the IDE seems

[jira] [Commented] (BEAM-1295) Annotations are not properly rendered in JavaDoc when using {@code}

[ https://issues.apache.org/jira/browse/BEAM-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833547#comment-15833547 ] Stas Levin commented on BEAM-1295: -- I think we may be being bitten by

[jira] [Updated] (BEAM-1295) Annotations are not properly rendered in JavaDoc when using {@code}

[ https://issues.apache.org/jira/browse/BEAM-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1295: - Description: {code} {@code {@literal @}Override } {code} Produces {code} { @}Override {code} Instead of:

[jira] [Updated] (BEAM-1295) Annotations are not properly rendered in JavaDoc when using {@code}

[ https://issues.apache.org/jira/browse/BEAM-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1295: - Description: {code} {@code {@literal @}Override } {code} Produces {code} { @}Override {code} Instead of:

[jira] [Updated] (BEAM-1295) Annotations are not properly rendered in JavaDoc when using {@code}

[ https://issues.apache.org/jira/browse/BEAM-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1295: - Description: {code} {@code {@literal @}Override } {code} Produces {code} { @}Override {code} Instead of:

[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site

[ https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882918#comment-15882918 ] Stas Levin commented on BEAM-1499: -- [~jasonkuster], I've added two paragraphs under the contribute/testing

[jira] [Comment Edited] (BEAM-1499) Update testing documentation at beam-site

[ https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882918#comment-15882918 ] Stas Levin edited comment on BEAM-1499 at 2/24/17 3:45 PM: --- [~jasonkuster], I've

[jira] [Commented] (BEAM-1543) TestPipeline: @Rule error message confusing/javadoc doesn't explain proper usage

[ https://issues.apache.org/jira/browse/BEAM-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880974#comment-15880974 ] Stas Levin commented on BEAM-1543: -- Definitely, I'll take care of it. Did this PR assist in resolving the

[jira] [Comment Edited] (BEAM-1543) TestPipeline: @Rule error message confusing/javadoc doesn't explain proper usage

[ https://issues.apache.org/jira/browse/BEAM-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880974#comment-15880974 ] Stas Levin edited comment on BEAM-1543 at 2/23/17 6:26 PM: --- [~kenn] definitely,

[jira] [Comment Edited] (BEAM-1399) Code coverage numbers are not accurate

[ https://issues.apache.org/jira/browse/BEAM-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873590#comment-15873590 ] Stas Levin edited comment on BEAM-1399 at 2/20/17 8:04 AM: --- Thanks for the tip

[jira] [Comment Edited] (BEAM-1399) Code coverage numbers are not accurate

[ https://issues.apache.org/jira/browse/BEAM-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873590#comment-15873590 ] Stas Levin edited comment on BEAM-1399 at 2/20/17 8:04 AM: --- Thanks for the tip

[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site

[ https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873270#comment-15873270 ] Stas Levin commented on BEAM-1499: -- [~davor], sure thing. Thanks for helping out! Looking forward to get

[jira] [Comment Edited] (BEAM-298) Make TestPipeline implement the TestRule interface

[ https://issues.apache.org/jira/browse/BEAM-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862327#comment-15862327 ] Stas Levin edited comment on BEAM-298 at 2/11/17 11:39 AM: --- After taking a deeper

[jira] [Commented] (BEAM-298) Make TestPipeline implement the TestRule interface

[ https://issues.apache.org/jira/browse/BEAM-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862327#comment-15862327 ] Stas Levin commented on BEAM-298: - Could you please provide some more info regarding your scenario and how I

[jira] [Assigned] (BEAM-1048) Spark Runner streaming batch duration does not include duration of reading from source

[ https://issues.apache.org/jira/browse/BEAM-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-1048: Assignee: Stas Levin (was: Kobi Salant) > Spark Runner streaming batch duration does not include

[jira] [Commented] (BEAM-1048) Spark Runner streaming batch duration does not include duration of reading from source

[ https://issues.apache.org/jira/browse/BEAM-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863792#comment-15863792 ] Stas Levin commented on BEAM-1048: -- [~ksalant], following our discussion and your blessing I'm assigning

[jira] [Resolved] (BEAM-878) Allow usage of ApiSurfaceTest providing nothing but a whitelist

[ https://issues.apache.org/jira/browse/BEAM-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-878. - Resolution: Fixed > Allow usage of ApiSurfaceTest providing nothing but a whitelist >

[jira] [Commented] (BEAM-1295) Annotations are not properly rendered in JavaDoc when using {@code}

[ https://issues.apache.org/jira/browse/BEAM-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859801#comment-15859801 ] Stas Levin commented on BEAM-1295: -- Hi [~dhalp...@google.com], Sorry for the delayed response. I'm

[jira] [Resolved] (BEAM-883) Make ApiSurfaceTest fail if something whitelisted is _not_ exposed

[ https://issues.apache.org/jira/browse/BEAM-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-883. - Resolution: Fixed > Make ApiSurfaceTest fail if something whitelisted is _not_ exposed >

[jira] [Updated] (BEAM-883) Make ApiSurfaceTest fail if something whitelisted is _not_ exposed

[ https://issues.apache.org/jira/browse/BEAM-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-883: Fix Version/s: (was: Not applicable) 0.6.0 > Make ApiSurfaceTest fail if something

[jira] [Updated] (BEAM-882) Make ApiSurfaceTest detect the java package/module under test

[ https://issues.apache.org/jira/browse/BEAM-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-882: Fix Version/s: (was: Not applicable) 0.6.0 > Make ApiSurfaceTest detect the java

[jira] [Updated] (BEAM-878) Allow usage of ApiSurfaceTest providing nothing but a whitelist

[ https://issues.apache.org/jira/browse/BEAM-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-878: Fix Version/s: (was: Not applicable) 0.6.0 > Allow usage of ApiSurfaceTest providing

[jira] [Created] (BEAM-1499) Update testing documentation at beam-site

Stas Levin created BEAM-1499: Summary: Update testing documentation at beam-site Key: BEAM-1499 URL: https://issues.apache.org/jira/browse/BEAM-1499 Project: Beam Issue Type: Improvement

[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site

[ https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870539#comment-15870539 ] Stas Levin commented on BEAM-1499: -- I'd be glad to lend a hand as well, just say the word :) > Update

[jira] [Commented] (BEAM-1399) Code coverage numbers are not accurate

[ https://issues.apache.org/jira/browse/BEAM-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868375#comment-15868375 ] Stas Levin commented on BEAM-1399: -- Having spent a while researching this, I can share the following

[jira] [Comment Edited] (BEAM-1399) Code coverage numbers are not accurate

[ https://issues.apache.org/jira/browse/BEAM-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868375#comment-15868375 ] Stas Levin edited comment on BEAM-1399 at 2/15/17 7:06 PM: --- Having spent a while

[jira] [Assigned] (BEAM-878) Allow usage of ApiSurfaceTest providing nothing but a whitelist

[ https://issues.apache.org/jira/browse/BEAM-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-878: --- Assignee: Stas Levin > Allow usage of ApiSurfaceTest providing nothing but a whitelist >

[jira] [Assigned] (BEAM-882) Make ApiSurfaceTest detect the java package/module under test

[ https://issues.apache.org/jira/browse/BEAM-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-882: --- Assignee: Stas Levin > Make ApiSurfaceTest detect the java package/module under test >

[jira] [Assigned] (BEAM-883) Make ApiSurfaceTest fail if something whitelisted is _not_ exposed

[ https://issues.apache.org/jira/browse/BEAM-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-883: --- Assignee: Stas Levin > Make ApiSurfaceTest fail if something whitelisted is _not_ exposed >

[jira] [Updated] (BEAM-979) ConcurrentModificationException exception after hours of running

[ https://issues.apache.org/jira/browse/BEAM-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-979: Assignee: Amit Sela (was: Stas Levin) > ConcurrentModificationException exception after hours of running >

[jira] [Commented] (BEAM-1223) Add static factory methods for Sum.[*]Fn classes

[ https://issues.apache.org/jira/browse/BEAM-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15825732#comment-15825732 ] Stas Levin commented on BEAM-1223: -- [~yafengguo] feel free to start a discussion in the dev list and/or

[jira] [Updated] (BEAM-1557) Separate TestPipeline into 2 versions: one for users, and one for sdk/runner developers

[ https://issues.apache.org/jira/browse/BEAM-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1557: - Description: At the moment, {{TestPipeline}} has enforces some usage patterns, that may be too strict for

[jira] [Updated] (BEAM-1557) Separate TestPipeline into 2 versions: one for users, and one for sdk/runner developers

[ https://issues.apache.org/jira/browse/BEAM-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1557: - Description: At the moment, {{TestPipeline}} has enforces some usage patterns, that may be too strict for

[jira] [Created] (BEAM-1557) Separate TestPipeline into 2 versions: one for users, and one for sdk/runner developers

Stas Levin created BEAM-1557: Summary: Separate TestPipeline into 2 versions: one for users, and one for sdk/runner developers Key: BEAM-1557 URL: https://issues.apache.org/jira/browse/BEAM-1557 Project:

[jira] [Commented] (BEAM-1543) TestPipeline: @Rule error message confusing/javadoc doesn't explain proper usage

[ https://issues.apache.org/jira/browse/BEAM-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884847#comment-15884847 ] Stas Levin commented on BEAM-1543: -- [~sisk], we did some [brush ups|

[jira] [Comment Edited] (BEAM-849) Redesign PipelineResult API

[ https://issues.apache.org/jira/browse/BEAM-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782396#comment-15782396 ] Stas Levin edited comment on BEAM-849 at 1/8/17 12:21 PM: -- In addition, the

[jira] [Updated] (BEAM-1223) Add static factory methods for Sum.[*]Fn classes

[ https://issues.apache.org/jira/browse/BEAM-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1223: - Description: {{Sum.SumDoubleFn}}, {{SumIntegerFn}} and {{SumLongFn}} are not using the {{X.of()}} or

[jira] [Resolved] (BEAM-1230) Typo in the documentation of the Window class

[ https://issues.apache.org/jira/browse/BEAM-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-1230. -- Resolution: Fixed Fix Version/s: 0.5.0 > Typo in the documentation of the Window class >

[jira] [Updated] (BEAM-1205) Auto set "enableAbandonedNodeEnforcement" in TestPipeline

[ https://issues.apache.org/jira/browse/BEAM-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1205: - Description: At the moment one has to manually set {{enableAbandonedNodeEnforcement(false)}} in tests

[jira] [Updated] (BEAM-1205) Auto set "enableAbandonedNodeEnforcement" in TestPipeline

[ https://issues.apache.org/jira/browse/BEAM-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1205: - Description: At the moment one has to manually set {{enableAbandonedNodeEnforcement(false)}} in tests

[jira] [Updated] (BEAM-1223) Add static factory methods for Sum.[*]Fn classes

[ https://issues.apache.org/jira/browse/BEAM-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1223: - Summary: Add static factory methods for Sum.[*]Fn classes (was: Static factory methods for Sum.[*]Fn

[jira] [Commented] (BEAM-1205) Auto set "enableAbandonedNodeEnforcement" in TestPipeline

[ https://issues.apache.org/jira/browse/BEAM-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15770602#comment-15770602 ] Stas Levin commented on BEAM-1205: -- I see, thanks for commenting. So {{if (!sCrashingRunner ||

[jira] [Created] (BEAM-1205) Auto set "enableAbandonedNodeEnforcement" in TestPipeline

Stas Levin created BEAM-1205: Summary: Auto set "enableAbandonedNodeEnforcement" in TestPipeline Key: BEAM-1205 URL: https://issues.apache.org/jira/browse/BEAM-1205 Project: Beam Issue Type:

[jira] [Updated] (BEAM-1712) TestPipeline.run should perhaps waitUntilFinish

[ https://issues.apache.org/jira/browse/BEAM-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1712: - Priority: Minor (was: Major) > TestPipeline.run should perhaps waitUntilFinish >

[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site

[ https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944993#comment-15944993 ] Stas Levin commented on BEAM-1499: -- [~jasonkuster], we can add some info following the change of

[jira] [Resolved] (BEAM-1713) SparkRuntimeContext instances are leaking via StateSpecFunctions#mapSourceFunction

[ https://issues.apache.org/jira/browse/BEAM-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-1713. -- Resolution: Fixed Fix Version/s: First stable release > SparkRuntimeContext instances are leaking

[jira] [Resolved] (BEAM-1839) Opitimize StatelessJavaSerializer

[ https://issues.apache.org/jira/browse/BEAM-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-1839. -- Resolution: Fixed Fix Version/s: First stable release > Opitimize StatelessJavaSerializer >

[jira] [Resolved] (BEAM-1828) GlobalWatermarkHolder uses unpersist instead of destory

[ https://issues.apache.org/jira/browse/BEAM-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-1828. -- Resolution: Fixed Fix Version/s: First stable release > GlobalWatermarkHolder uses unpersist

[jira] [Commented] (BEAM-1676) SdkCoreApiSurfaceTest Failed When Directory Contains Space

[ https://issues.apache.org/jira/browse/BEAM-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948913#comment-15948913 ] Stas Levin commented on BEAM-1676: -- This has recently been fixed in {{Guava}}'s

[jira] [Updated] (BEAM-1839) Optimize StatelessJavaSerializer

[ https://issues.apache.org/jira/browse/BEAM-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1839: - Summary: Optimize StatelessJavaSerializer (was: Opitimize StatelessJavaSerializer) > Optimize

[jira] [Created] (BEAM-1839) Opitimize StatelessJavaSerializer

Stas Levin created BEAM-1839: Summary: Opitimize StatelessJavaSerializer Key: BEAM-1839 URL: https://issues.apache.org/jira/browse/BEAM-1839 Project: Beam Issue Type: Improvement

[jira] [Updated] (BEAM-1839) Opitimize StatelessJavaSerializer

[ https://issues.apache.org/jira/browse/BEAM-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1839: - Description: Since Kryo uses reflection to sequentially look for constructor signatures, we can prevent

[jira] [Assigned] (BEAM-1828) GlobalWatermarkHolder uses unpersist instead of destory

[ https://issues.apache.org/jira/browse/BEAM-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-1828: Assignee: Stas Levin (was: Amit Sela) > GlobalWatermarkHolder uses unpersist instead of destory >

[jira] [Created] (BEAM-1828) GlobalWatermarkHolder uses unpersist instead of destory

Stas Levin created BEAM-1828: Summary: GlobalWatermarkHolder uses unpersist instead of destory Key: BEAM-1828 URL: https://issues.apache.org/jira/browse/BEAM-1828 Project: Beam Issue Type: Bug

[jira] [Commented] (BEAM-1676) SdkCoreApiSurfaceTest Failed When Directory Contains Space

[ https://issues.apache.org/jira/browse/BEAM-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931625#comment-15931625 ] Stas Levin commented on BEAM-1676: -- Good catch [~markflyhigh], looks like it has to do with [this issue in

[jira] [Commented] (BEAM-1777) If PipelineEnforcement throws an exception after Pipeline.run() fails, it overwrites the original failure

[ https://issues.apache.org/jira/browse/BEAM-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936232#comment-15936232 ] Stas Levin commented on BEAM-1777: -- I wonder if this can be resolved by removing the {{finally}} around

[jira] [Comment Edited] (BEAM-1777) If PipelineEnforcement throws an exception after Pipeline.run() fails, it overwrites the original failure

[ https://issues.apache.org/jira/browse/BEAM-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936232#comment-15936232 ] Stas Levin edited comment on BEAM-1777 at 3/22/17 12:47 PM: I wonder if this

[jira] [Comment Edited] (BEAM-1777) If PipelineEnforcement throws an exception after Pipeline.run() fails, it overwrites the original failure

[ https://issues.apache.org/jira/browse/BEAM-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956479#comment-15956479 ] Stas Levin edited comment on BEAM-1777 at 4/5/17 8:00 AM: -- [~tgroh] since I was

[jira] [Commented] (BEAM-1777) If PipelineEnforcement throws an exception after Pipeline.run() fails, it overwrites the original failure

[ https://issues.apache.org/jira/browse/BEAM-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956479#comment-15956479 ] Stas Levin commented on BEAM-1777: -- [~tgroh] Since I was unable to come up with a proper test for this,

[jira] [Comment Edited] (BEAM-1777) If PipelineEnforcement throws an exception after Pipeline.run() fails, it overwrites the original failure

[ https://issues.apache.org/jira/browse/BEAM-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956479#comment-15956479 ] Stas Levin edited comment on BEAM-1777 at 4/5/17 8:01 AM: -- [~tgroh] since I was

[jira] [Updated] (BEAM-1048) Spark Runner streaming batch duration does not include duration of reading from source

[ https://issues.apache.org/jira/browse/BEAM-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1048: - Fix Version/s: First stable release > Spark Runner streaming batch duration does not include duration of

[jira] [Resolved] (BEAM-1048) Spark Runner streaming batch duration does not include duration of reading from source

[ https://issues.apache.org/jira/browse/BEAM-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-1048. -- Resolution: Workaround > Spark Runner streaming batch duration does not include duration of reading >

[jira] [Commented] (BEAM-1048) Spark Runner streaming batch duration does not include duration of reading from source

[ https://issues.apache.org/jira/browse/BEAM-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952616#comment-15952616 ] Stas Levin commented on BEAM-1048: -- While batch duration is still (and probably won't be) reported as part

[jira] [Assigned] (BEAM-1295) Annotations are not properly rendered in JavaDoc when using {@code}

[ https://issues.apache.org/jira/browse/BEAM-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-1295: Assignee: (was: Stas Levin) > Annotations are not properly rendered in JavaDoc when using

[jira] [Comment Edited] (BEAM-1712) TestPipeline.run doesn't actually waitUntilFinish

[ https://issues.apache.org/jira/browse/BEAM-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923650#comment-15923650 ] Stas Levin edited comment on BEAM-1712 at 3/14/17 6:20 AM: --- [A related

[jira] [Commented] (BEAM-1712) TestPipeline.run doesn't actually waitUntilFinish

[ https://issues.apache.org/jira/browse/BEAM-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923650#comment-15923650 ] Stas Levin commented on BEAM-1712: -- [A related

[jira] [Created] (BEAM-1713) {{SparkRuntimeContext}} instances are leaking via {{StateSpecFunctions#mapSourceFunction}}

Stas Levin created BEAM-1713: Summary: {{SparkRuntimeContext}} instances are leaking via {{StateSpecFunctions#mapSourceFunction}} Key: BEAM-1713 URL: https://issues.apache.org/jira/browse/BEAM-1713

[jira] [Assigned] (BEAM-1713) {{SparkRuntimeContext}} instances are leaking via {{StateSpecFunctions#mapSourceFunction}}

[ https://issues.apache.org/jira/browse/BEAM-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-1713: Assignee: Stas Levin (was: Amit Sela) > {{SparkRuntimeContext}} instances are leaking via >

[jira] [Updated] (BEAM-1713) SparkRuntimeContext instances are leaking via StateSpecFunctions#mapSourceFunction

[ https://issues.apache.org/jira/browse/BEAM-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1713: - Summary: SparkRuntimeContext instances are leaking via StateSpecFunctions#mapSourceFunction (was:

[jira] [Updated] (BEAM-1713) SparkRuntimeContext instances are leaking via StateSpecFunctions#mapSourceFunction

[ https://issues.apache.org/jira/browse/BEAM-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1713: - Description: When creating an anonymous class like so: {code:java}new Iterable() {...}{code} it is

[jira] [Updated] (BEAM-1557) Separate TestPipeline into 2 versions: one for users, and one for sdk/runner developers

[ https://issues.apache.org/jira/browse/BEAM-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-1557: - Description: At the moment, {{TestPipeline}} enforces some usage patterns, that may be too strict for non

[jira] [Commented] (BEAM-2671) CreateStreamTest.testFirstElementLate validatesRunner test fails on Spark runner

[ https://issues.apache.org/jira/browse/BEAM-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129014#comment-16129014 ] Stas Levin commented on BEAM-2671: -- I believe I've been able to pinpoint the problem and am working

[jira] [Comment Edited] (BEAM-2671) CreateStreamTest.testFirstElementLate validatesRunner test fails on Spark runner

[ https://issues.apache.org/jira/browse/BEAM-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129014#comment-16129014 ] Stas Levin edited comment on BEAM-2671 at 8/16/17 4:13 PM: --- I believe I've been

[jira] [Commented] (BEAM-2671) CreateStreamTest.testFirstElementLate validatesRunner test fails on Spark runner

[ https://issues.apache.org/jira/browse/BEAM-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124897#comment-16124897 ] Stas Levin commented on BEAM-2671: -- [~kenn], could you elaborate on when there might be a race, and what

[jira] [Assigned] (BEAM-2670) ParDoTest.testPipelineOptionsParameter* validatesRunner tests fail on Spark runner

[ https://issues.apache.org/jira/browse/BEAM-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-2670: Assignee: Stas Levin (was: Amit Sela) > ParDoTest.testPipelineOptionsParameter* validatesRunner

[jira] [Commented] (BEAM-1777) If PipelineEnforcement throws an exception after Pipeline.run() fails, it overwrites the original failure

[ https://issues.apache.org/jira/browse/BEAM-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15986425#comment-15986425 ] Stas Levin commented on BEAM-1777: -- [~tgroh] do you believe we can mark this one as resolved? > If

[jira] [Created] (BEAM-2092) MicrobatchSource can be relieved of some of its methods since it's never used as an actual BoundedSource

Stas Levin created BEAM-2092: Summary: MicrobatchSource can be relieved of some of its methods since it's never used as an actual BoundedSource Key: BEAM-2092 URL: https://issues.apache.org/jira/browse/BEAM-2092

[jira] [Created] (BEAM-2072) MicrobatchSource.reader stops reading after reaching maxNumRecords for the first time

Stas Levin created BEAM-2072: Summary: MicrobatchSource.reader stops reading after reaching maxNumRecords for the first time Key: BEAM-2072 URL: https://issues.apache.org/jira/browse/BEAM-2072 Project:

[jira] [Created] (BEAM-2073) Change SourceDStream.rateControlledMaxRecords() to better reflect its intention

Stas Levin created BEAM-2073: Summary: Change SourceDStream.rateControlledMaxRecords() to better reflect its intention Key: BEAM-2073 URL: https://issues.apache.org/jira/browse/BEAM-2073 Project: Beam

[jira] [Created] (BEAM-2074) SourceDStream's rate control mechanism may not work

Stas Levin created BEAM-2074: Summary: SourceDStream's rate control mechanism may not work Key: BEAM-2074 URL: https://issues.apache.org/jira/browse/BEAM-2074 Project: Beam Issue Type: Bug

[jira] [Commented] (BEAM-1676) SdkCoreApiSurfaceTest Failed When Directory Contains Space

[ https://issues.apache.org/jira/browse/BEAM-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990193#comment-15990193 ] Stas Levin commented on BEAM-1676: -- We can internalise (euphemism for copy-paste) the fixed {{ClassPath}}

[jira] [Comment Edited] (BEAM-1676) SdkCoreApiSurfaceTest Failed When Directory Contains Space

[ https://issues.apache.org/jira/browse/BEAM-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990193#comment-15990193 ] Stas Levin edited comment on BEAM-1676 at 4/30/17 11:32 AM: We can internalize

[jira] [Comment Edited] (BEAM-1676) SdkCoreApiSurfaceTest Failed When Directory Contains Space

[ https://issues.apache.org/jira/browse/BEAM-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990193#comment-15990193 ] Stas Levin edited comment on BEAM-1676 at 4/30/17 11:31 AM: We can internalize

[jira] [Updated] (BEAM-2095) The hasNext method of the iterator returned by SourceRDD#compute is not idempotent

[ https://issues.apache.org/jira/browse/BEAM-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-2095: - Summary: The hasNext method of the iterator returned by SourceRDD#compute is not idempotent (was:

[jira] [Comment Edited] (BEAM-2095) The hasNext method of the iterator returned by SourceRDD#compute is not idempotent

[ https://issues.apache.org/jira/browse/BEAM-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006299#comment-16006299 ] Stas Levin edited comment on BEAM-2095 at 5/11/17 12:01 PM: Hi Arvid, Sorry I

[jira] [Commented] (BEAM-2095) The hasNext method of the iterator returned by SourceRDD#compute is not idempotent

[ https://issues.apache.org/jira/browse/BEAM-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006299#comment-16006299 ] Stas Levin commented on BEAM-2095: -- Sorry I did not provide any context here. I was hoping you'd be

[jira] [Comment Edited] (BEAM-2095) The hasNext method of the iterator returned by SourceRDD#compute is not idempotent

[ https://issues.apache.org/jira/browse/BEAM-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006299#comment-16006299 ] Stas Levin edited comment on BEAM-2095 at 5/11/17 12:04 PM: Hi Arvid, Sorry I

[jira] [Resolved] (BEAM-2095) The hasNext method of the iterator returned by SourceRDD#compute is not idempotent

[ https://issues.apache.org/jira/browse/BEAM-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-2095. -- Resolution: Fixed Fix Version/s: 2.1.0 > The hasNext method of the iterator returned by

[jira] [Commented] (BEAM-2095) The hasNext method of the iterator returned by SourceRDD#compute is not idempotent

[ https://issues.apache.org/jira/browse/BEAM-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002206#comment-16002206 ] Stas Levin commented on BEAM-2095: -- [~arvid heise] this fix is currently in the master branch and will

[jira] [Assigned] (BEAM-1712) TestPipeline.run should perhaps waitUntilFinish

[ https://issues.apache.org/jira/browse/BEAM-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-1712: Assignee: (was: Stas Levin) > TestPipeline.run should perhaps waitUntilFinish >

[jira] [Assigned] (BEAM-2464) Create.of(...) does not work as expected when runner is configured to streaming mode

[ https://issues.apache.org/jira/browse/BEAM-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin reassigned BEAM-2464: Assignee: Stas Levin (was: Amit Sela) > Create.of(...) does not work as expected when runner is

[jira] [Created] (BEAM-2464) Create.of(...) is not properly handled when runner is configured to streaming mode

Stas Levin created BEAM-2464: Summary: Create.of(...) is not properly handled when runner is configured to streaming mode Key: BEAM-2464 URL: https://issues.apache.org/jira/browse/BEAM-2464 Project: Beam

[jira] [Updated] (BEAM-2464) Create.of(...) does not work as expected when runner is configured to streaming mode

[ https://issues.apache.org/jira/browse/BEAM-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin updated BEAM-2464: - Summary: Create.of(...) does not work as expected when runner is configured to streaming mode (was:

[jira] [Resolved] (BEAM-2072) MicrobatchSource.reader stops reading after reaching maxNumRecords for the first time

[ https://issues.apache.org/jira/browse/BEAM-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-2072. -- Resolution: Fixed Fix Version/s: First stable release > MicrobatchSource.reader stops reading

[jira] [Resolved] (BEAM-2073) Change SourceDStream.rateControlledMaxRecords() to better reflect its intention

[ https://issues.apache.org/jira/browse/BEAM-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-2073. -- Resolution: Fixed Fix Version/s: First stable release > Change

[jira] [Resolved] (BEAM-2074) SourceDStream's rate control mechanism may not work

[ https://issues.apache.org/jira/browse/BEAM-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stas Levin resolved BEAM-2074. -- Resolution: Fixed Fix Version/s: First stable release > SourceDStream's rate control mechanism

  1   2   >