Hi, I used PopularPlacesFromKafka from dataartisans.flinktraining.exercises as the basis. I made very minor changes
object KafkaEventTimeWindow { class PositionEventProtoTSAssigner |
Hi shyla, I answered a similar question on stackoverflow[1], you can take a look first. Best, Hequn On Sun, Aug 5, 2018 at 11:24 AM, shyla deshpande <[hidden email]> wrote:
|
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 set the TimeCharacteristic to the stream level instead on the application level? Thank you On Sat, Aug 4, 2018 at 10:05 PM, Hequn Cheng <[hidden email]> wrote:
|
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.ProcessingT Thanks, the link you provided saved my time. -shyla
On Sun, Aug 5, 2018 at 9:28 AM, anna stax <[hidden email]> wrote:
|
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 <[hidden email]> 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 any additional data. You can use both, EventTime and ProcessingTime in the same application and StreamExecutionEnvironment. However, if you enable EventTime, this will be the default mode in some API methods that create time-based operators and you will need to explicitly create ProcessingTime operators if you want to work in ProcessingTime. For example, the stream.keyBy().timeWindow(Time.minute(1)) shortcut, would create an EventTime Tumbling Window if the TimeCharacteristic is set to EventTime and a ProcessingTIme Tumbling Window if it is ProcessingTIme. Best, Fabian 2018-08-06 4:30 GMT+02:00 Hequn Cheng <[hidden email]>:
|
Hi Hequn and Fabian, Thanks. Appreciate your help On Mon, Aug 6, 2018 at 1:32 AM, Fabian Hueske <[hidden email]> wrote:
|
Free forum by Nabble | Edit this page |