[jira] [Updated] (SAMZA-1827) Window operator should fire triggers during startup

2018-08-24 Thread Jagadish (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadish updated SAMZA-1827: Description: Currently, all pending triggers are fired during shut-down when flushing the operator state.

[jira] [Created] (SAMZA-1827) Window operator should fire triggers during startup

2018-08-24 Thread Jagadish (JIRA)
Jagadish created SAMZA-1827: --- Summary: Window operator should fire triggers during startup Key: SAMZA-1827 URL: https://issues.apache.org/jira/browse/SAMZA-1827 Project: Samza Issue Type: Bug

[jira] [Commented] (SAMZA-1826) Unit test for table tests failed with assert errors on PageViewToProfileJoinFunction

2018-08-24 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592337#comment-16592337 ] ASF GitHub Bot commented on SAMZA-1826: --- GitHub user nickpan47 opened a pull request:

[jira] [Created] (SAMZA-1826) Unit test for table tests failed with assert errors on PageViewToProfileJoinFunction

2018-08-24 Thread Yi Pan (Data Infrastructure) (JIRA)
Yi Pan (Data Infrastructure) created SAMZA-1826: --- Summary: Unit test for table tests failed with assert errors on PageViewToProfileJoinFunction Key: SAMZA-1826 URL:

[jira] [Commented] (SAMZA-1821) Fetching systemStream configs causes duplicate key exception

2018-08-24 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592066#comment-16592066 ] ASF GitHub Bot commented on SAMZA-1821: --- GitHub user weiqingy opened a pull request:

[jira] [Resolved] (SAMZA-1825) SamzaSQL testendToEnd is failing

2018-08-24 Thread Srinivasulu Punuru (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivasulu Punuru resolved SAMZA-1825. --- Resolution: Fixed > SamzaSQL testendToEnd is failing >

samza git commit: SAMZA-1825: Fix for the test failure

2018-08-24 Thread srinivasulu
Repository: samza Updated Branches: refs/heads/master 25d943f1c -> 4394b89ef SAMZA-1825: Fix for the test failure Project: http://git-wip-us.apache.org/repos/asf/samza/repo Commit: http://git-wip-us.apache.org/repos/asf/samza/commit/4394b89e Tree:

[jira] [Created] (SAMZA-1825) SamzaSQL testendToEnd is failing

2018-08-24 Thread Srinivasulu Punuru (JIRA)
Srinivasulu Punuru created SAMZA-1825: - Summary: SamzaSQL testendToEnd is failing Key: SAMZA-1825 URL: https://issues.apache.org/jira/browse/SAMZA-1825 Project: Samza Issue Type: Bug

[jira] [Commented] (SAMZA-1824) Samza AM does not handle some failures during container launch

2018-08-24 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591946#comment-16591946 ] ASF GitHub Bot commented on SAMZA-1824: --- GitHub user vjagadish1989 opened a pull request:

[jira] [Updated] (SAMZA-1371) Some Samza Containers get stuck at "Starting BrokerProxy for hostname:portnum" while others seem to be fine

2018-08-24 Thread Jagadish (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadish updated SAMZA-1371: Description: We have multiple Samza apps using local store that have this issue. Some containers get

[jira] [Updated] (SAMZA-1371) Some Samza Containers get stuck at "Starting BrokerProxy for hostname:portnum" while others seem to be fine

2018-08-24 Thread Jagadish (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadish updated SAMZA-1371: Description: I noticed this behavior in the AM today where it fails to allocate a new container on

[jira] [Updated] (SAMZA-1371) Some Samza Containers get stuck at "Starting BrokerProxy for hostname:portnum" while others seem to be fine

2018-08-24 Thread Jagadish (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadish updated SAMZA-1371: Description: I noticed this behavior in the AM today where it fails to allocate a new container on

[jira] [Created] (SAMZA-1823) Handle errors when launching containers

2018-08-24 Thread Jagadish (JIRA)
Jagadish created SAMZA-1823: --- Summary: Handle errors when launching containers Key: SAMZA-1823 URL: https://issues.apache.org/jira/browse/SAMZA-1823 Project: Samza Issue Type: Bug

[jira] [Updated] (SAMZA-1822) Samza 0.14.1 not correctly handling OffsetOutOfRangeException exception

2018-08-24 Thread DM (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DM updated SAMZA-1822: -- Description:   Samza is requesting for an Kafka partition offset that is too old (i.e Kafka log has moved ahead). We

[jira] [Updated] (SAMZA-1822) Samza 0.14.1 not correctly handling OffsetOutOfRangeException exception

2018-08-24 Thread DM (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DM updated SAMZA-1822: -- Description:   Samza is requesting for an Kafka partition offset that is too old (i.e Kafka log has moved ahead). We

[jira] [Created] (SAMZA-1822) Samza 0.14.1 not correctly handling OffsetOutOfRangeException exception

2018-08-24 Thread DM (JIRA)
DM created SAMZA-1822: - Summary: Samza 0.14.1 not correctly handling OffsetOutOfRangeException exception Key: SAMZA-1822 URL: https://issues.apache.org/jira/browse/SAMZA-1822 Project: Samza Issue Type:

[jira] [Updated] (SAMZA-1821) Fetching systemStream configs causes duplicate key exception

2018-08-24 Thread Weiqing Yang (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated SAMZA-1821: Fix Version/s: 1.0 > Fetching systemStream configs causes duplicate key exception >