[
https://issues.apache.org/jira/browse/NIFI-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-791:
----------------------------
Description:
We should expose the different configuration options offered by Kafka in the
GetKafka Processor (and PutKafka Processor, for that matter).
We should also remove the hardcoded value for the auto.commit.offsets and
instead provide a property that allows the user to specify whether or not the
offsets are committed. From an email on the dev mailing list:
In the case of auto.commit.enable - we had a scenario during our last
deploy in which we did not commit the offsets we read at all. This
atypical. This is in the case of a Lambda-like architecture in which we use
S3 to provide historical data to repopulate the near real-time datastore
during a deploy.
> Expose more configuration options for GetKafka processor
> --------------------------------------------------------
>
> Key: NIFI-791
> URL: https://issues.apache.org/jira/browse/NIFI-791
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
>
> We should expose the different configuration options offered by Kafka in the
> GetKafka Processor (and PutKafka Processor, for that matter).
> We should also remove the hardcoded value for the auto.commit.offsets and
> instead provide a property that allows the user to specify whether or not the
> offsets are committed. From an email on the dev mailing list:
> In the case of auto.commit.enable - we had a scenario during our last
> deploy in which we did not commit the offsets we read at all. This
> atypical. This is in the case of a Lambda-like architecture in which we use
> S3 to provide historical data to repopulate the near real-time datastore
> during a deploy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
