[jira] [Moved] (APEXMALHAR-2118) Enhance Kafka 0.9 input operator to support starting from custom offsets in multiple partitions

["Thomas Weise (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/APEXMALHAR-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Weise moved APEXCORE-472 to APEXMALHAR-2118:
---------------------------------------------------

    Affects Version/s:     (was: 3.3.1)
                       3.3.1
             Workflow: Default workflow, editable Closed status  (was: jira)
                  Key: APEXMALHAR-2118  (was: APEXCORE-472)
              Project: Apache Apex Malhar  (was: Apache Apex Core)

> Enhance Kafka 0.9 input operator to support starting from custom offsets in multiple partitions
> -----------------------------------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2118
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2118
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>    Affects Versions: 3.3.1
>            Reporter: Ananth
>
> Enhance Kafka 0.9 input operator to support starting from custom offsets in multiple partitions
> This is needed for multiple reasons: 
> Assuming kafka is hosting data that does not expire soon but after an extended period of time by configuring the TTL :
> Example use cases include 
> - Bugs introduced in a middle of a data stream from an upstream application writing to kafka and downstream Apex app needs to process data
> - Feature enhancements to business logic in an Operator that needs a code update and need to process data from a certain time that a developer knows is from a certain offset in kafka



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)