[jira] [Commented] (SAMZA-1276) SamzaContainer does not take into account the custom metrics reporter passed by streamprocessor

[ https://issues.apache.org/jira/browse/SAMZA-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003888#comment-16003888 ] ASF GitHub Bot commented on SAMZA-1276: --- Github user asfgit closed the pull request at:

samza git commit: SAMZA-1276 : Adding customReporters passed by StreamProcessor into SamzaContainer

Repository: samza Updated Branches: refs/heads/master 8183781f2 -> c50dd080b SAMZA-1276 : Adding customReporters passed by StreamProcessor into SamzaContainer SamzaContainer is not adding custom reporters along side class-loaded reporters from config. This was missed in

[jira] [Commented] (SAMZA-1272) ZkCoordinationUtils deletes the entire Zk tree on reset

[ https://issues.apache.org/jira/browse/SAMZA-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003879#comment-16003879 ] ASF GitHub Bot commented on SAMZA-1272: --- Github user asfgit closed the pull request at:

[jira] [Resolved] (SAMZA-1272) ZkCoordinationUtils deletes the entire Zk tree on reset

[ https://issues.apache.org/jira/browse/SAMZA-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navina Ramesh resolved SAMZA-1272. -- Resolution: Fixed Issue resolved by pull request 173 [https://github.com/apache/samza/pull/173]

samza git commit: SAMZA-1272 : ZkCoordinationUtils deletes the entire Zk tree on reset

Repository: samza Updated Branches: refs/heads/master b815e6d91 -> 8183781f2 SAMZA-1272 : ZkCoordinationUtils deletes the entire Zk tree on reset * ZkCoordinationUtils has a reset interface that deletes the entire Zk tree. This is not desirable. * Also, fixed flakiness in unit test by unique

[jira] [Commented] (SAMZA-1258) HappyPathTesting. Single and multiple processors happy path.

[ https://issues.apache.org/jira/browse/SAMZA-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003861#comment-16003861 ] ASF GitHub Bot commented on SAMZA-1258: --- GitHub user sborya opened a pull request:

[jira] [Commented] (SAMZA-1276) SamzaContainer does not take into account the custom metrics reporter passed by streamprocessor

[ https://issues.apache.org/jira/browse/SAMZA-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003862#comment-16003862 ] ASF GitHub Bot commented on SAMZA-1276: --- GitHub user navina opened a pull request:

[jira] [Commented] (SAMZA-1270) Pull out MetricsReporter lifecycle from Container

[ https://issues.apache.org/jira/browse/SAMZA-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003842#comment-16003842 ] Navina Ramesh commented on SAMZA-1270: -- This issue is much harder than it seems. It feels like a

[jira] [Updated] (SAMZA-1270) Pull out MetricsReporter lifecycle from Container

[ https://issues.apache.org/jira/browse/SAMZA-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navina Ramesh updated SAMZA-1270: - Fix Version/s: 0.14.0 > Pull out MetricsReporter lifecycle from Container >

[jira] [Commented] (SAMZA-1185) Document async commit support in configuration table

[ https://issues.apache.org/jira/browse/SAMZA-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003756#comment-16003756 ] ASF GitHub Bot commented on SAMZA-1185: --- GitHub user shanthoosh opened a pull request:

[jira] [Resolved] (SAMZA-1274) Update kafka-python and kafka broker version for integration tests

[ https://issues.apache.org/jira/browse/SAMZA-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prateek Maheshwari resolved SAMZA-1274. --- Resolution: Fixed > Update kafka-python and kafka broker version for integration

[jira] [Resolved] (SAMZA-1275) Kafka throws when users configure replication.factor for Kafka default stream

[ https://issues.apache.org/jira/browse/SAMZA-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Maes resolved SAMZA-1275. -- Resolution: Fixed Issue resolved by pull request 176 [https://github.com/apache/samza/pull/176] >

[jira] [Commented] (SAMZA-1275) Kafka throws when users configure replication.factor for Kafka default stream

[ https://issues.apache.org/jira/browse/SAMZA-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003714#comment-16003714 ] ASF GitHub Bot commented on SAMZA-1275: --- Github user asfgit closed the pull request at:

samza git commit: SAMZA-1275: Kafka throws when users configure replication.factor for …

Repository: samza Updated Branches: refs/heads/master 279a2952d -> b815e6d91 SAMZA-1275: Kafka throws when users configure replication.factor for … …Kafka default stream Author: Jacob Maes Reviewers: Prateek Maheshwari , Xinyu Liu

[jira] [Updated] (SAMZA-1277) merge() operator should not require chaining.

[ https://issues.apache.org/jira/browse/SAMZA-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Maes updated SAMZA-1277: - Description: The current design forces users to do stuff like this (I can provide more than a few

[jira] [Resolved] (SAMZA-1246) ApplicatonRunner.stats() should include exception in case of failure

[ https://issues.apache.org/jira/browse/SAMZA-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyu Liu resolved SAMZA-1246. -- Resolution: Fixed Fix Version/s: 0.13.0 > ApplicatonRunner.stats() should include exception in

[jira] [Created] (SAMZA-1276) SamzaContainer does not take into account the custom metrics reporter passed by streamprocessor

Navina Ramesh created SAMZA-1276: Summary: SamzaContainer does not take into account the custom metrics reporter passed by streamprocessor Key: SAMZA-1276 URL: https://issues.apache.org/jira/browse/SAMZA-1276

samza git commit: SAMZA-1268: More javadoc cleanup for public APIs for 0.13 release

Repository: samza Updated Branches: refs/heads/master 9e2ee35d6 -> 279a2952d SAMZA-1268: More javadoc cleanup for public APIs for 0.13 release Author: Prateek Maheshwari Reviewers: Jacob Maes Closes #175 from prateekm/documentation-cleanup

[jira] [Commented] (SAMZA-1268) Javadoc cleanup for public APIs for 0.13 release

[ https://issues.apache.org/jira/browse/SAMZA-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003645#comment-16003645 ] ASF GitHub Bot commented on SAMZA-1268: --- Github user asfgit closed the pull request at:

[jira] [Commented] (SAMZA-1275) Kafka throws when users configure replication.factor for Kafka default stream

[ https://issues.apache.org/jira/browse/SAMZA-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003325#comment-16003325 ] ASF GitHub Bot commented on SAMZA-1275: --- GitHub user jmakes opened a pull request:

[jira] [Updated] (SAMZA-1275) Kafka throws when users configure replication.factor for Kafka default stream

[ https://issues.apache.org/jira/browse/SAMZA-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Maes updated SAMZA-1275: - Fix Version/s: 0.13.0 > Kafka throws when users configure replication.factor for Kafka default stream >

[jira] [Updated] (SAMZA-1275) Kafka throws when users configure replication.factor for Kafka default stream

[ https://issues.apache.org/jira/browse/SAMZA-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Maes updated SAMZA-1275: - Affects Version/s: 0.13.0 > Kafka throws when users configure replication.factor for Kafka default stream

[jira] [Created] (SAMZA-1275) Kafka throws when users configure replication.factor for Kafka default stream

Jake Maes created SAMZA-1275: Summary: Kafka throws when users configure replication.factor for Kafka default stream Key: SAMZA-1275 URL: https://issues.apache.org/jira/browse/SAMZA-1275 Project: Samza

[jira] [Commented] (SAMZA-1268) Javadoc cleanup for public APIs for 0.13 release

[ https://issues.apache.org/jira/browse/SAMZA-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003277#comment-16003277 ] ASF GitHub Bot commented on SAMZA-1268: --- GitHub user prateekm opened a pull request:

[jira] [Commented] (SAMZA-1274) Update kafka-python and kafka broker version for integration tests

[ https://issues.apache.org/jira/browse/SAMZA-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003148#comment-16003148 ] ASF GitHub Bot commented on SAMZA-1274: --- Github user asfgit closed the pull request at:

samza git commit: SAMZA-1274; Update kafka-python and kafka broker version for integration tests

Repository: samza Updated Branches: refs/heads/master d89d1ba3a -> 9e2ee35d6 SAMZA-1274; Update kafka-python and kafka broker version for integration tests Author: Prateek Maheshwari Reviewers: Jagadish Closes #174 from

[jira] [Commented] (SAMZA-1274) Update kafka-python and kafka broker version for integration tests

[ https://issues.apache.org/jira/browse/SAMZA-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003107#comment-16003107 ] ASF GitHub Bot commented on SAMZA-1274: --- GitHub user prateekm opened a pull request:

[jira] [Created] (SAMZA-1274) Update kafka-python and kafka broker version for integration tests

Prateek Maheshwari created SAMZA-1274: - Summary: Update kafka-python and kafka broker version for integration tests Key: SAMZA-1274 URL: https://issues.apache.org/jira/browse/SAMZA-1274 Project:

[jira] [Resolved] (SAMZA-1273) Make StreamConfig.getStreamIds() public

[ https://issues.apache.org/jira/browse/SAMZA-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyu Liu resolved SAMZA-1273. -- Resolution: Fixed Fix Version/s: 0.13.0 > Make StreamConfig.getStreamIds() public >

[jira] [Commented] (SAMZA-1273) Make StreamConfig.getStreamIds() public

[ https://issues.apache.org/jira/browse/SAMZA-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002977#comment-16002977 ] ASF GitHub Bot commented on SAMZA-1273: --- Github user asfgit closed the pull request at:

samza git commit: SAMZA-1273: Make StreamConfig.getStreamIds() public

Repository: samza Updated Branches: refs/heads/master 634e568cd -> d89d1ba3a SAMZA-1273: Make StreamConfig.getStreamIds() public Making StreamConfig.getStreamIds() public so config provider can scan through all the configured streams and expand some properties if needed. Author: Xinyu Liu