You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/03/13 22:13:49 UTC
[jira] [Resolved] (SAMZA-157) Offset default behavior for streams
[ https://issues.apache.org/jira/browse/SAMZA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Riccomini resolved SAMZA-157.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.7.0
Merged and committed.
> Offset default behavior for streams
> -----------------------------------
>
> Key: SAMZA-157
> URL: https://issues.apache.org/jira/browse/SAMZA-157
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Chris Riccomini
> Fix For: 0.7.0
>
> Attachments: SAMZA-157.0.patch, SAMZA-157.1.patch, SAMZA-157.3.patch, SAMZA-157.4.patch
>
>
> Introduce a systems.<system name>.streams.<stream name>.samza.offset.default configuration, which specifies what to do when no checkpoint exists for an input topic. This is a similar to setting to Kafka's auto.offset.reset setting. Developers will be able to specify "oldest", "latest", or "fail".
> we should also add the ability to override offsets for specific stream partitions. Something like:
> {noformat}
> systems.<system name>.streams.<stream name>.samza.force.offsets=0:123,1:123,2:123
> {noformat}
> The format I'm proposing is:
> {noformat}
> <partition string>:<force offset>,...
> {noformat}
> This is obviously dependent on offsets not having ':' or ',' in them, which I think is a safe assumption.
> This setting would force the system consumer to be registered with the specified offset for the given SSP (ignoring both the checkpoint, if it exists, and the samza.reset.offset setting).
--
This message was sent by Atlassian JIRA
(v6.2#6252)