[
https://issues.apache.org/jira/browse/SPARK-17812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576840#comment-15576840
]
Michael Armbrust commented on SPARK-17812:
------------------------------------------
That sounds pretty good to me, with one question: Is {{assign}} useful here?
It seems you know the list of topicpartitions as they are all passed to
{{startingOffsets}}. If we get rid of {{assign}}, and keep the offset log
format consistent with {{startingOffsets}}, then you could resume a query where
another left off, simply by copying the last batch. However, if we keep
{{assign}}, you'll have to type that out manually and I'm not sure what you are
gaining.
I would use jackson for the JSON stuff, but I would probably not use
catalyst/encoders since those require code generation thats not going to buy us
much.
Thanks for working on this!
> More granular control of starting offsets (assign)
> --------------------------------------------------
>
> Key: SPARK-17812
> URL: https://issues.apache.org/jira/browse/SPARK-17812
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Reporter: Michael Armbrust
> Assignee: Cody Koeninger
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
