[jira] [Created] (SAMZA-1757) Tests in samza-api which are written in Scala are not triggered

Cameron Lee created SAMZA-1757: -- Summary: Tests in samza-api which are written in Scala are not triggered Key: SAMZA-1757 URL: https://issues.apache.org/jira/browse/SAMZA-1757 Project: Samza

samza git commit: Minor: Changing tests which use resource files to use Class.getResource instead of File to get the path to the resource; without this change, these tests fail when run in the IDE

Repository: samza Updated Branches: refs/heads/master 187ec5f2f -> c8b776ec1 Minor: Changing tests which use resource files to use Class.getResource instead of File to get the path to the resource; without this change, these tests fail when run in the IDE Author: Cameron Lee Reviewers:

[jira] [Resolved] (SAMZA-1718) Simplify coordination state in Zookeeper

[ https://issues.apache.org/jira/browse/SAMZA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadish resolved SAMZA-1718. - Resolution: Fixed > Simplify coordination state in Zookeeper >

[jira] [Commented] (SAMZA-1718) Simplify coordination state in Zookeeper

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

samza git commit: SAMZA-1718: Simplify management of Zookeeper coordination state

Repository: samza Updated Branches: refs/heads/master 11afae3fd -> 187ec5f2f SAMZA-1718: Simplify management of Zookeeper coordination state 1. Currently coordination related state is spread across several Zookeeper classes. There are also back-and-forth flows that exist between the

samza git commit: Fixed failed unit tests in TestCachingTable

Repository: samza Updated Branches: refs/heads/master cdeea9015 -> 11afae3fd Fixed failed unit tests in TestCachingTable This is due to the recent refactoring of table metrics, for some reason running build locally didn't catch these failed tests. Author: Wei Song Author: Cameron Lee

[jira] [Commented] (SAMZA-1748) Standalone failure tests.

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

samza git commit: SAMZA-1748: Standalone failure tests.

Repository: samza Updated Branches: refs/heads/master ff251405b -> cdeea9015 SAMZA-1748: Standalone failure tests. In the standalone model, a processor can leave and join the group at any point in time. This processor reshuffle is referred to as rebalancing which results in task(work)

[jira] [Reopened] (SAMZA-1724) Guarantee exit from ApplicationRunnerMain during deploys

[ https://issues.apache.org/jira/browse/SAMZA-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron Lee reopened SAMZA-1724: Reopening, as the changes to ApplicationRunnerMain caused the issues described in

[jira] [Resolved] (SAMZA-1756) System exit calls in ApplicationRunnerMain break ProcessJob and cause unit tests to get skipped

[ https://issues.apache.org/jira/browse/SAMZA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron Lee resolved SAMZA-1756. Resolution: Fixed > System exit calls in ApplicationRunnerMain break ProcessJob and cause unit >

[jira] [Commented] (SAMZA-1756) System exit calls in ApplicationRunnerMain break ProcessJob and cause unit tests to get skipped

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

samza git commit: SAMZA-1756: System exit calls in ApplicationRunnerMain break ProcessJob and cause unit tests to get skipped

Repository: samza Updated Branches: refs/heads/master 15c5a1a7e -> ff251405b SAMZA-1756: System exit calls in ApplicationRunnerMain break ProcessJob and cause unit tests to get skipped Author: Cameron Lee Reviewers: Xinyu Liu Closes #561 from cameronlee314/app_runner_main_exit Project:

[jira] [Commented] (SAMZA-1756) System exit calls in ApplicationRunnerMain break ProcessJob and cause unit tests to get skipped

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

samza git commit: SAMZA-1648: Integration Test Framework & Collection Stream Impl

Repository: samza Updated Branches: refs/heads/master 991ed99aa -> 15c5a1a7e SAMZA-1648: Integration Test Framework & Collection Stream Impl This patch provides the following: - TestRunner: Tesing Wrapper to run Samza job - CollectionStream: Acts as a stream descriptor for in memory

[jira] [Updated] (SAMZA-1756) System exit calls in ApplicationRunnerMain break ProcessJob and cause unit tests to get skipped

[ https://issues.apache.org/jira/browse/SAMZA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron Lee updated SAMZA-1756: --- Description: A recent change from SAMZA-1724 introduced a System.exit call at the end of

[jira] [Updated] (SAMZA-1756) System exit calls in ApplicationRunnerMain break ProcessJob and cause unit tests to get skipped

[ https://issues.apache.org/jira/browse/SAMZA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron Lee updated SAMZA-1756: --- Summary: System exit calls in ApplicationRunnerMain break ProcessJob and cause unit tests to get

[jira] [Commented] (SAMZA-1753) Add set/get timestamp for IncomingMessageEnvelope from the kafka event

[ https://issues.apache.org/jira/browse/SAMZA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520748#comment-16520748 ] Boris Shkolnik commented on SAMZA-1753: --- Sometimes we need to have access to the Kafka record

[jira] [Commented] (SAMZA-1726) Isolate InMemorySystem Factory to run separately per job

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

samza git commit: SAMZA-1726: Isolate InMemorySystemFactory to run separately per job

Repository: samza Updated Branches: refs/heads/master 42b187a21 -> 991ed99aa SAMZA-1726: Isolate InMemorySystemFactory to run separately per job Tested by running the corresponding integration and unit tests Author: sanil15 Reviewers: Xinyu Liu Closes #532 from Sanil15/SAMZA-1726

[jira] [Created] (SAMZA-1756) ProcessJob no longer works since ApplicationRunnerMain does a System.exit

Cameron Lee created SAMZA-1756: -- Summary: ProcessJob no longer works since ApplicationRunnerMain does a System.exit Key: SAMZA-1756 URL: https://issues.apache.org/jira/browse/SAMZA-1756 Project: Samza