Re: microsecond resolution

2016-12-05 Thread jeff jacobson
stem.currentTimeMillis()) > > So, you can "re-interpret" them by using custom window assigners and not > using processing time. > If you want to use a processing time like component, I'd suggest to > incorporate that in your watermark generator. > > Stephan > >

Re: microsecond resolution

2016-12-05 Thread jeff jacobson
; Hi Jeff, > > Actually in Flink timestamps are simple longs. > This means that you can assign anything you want as a timestamp, as long > as it fits in a long. > > Hope this helps and if not, we can discuss to see if we can find a > solution that > fits your needs together.

Re: microsecond resolution

2016-12-04 Thread jeff jacobson
not read your question carefully enough. > > Than the answer is no, it does not support microseconds (only > milliseconds). > > - -Matthias > > > On 12/4/16 2:22 PM, jeff jacobson wrote: > > Sorry if I'm missing something. That link mentions milliseconds, > > no?

Re: microsecond resolution

2016-12-04 Thread jeff jacobson
rg/projects/flink/flink-docs- > release-1.1/apis/streaming/event_timestamps_watermarks. > html#assigning-timestamps > > "Both timestamps and watermarks are specified as millliseconds since the > Java epoch of 1970-01-01T00:00:00Z." > > > > -Matthias > > >

microsecond resolution

2016-12-04 Thread jeff jacobson
I've sourced stackoverflow, the docs, and the web but I can't figure out: does flink support microsecond timestamp resolution? Thanks!