spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ofir Manor (JIRA)" <>
Subject [jira] [Commented] (SPARK-17812) More granular control of starting offsets (assign)
Date Thu, 13 Oct 2016 20:36:20 GMT


Ofir Manor commented on SPARK-17812:

Regarding (1) - of course it is *all* data in the source, as of query start. Just the same
as file system directory or a database table - I'm not sure a disclaimer that the directory
or table could have had different data in the past adds anything but confusion...
Anyway, the startingOffset is confusing because, it seems you want a different parameter for
"assign" --> to explicitly specify starting offsets.
For you use case, I would add:
5. Give me nnn messages (not last ones). We still do one of the above options (trying to go
back nnn messages, somehow split between the topic-partitions involved), but not provide a
more explicit guarantee like "last nnn". Generally, the distribution of messages to partitions
don't have to be round-robin or uniform, it is strongly based on the key (example, could be
state, could be URL etc).
Anyway, I haven't seen a concrete suggestion on how to specify offsets or timestamp, so I
think that would be the next step in this ticket (I suggested you could condense all to one
option to avoid dependencies between options, but I don't have an elegant "stringly" suggestion)

> More granular control of starting offsets (assign)
> --------------------------------------------------
>                 Key: SPARK-17812
>                 URL:
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Michael Armbrust
> Right now you can only run a Streaming Query starting from either the earliest or latests
offsets available at the moment the query is started.  Sometimes this is a lot of data.  It
would be nice to be able to do the following:
>  - seek to user specified offsets for manually specified topicpartitions

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message