as a Jira talk about retraction.
>> In other cases, results are derived from long history which makes not
>> rationale to keep. A side pipeline capture those events with late arriving
>> event handling might interact with external storage and amend results.
>>
>> Thanks
e events with late arriving
> event handling might interact with external storage and amend results.
>
> Thanks,
> Chen
>
>
> *From: *Peter Lappo <pe...@systematicmethods.com>
> *Sent: *Sunday, September 10, 2017 3:00 PM
> *To: *user@flink.apache.org
> *Subject:
eline capture those events with late arriving
> event handling might interact with external storage and amend results.
>
> Thanks,
> Chen
>
> From: Peter Lappo <mailto:pe...@systematicmethods.com>
> Sent: Sunday, September 10, 2017 3:00 PM
> To: user@flink.apache.org <
, September 10, 2017 3:00 PM
To: user@flink.apache.org
Subject: ETL with changing reference data
hi,
We are building an ETL style application in Flink that consumes records from a
file or a message bus as a DataStream. We are transforming records using SQL
and UDFs. The UDF loads reference data
hi,
We are building an ETL style application in Flink that consumes records from a
file or a message bus as a DataStream. We are transforming records using SQL
and UDFs. The UDF loads reference data in the open method and currently the
data loaded remains in memory until the job is cancelled.