Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/21651
- We need agreement on whether it is worth making a change to the public
Sink api (probably not any time soon, judging from the spark 3.0 vs 2.4
discussion), or whether there is a different way to accomplish the goal.
- I wouldn't worry about what any particular sink implementation does with
the offsets, most of the existing ones shouldn't do anything by default. You
just need a proof of concept that a given sink (e.g. a database sink) can do
something useful with them.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
