apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkata Rama Puppala (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXMALHAR-2522) Add support for specifying begin and end offsets for each partitions
Date Tue, 11 Jul 2017 19:31:00 GMT

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

Venkata Rama Puppala updated APEXMALHAR-2522:
---------------------------------------------
    Description: 
Add support for specifying begin and end offsets for different partitions which when reached
would result in the application shutting itself down. It would be good to have the ability
to set these dynamically.

Throw shutdown exception when committed offset reaches end offset.

Note:

The feature that was added to provide initial offsets, is requiring a full list of all the
kafka nodes in the cluster and in the right order. Can this tight restriction be removed or
relaxed?

  was:
Add support for specifying begin and end offsets for different partitions which when reached
would result in the application shutting itself down. It would be good to have the ability
to set these dynamically.

Throw shutdown exception when committed offset reaches end offset.


> Add support for specifying begin and end offsets for each partitions
> --------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2522
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2522
>             Project: Apache Apex Malhar
>          Issue Type: New Feature
>            Reporter: Venkata Rama Puppala
>            Assignee: Sandesh
>
> Add support for specifying begin and end offsets for different partitions which when
reached would result in the application shutting itself down. It would be good to have the
ability to set these dynamically.
> Throw shutdown exception when committed offset reaches end offset.
> Note:
> The feature that was added to provide initial offsets, is requiring a full list of all
the kafka nodes in the cluster and in the right order. Can this tight restriction be removed
or relaxed?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message