Hi izual,
There is a workaround that you could implement your own sink which write
record sink1 and sink2 in turn.
*Best Regards,*
*Zhenghua Gao*
On Wed, Mar 25, 2020 at 10:41 PM Benchao Li wrote:
> Hi izual,
>
> AFAIK, there is no way to to this in pure SQL.
>
>
>
>
> izual 于2020年3月25日周三 下午
Hi izual,
AFAIK, there is no way to to this in pure SQL.
izual 于2020年3月25日周三 下午10:33写道：
> We have two output sinks, and the order assurance is achieved by code like
> this:
>
> record.apply(insert_into_sink1).thenApply(
>
> recorder_2 = foo(record)
>
> recorder_2.insert_into_sink2
>
> )
>
>
We have two output sinks, and the order assurance is achieved by code like this:
record.apply(insert_into_sink1).thenApply(
recorder_2 = foo(record)
recorder_2.insert_into_sink2
)
So when sink2 receives the record_2, record must be existed in sink1, then we
can seek corresponding value of rec
