Github user hvanhovell commented on the issue: https://github.com/apache/spark/pull/14568 Ok, so the maximum of the lower 33 bits would be the starting offset for the next batch. That is not super easy for an end user to do. Lets say a user inserts data from table a into table b, using this would require code like this: ```sql insert into b select *, monotonically_increasing_id((select max(id & 8589934591) from b)) as id from a ``` Other than that, the change looks pretty good. I left one last comment regarding the python code.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org