aho135 commented on code in PR #19386:
URL: https://github.com/apache/druid/pull/19386#discussion_r3157804426


##########
docs/querying/math-expr.md:
##########
@@ -119,6 +120,26 @@ The following built-in functions are available.
 |timestamp_parse|timestamp_parse(string expr, \[pattern, [timezone\]\]) parses 
a string into a timestamp using a given [Joda DateTimeFormat 
pattern](http://www.joda.org/joda-time/apidocs/org/joda/time/format/DateTimeFormat).
 If the pattern is not provided, this parses time strings in either ISO8601 or 
SQL format. The time zone, if provided, should be a time zone name like 
"America/Los_Angeles" or offset like "-08:00", and will be used as the time 
zone for strings that do not include a time zone offset. Pattern and time zone 
must be literals. Strings that cannot be parsed as timestamps will be returned 
as nulls.|
 |timestamp_format|timestamp_format(expr, \[pattern, \[timezone\]\]) formats a 
timestamp as a string with a given [Joda DateTimeFormat 
pattern](http://www.joda.org/joda-time/apidocs/org/joda/time/format/DateTimeFormat),
 or ISO8601 if the pattern is not provided. The time zone, if provided, should 
be a time zone name like "America/Los_Angeles" or offset like "-08:00". Pattern 
and time zone must be literals.|
 
+### Using `now()` in ingestion
+
+:::warning
+`now()` is non-deterministic: replicated streaming tasks and task replays 
evaluate it to different
+values, producing inconsistent results across replicas. Do not use `now()` to 
overwrite `__time`.
+For Kafka, prefer [`kafka.timestamp`](../ingestion/data-formats.md#kafka) as 
the
+`__time` source.

Review Comment:
   I'm not sure if it makes sense to mention Kafka here. The timestamps aren't 
equivalent as one is the time the event lands on Kafka and the other is the 
time the event is ingested in Druid



-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to