[jira] [Created] (SAMZA-967) Add HDFS system consumer to Samza

2016-06-14 Thread Hai (JIRA)
Hai created SAMZA-967: - Summary: Add HDFS system consumer to Samza Key: SAMZA-967 URL: https://issues.apache.org/jira/browse/SAMZA-967 Project: Samza Issue Type: Sub-task Reporter: Hai

[jira] [Updated] (SAMZA-967) Add HDFS system consumer to Samza

2016-08-16 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-967: -- Attachment: HDFSSystemConsumer.pdf > Add HDFS system consumer to Samza > - > >

[jira] [Commented] (SAMZA-967) Add HDFS system consumer to Samza

2016-09-08 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475223#comment-15475223 ] Hai commented on SAMZA-967: --- [~navina] Thanks so much for your valuable feedback. Please take a look at the

[jira] [Updated] (SAMZA-967) Add HDFS system consumer to Samza

2016-09-08 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-967: -- Attachment: HDFSSystemConsumer.pdf > Add HDFS system consumer to Samza > - > >

[jira] [Created] (SAMZA-1026) HDFS System Producer should not have Kafka dependency

2016-09-28 Thread Hai (JIRA)
Hai created SAMZA-1026: -- Summary: HDFS System Producer should not have Kafka dependency Key: SAMZA-1026 URL: https://issues.apache.org/jira/browse/SAMZA-1026 Project: Samza Issue Type: Sub-task

[jira] [Created] (SAMZA-1025) Documentation page for HDFS System Consumer feature

2016-09-28 Thread Hai (JIRA)
Hai created SAMZA-1025: -- Summary: Documentation page for HDFS System Consumer feature Key: SAMZA-1025 URL: https://issues.apache.org/jira/browse/SAMZA-1025 Project: Samza Issue Type: Sub-task

[jira] [Created] (SAMZA-1032) create staging directory in the job level instead of the YARN module

2016-10-04 Thread Hai (JIRA)
Hai created SAMZA-1032: -- Summary: create staging directory in the job level instead of the YARN module Key: SAMZA-1032 URL: https://issues.apache.org/jira/browse/SAMZA-1032 Project: Samza Issue Type:

[jira] [Created] (SAMZA-1034) Support LATEST path and single file as the input of HDFSSystemConsumer

2016-10-07 Thread Hai (JIRA)
Hai created SAMZA-1034: -- Summary: Support LATEST path and single file as the input of HDFSSystemConsumer Key: SAMZA-1034 URL: https://issues.apache.org/jira/browse/SAMZA-1034 Project: Samza Issue

[jira] [Commented] (SAMZA-1034) Support LATEST path and single file as the input of HDFSSystemConsumer

2016-10-07 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556764#comment-15556764 ] Hai commented on SAMZA-1034: https://reviews.apache.org/r/52660/ > Support LATEST path and single file as the

[jira] [Commented] (SAMZA-1025) Documentation page for HDFS System Consumer feature

2016-10-07 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556766#comment-15556766 ] Hai commented on SAMZA-1025: https://reviews.apache.org/r/52570/ > Documentation page for HDFS System

[jira] [Commented] (SAMZA-1034) Support LATEST path and single file as the input of HDFSSystemConsumer

2016-10-10 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563296#comment-15563296 ] Hai commented on SAMZA-1034: On second thought, this is probably not a very interesting feature on open

[jira] [Resolved] (SAMZA-1463) Disable flaky tests in hdfs

2017-10-16 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1463. Resolution: Fixed > Disable flaky tests in hdfs > --- > > Key: SAMZA-1463 >

[jira] [Updated] (SAMZA-1471) No polling for end-of-stream partitions in SystemConsumers

2017-10-25 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1471: --- Labels: samzaHadoop (was: ) > No polling for end-of-stream partitions in SystemConsumers >

[jira] [Created] (SAMZA-1706) lazy initialization for eventhub system producer

2018-05-08 Thread Hai (JIRA)
Hai created SAMZA-1706: -- Summary: lazy initialization for eventhub system producer Key: SAMZA-1706 URL: https://issues.apache.org/jira/browse/SAMZA-1706 Project: Samza Issue Type: Improvement

[jira] [Resolved] (SAMZA-1706) lazy initialization for eventhub system producer

2018-05-09 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1706. Resolution: Fixed > lazy initialization for eventhub system producer >

[jira] [Created] (SAMZA-1690) AsyncSystemProducer should enforce max pending sends

2018-04-27 Thread Hai (JIRA)
Hai created SAMZA-1690: -- Summary: AsyncSystemProducer should enforce max pending sends Key: SAMZA-1690 URL: https://issues.apache.org/jira/browse/SAMZA-1690 Project: Samza Issue Type: Improvement

[jira] [Resolved] (SAMZA-1688) use per partition eventhubs client

2018-04-27 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1688. Resolution: Fixed > use per partition eventhubs client > -- > >

[jira] [Created] (SAMZA-1708) investigate shutdown timeout on eventhubs producer

2018-05-09 Thread Hai (JIRA)
Hai created SAMZA-1708: -- Summary: investigate shutdown timeout on eventhubs producer Key: SAMZA-1708 URL: https://issues.apache.org/jira/browse/SAMZA-1708 Project: Samza Issue Type: Improvement

[jira] [Resolved] (SAMZA-1741) EH consumer shutdown taking too long and causing rebalance to fail

2018-06-08 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1741. Resolution: Fixed > EH consumer shutdown taking too long and causing rebalance to fail >

[jira] [Created] (SAMZA-1741) EH consumer shutdown taking too long and causing rebalance to fail

2018-06-06 Thread Hai (JIRA)
Hai created SAMZA-1741: -- Summary: EH consumer shutdown taking too long and causing rebalance to fail Key: SAMZA-1741 URL: https://issues.apache.org/jira/browse/SAMZA-1741 Project: Samza Issue Type:

[jira] [Updated] (SAMZA-1673) EventHub: readLatency metric returns negative value

2018-04-30 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1673: --- Fix Version/s: 0.14.1 > EventHub: readLatency metric returns negative value >

[jira] [Updated] (SAMZA-1675) EventHub: Log the metadata that we are fetching from the event hubs.

2018-04-30 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1675: --- Fix Version/s: 0.14.1 > EventHub: Log the metadata that we are fetching from the event hubs. >

[jira] [Updated] (SAMZA-1625) EventHub systemAdmin is swallowing exceptions

2018-04-30 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1625: --- Fix Version/s: 0.14.1 > EventHub systemAdmin is swallowing exceptions > -

[jira] [Updated] (SAMZA-1676) miscellaneous fix and improvement for eventhubs system

2018-04-30 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1676: --- Fix Version/s: 0.14.1 > miscellaneous fix and improvement for eventhubs system >

[jira] [Updated] (SAMZA-1624) EventHub system should prefix the configs with senstive for SasKey and SasToken

2018-04-30 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1624: --- Fix Version/s: 0.14.1 > EventHub system should prefix the configs with senstive for SasKey and > SasToken >

[jira] [Updated] (SAMZA-1674) EventHub: Rename readLatency to consumptionLagMs

2018-04-30 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1674: --- Fix Version/s: 0.14.1 > EventHub: Rename readLatency to consumptionLagMs >

[jira] [Resolved] (SAMZA-1785) implement retry logic in eventhubs consumer

2018-07-30 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1785. Resolution: Fixed > implement retry logic in eventhubs consumer > --- > >

[jira] [Updated] (SAMZA-1785) implement retry logic in eventhubs consumer

2018-07-26 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1785: --- Summary: implement retry logic in eventhubs consumer (was: ignore timeout exception during receiver renew in

[jira] [Commented] (SAMZA-1785) implement retry logic in eventhubs consumer

2018-07-26 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558644#comment-16558644 ] Hai commented on SAMZA-1785: We initially found TimeoutException but later on saw different exception

[jira] [Updated] (SAMZA-1794) setting application acl in launch context for secured YARN cluster

2018-07-31 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1794: --- Description: Currently we don't set application acl for container launch context. See

[jira] [Created] (SAMZA-1794) setting application acl in launch context for secured YARN cluster

2018-07-31 Thread Hai (JIRA)
Hai created SAMZA-1794: -- Summary: setting application acl in launch context for secured YARN cluster Key: SAMZA-1794 URL: https://issues.apache.org/jira/browse/SAMZA-1794 Project: Samza Issue Type:

[jira] [Resolved] (SAMZA-1794) setting application acl in launch context for secured YARN cluster

2018-08-01 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1794. Resolution: Fixed > setting application acl in launch context for secured YARN cluster >

[jira] [Created] (SAMZA-1775) EH consumer renew too frequently under transient exception

2018-07-19 Thread Hai (JIRA)
Hai created SAMZA-1775: -- Summary: EH consumer renew too frequently under transient exception Key: SAMZA-1775 URL: https://issues.apache.org/jira/browse/SAMZA-1775 Project: Samza Issue Type: Bug

[jira] [Resolved] (SAMZA-1775) EH consumer renew too frequently under transient exception

2018-07-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1775. Resolution: Fixed > EH consumer renew too frequently under transient exception >

[jira] [Created] (SAMZA-1785) ignore timeout exception during receiver renew in eventhubs consumer

2018-07-25 Thread Hai (JIRA)
Hai created SAMZA-1785: -- Summary: ignore timeout exception during receiver renew in eventhubs consumer Key: SAMZA-1785 URL: https://issues.apache.org/jira/browse/SAMZA-1785 Project: Samza Issue Type:

[jira] [Updated] (SAMZA-1708) investigate shutdown timeout on eventhubs producer

2018-08-29 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1708: --- Description: We oftentimes see timeout when trying to shutdown consumer/producer because the EH client times out

[jira] [Updated] (SAMZA-1708) investigate timeout exception in eventhubs client during shutdown

2018-08-29 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1708: --- Summary: investigate timeout exception in eventhubs client during shutdown (was: investigate shutdown timeout on

[jira] [Created] (SAMZA-1618) fix HdfsFileSystemAdapter to get files recursively

2018-03-13 Thread Hai (JIRA)
Hai created SAMZA-1618: -- Summary: fix HdfsFileSystemAdapter to get files recursively Key: SAMZA-1618 URL: https://issues.apache.org/jira/browse/SAMZA-1618 Project: Samza Issue Type: Bug

[jira] [Created] (SAMZA-1622) avro writer in hdfs system producer to support generic record

2018-03-15 Thread Hai (JIRA)
Hai created SAMZA-1622: -- Summary: avro writer in hdfs system producer to support generic record Key: SAMZA-1622 URL: https://issues.apache.org/jira/browse/SAMZA-1622 Project: Samza Issue Type: Bug

[jira] [Resolved] (SAMZA-1618) fix HdfsFileSystemAdapter to get files recursively

2018-03-13 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1618. Resolution: Fixed > fix HdfsFileSystemAdapter to get files recursively >

[jira] [Created] (SAMZA-1654) calculate the exact size of the AMQP message for skipping large message

2018-04-12 Thread Hai (JIRA)
Hai created SAMZA-1654: -- Summary: calculate the exact size of the AMQP message for skipping large message Key: SAMZA-1654 URL: https://issues.apache.org/jira/browse/SAMZA-1654 Project: Samza Issue

[jira] [Updated] (SAMZA-1674) EventHub: Rename readLatency to consumptionLagMs

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1674: --- Issue Type: Sub-task (was: Bug) Parent: SAMZA-1676 > EventHub: Rename readLatency to consumptionLagMs >

[jira] [Updated] (SAMZA-1673) EventHub: readLatency metric returns negative value

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1673: --- Issue Type: Sub-task (was: Bug) Parent: SAMZA-1676 > EventHub: readLatency metric returns negative value >

[jira] [Updated] (SAMZA-1625) EventHub systemAdmin is swallowing exceptions

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1625: --- Issue Type: Sub-task (was: Bug) Parent: SAMZA-1676 > EventHub systemAdmin is swallowing exceptions >

[jira] [Updated] (SAMZA-1675) EventHub: Log the metadata that we are fetching from the event hubs.

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1675: --- Issue Type: Sub-task (was: Bug) Parent: SAMZA-1676 > EventHub: Log the metadata that we are fetching from

[jira] [Assigned] (SAMZA-1625) EventHub systemAdmin is swallowing exceptions

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai reassigned SAMZA-1625: -- Assignee: Hai > EventHub systemAdmin is swallowing exceptions > -

[jira] [Assigned] (SAMZA-1674) EventHub: Rename readLatency to consumptionLagMs

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai reassigned SAMZA-1674: -- Assignee: Hai > EventHub: Rename readLatency to consumptionLagMs >

[jira] [Assigned] (SAMZA-1673) EventHub: readLatency metric returns negative value

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai reassigned SAMZA-1673: -- Assignee: Hai > EventHub: readLatency metric returns negative value >

[jira] [Assigned] (SAMZA-1675) EventHub: Log the metadata that we are fetching from the event hubs.

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai reassigned SAMZA-1675: -- Assignee: Hai > EventHub: Log the metadata that we are fetching from the event hubs. >

[jira] [Resolved] (SAMZA-1624) EventHub system should prefix the configs with senstive for SasKey and SasToken

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1624. Resolution: Fixed > EventHub system should prefix the configs with senstive for SasKey and > SasToken >

[jira] [Created] (SAMZA-1676) miscellaneous fix and improvement for eventhubs system

2018-04-20 Thread Hai (JIRA)
Hai created SAMZA-1676: -- Summary: miscellaneous fix and improvement for eventhubs system Key: SAMZA-1676 URL: https://issues.apache.org/jira/browse/SAMZA-1676 Project: Samza Issue Type: Improvement

[jira] [Updated] (SAMZA-1676) miscellaneous fix and improvement for eventhubs system

2018-04-20 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1676: --- Labels: EventHub (was: ) > miscellaneous fix and improvement for eventhubs system >

[jira] [Resolved] (SAMZA-1625) EventHub systemAdmin is swallowing exceptions

2018-04-24 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1625. Resolution: Fixed > EventHub systemAdmin is swallowing exceptions > - >

[jira] [Resolved] (SAMZA-1673) EventHub: readLatency metric returns negative value

2018-04-24 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1673. Resolution: Fixed > EventHub: readLatency metric returns negative value >

[jira] [Resolved] (SAMZA-1676) miscellaneous fix and improvement for eventhubs system

2018-04-24 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1676. Resolution: Fixed > miscellaneous fix and improvement for eventhubs system >

[jira] [Resolved] (SAMZA-1675) EventHub: Log the metadata that we are fetching from the event hubs.

2018-04-24 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1675. Resolution: Fixed > EventHub: Log the metadata that we are fetching from the event hubs. >

[jira] [Resolved] (SAMZA-1674) EventHub: Rename readLatency to consumptionLagMs

2018-04-24 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1674. Resolution: Fixed > EventHub: Rename readLatency to consumptionLagMs >

[jira] [Resolved] (SAMZA-1623) AvroDataFileHdfsWriter should include avro as the file suffix

2018-03-21 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1623. Resolution: Fixed > AvroDataFileHdfsWriter should include avro as the file suffix >

[jira] [Created] (SAMZA-1623) AvroDataFileHdfsWriter should include avro as the file suffix

2018-03-21 Thread Hai (JIRA)
Hai created SAMZA-1623: -- Summary: AvroDataFileHdfsWriter should include avro as the file suffix Key: SAMZA-1623 URL: https://issues.apache.org/jira/browse/SAMZA-1623 Project: Samza Issue Type: Task

[jira] [Updated] (SAMZA-1688) use per partition eventhubs client

2018-04-25 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai updated SAMZA-1688: --- Labels: EventHub (was: ) > use per partition eventhubs client > -- > >

[jira] [Created] (SAMZA-1688) use per partition eventhubs client

2018-04-25 Thread Hai (JIRA)
Hai created SAMZA-1688: -- Summary: use per partition eventhubs client Key: SAMZA-1688 URL: https://issues.apache.org/jira/browse/SAMZA-1688 Project: Samza Issue Type: Improvement Reporter:

[jira] [Created] (SAMZA-1914) out of range starting offset for EH consumer

2018-09-26 Thread Hai (JIRA)
Hai created SAMZA-1914: -- Summary: out of range starting offset for EH consumer Key: SAMZA-1914 URL: https://issues.apache.org/jira/browse/SAMZA-1914 Project: Samza Issue Type: Bug Reporter:

[jira] [Resolved] (SAMZA-1914) out of range starting offset for EH consumer

2018-09-26 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1914. Resolution: Fixed > out of range starting offset for EH consumer > >

[jira] [Resolved] (SAMZA-1870) HDFS system admin not handling END_OF_STREAM offset

2018-09-12 Thread Hai (JIRA)
[ https://issues.apache.org/jira/browse/SAMZA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai resolved SAMZA-1870. Resolution: Fixed > HDFS system admin not handling END_OF_STREAM offset >

[jira] [Created] (SAMZA-1870) HDFS system admin not handling END_OF_STREAM offset

2018-09-11 Thread Hai (JIRA)
Hai created SAMZA-1870: -- Summary: HDFS system admin not handling END_OF_STREAM offset Key: SAMZA-1870 URL: https://issues.apache.org/jira/browse/SAMZA-1870 Project: Samza Issue Type: Bug