[jira] [Commented] (CAMEL-10696) Allow camel-kafka to resume from any offset

[Antoine DESSAIGNE (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821786#comment-15821786
 ] 

Antoine DESSAIGNE commented on CAMEL-10696:
---

Sure, no problem. Thanks for merging it.

> Allow camel-kafka to resume from any offset
> ---
>
> Key: CAMEL-10696
> URL: https://issues.apache.org/jira/browse/CAMEL-10696
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-kafka
>Reporter: Antoine DESSAIGNE
>Assignee: Claus Ibsen
> Fix For: 2.19.0
>
>
> As Kafka supports resuming from any offsets, it would be nice if this feature 
> was available camel-kafka component.
> Since Kafka needs the offset of each partition, its state (where to resume 
> from) should be somehow similar to a {{Map}}. We cannot use an 
> {{IdempotentRepository}} because it behaves like a {{Set}}.
> If we create a _standard_ API for holding the state as a {{Map}} then we can 
> reuse it for other purpose like resuming database reads from a particular 
> index.



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

[jira] [Commented] (CAMEL-10696) Allow camel-kafka to resume from any offset

[Antoine DESSAIGNE (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820749#comment-15820749
 ] 

Antoine DESSAIGNE commented on CAMEL-10696:
---

[~davsclaus] Did I forgot to do something regarding this ticket ? Thx.

> Allow camel-kafka to resume from any offset
> ---
>
> Key: CAMEL-10696
> URL: https://issues.apache.org/jira/browse/CAMEL-10696
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-kafka
>Reporter: Antoine DESSAIGNE
>
> As Kafka supports resuming from any offsets, it would be nice if this feature 
> was available camel-kafka component.
> Since Kafka needs the offset of each partition, its state (where to resume 
> from) should be somehow similar to a {{Map}}. We cannot use an 
> {{IdempotentRepository}} because it behaves like a {{Set}}.
> If we create a _standard_ API for holding the state as a {{Map}} then we can 
> reuse it for other purpose like resuming database reads from a particular 
> index.



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

[jira] [Commented] (CAMEL-10696) Allow camel-kafka to resume from any offset

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820591#comment-15820591
 ] 

ASF GitHub Bot commented on CAMEL-10696:


Github user adessaigne closed the pull request at:

https://github.com/apache/camel/pull/1393


> Allow camel-kafka to resume from any offset
> ---
>
> Key: CAMEL-10696
> URL: https://issues.apache.org/jira/browse/CAMEL-10696
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-kafka
>Reporter: Antoine DESSAIGNE
>
> As Kafka supports resuming from any offsets, it would be nice if this feature 
> was available camel-kafka component.
> Since Kafka needs the offset of each partition, its state (where to resume 
> from) should be somehow similar to a {{Map}}. We cannot use an 
> {{IdempotentRepository}} because it behaves like a {{Set}}.
> If we create a _standard_ API for holding the state as a {{Map}} then we can 
> reuse it for other purpose like resuming database reads from a particular 
> index.



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

[jira] [Commented] (CAMEL-10696) Allow camel-kafka to resume from any offset

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15818677#comment-15818677
 ] 

ASF GitHub Bot commented on CAMEL-10696:


GitHub user adessaigne opened a pull request:

https://github.com/apache/camel/pull/1393

CAMEL-10696 - Allow Kafka to resume from any offset

I created a new `StateRepository` _standard_ API in order to hold its state 
(the offset of each partition). This state looks like a `Map` whereas the 
`IdempotentRepository` behaves like a `Set` (that's why a created a new API).
Moreover this API can be later on reuse for other purpose like keeping the 
last index of database reads.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/adessaigne/camel CAMEL-10696

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1393.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1393


commit eae0b4fcb69f6376412adfa52f52268d957a9d55
Author: Antoine DESSAIGNE 
Date:   2017-01-11T15:48:02Z

CAMEL-10696 - Allow Kafka to resume from any offset based using a new 
"standard" API to hold its state




> Allow camel-kafka to resume from any offset
> ---
>
> Key: CAMEL-10696
> URL: https://issues.apache.org/jira/browse/CAMEL-10696
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-kafka
>Reporter: Antoine DESSAIGNE
>
> As Kafka supports resuming from any offsets, it would be nice if this feature 
> was available camel-kafka component.
> Since Kafka needs the offset of each partition, its state (where to resume 
> from) should be somehow similar to a {{Map}}. We cannot use an 
> {{IdempotentRepository}} because it behaves like a {{Set}}.
> If we create a _standard_ API for holding the state as a {{Map}} then we can 
> reuse it for other purpose like resuming database reads from a particular 
> index.



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