[GitHub] [druid] benkrug commented on issue #6513: Ability to auto populate timestamp on event ingestion.

[GitBox <gi...@apache.org>]

benkrug commented on issue #6513:
URL: https://github.com/apache/druid/issues/6513#issuecomment-818976140


   What's the risk of the operation not being idempotent?  If a realtime node restarts and it gets a new ingestion timestamp, does that cause some further issues?  Wouldn't only one value be persisted and published?  (Or, if not, could that just be a known risk?)  Or, if you have to restart with useEarliestOffset, you might get a different value, but couldn't that be a risk that could be known, like duplicate values is a risk?  This seems to be a common ask.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org