--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/74115469-a3ea-4451-a329-cde7dee36878%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This to me just sounds like it's the first time you have executed the query and as such there is no initial offset to start from. I say this because 1970-01-01 00:00:00.000 represents the Epoch for the java Calendar class. The end time just represents the current time on the target database as represented as a UTC Calendar date.Ryan
On Tue, Oct 11, 2016 at 10:30 PM, Shannon Ma <shan...@gmail.com> wrote:
Hi,I noticed from the log22:19| DEBUG | TimestampIncrementingTableQuerier.java 171 | Executing prepared statement with timestamp value = null (1970-01-01 00:00:00.000) end time 2016-10-12 02:19:53.804WHERE "SAMPLE_TIME" > ? AND "SAMPLE_TIME" < ? ORDER BY "SAMPLE_TIME" ASCdoes that mean the time range in the inputs are (1970 to 2016), what did i miss? what should be the start time?ThanksShannon
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.