Hi Hequn and Fabian,
Thanks. Appreciate your help
On Mon, Aug 6, 2018 at 1:32 AM, Fabian Hueske wrote:
> Hi,
>
> By setting the time characteristic to EventTime, you enable the internal
> handling of record timestamps and watermarks.
> In contrast to EventTime, ProcessingTime does not require an
Hi,
By setting the time characteristic to EventTime, you enable the internal
handling of record timestamps and watermarks.
In contrast to EventTime, ProcessingTime does not require any additional
data.
You can use both, EventTime and ProcessingTime in the same application and
StreamExecutionEnvir
Hi anna, shyla
When we call setStreamTimeCharacteristic(env.setStreamTimeCharacteristic),
it means sets the time characteristic for all streams create from this
environment. So if your application contains multi environments, then yes.
Best, Hequn
On Mon, Aug 6, 2018 at 9:37 AM, shyla deshpande
Hi Hequn,
I now realize that in Production, data will not be a problem since this
will be a high volume kafka topic.
So, I will go with EventTime.
Still, I would like to know if
I can use both TimeCharacteristic.ProcessingTime and
TimeCharacteristic.EventTime in an application.
*Thanks, the li
Hi Hequn,
Thanks for link. Looks like I better use ProcessingTime instead of
EventTime especially because of the 4th reason you listed..
"Data should cover a longer time span than the window size to advance the
event time."
I need the trigger when the data stops.
I have 1 more question.
Can I se
Hi shyla,
I answered a similar question on stackoverflow[1], you can take a look
first.
Best, Hequn
[1]
https://stackoverflow.com/questions/51691269/event-time-window-in-flink-does-not-trigger
On Sun, Aug 5, 2018 at 11:24 AM, shyla deshpande
wrote:
> Hi,
>
> I used PopularPlacesFromKafka from
