; >>>> >> > >
>>>> > >>>> >> > >
>>>> > >>>> >> > > Best,
>>>> > >>>> >> > > Ron
>>>> > >>>> >> > >
>>>> > >>>> >>
efer to set the default value of this option
>>> as'false in
>>> > >>>> the
>>> > >>>> >> first
>>> > >>>> >> > > > place. Setting as true might introduce unexpected
>>> behavior
>>> > for
>>> > >>>&
plementation options
>> > and
>> > >>>> are
>> > >>>> >> they
>> > >>>> >> > > > feasible?
>> > >>>> >> > > >
>> > >>>> >> > > > Yes, we have already imple
; >> > > > > Thank you for proposing this FLIP, it's great work and
> > looks
> > >>>> very
> > >>>> >> > > useful
> > >>>> >> > > > > for users.
> > >>>&g
;>> >> and
> >>>> >> > > > > should the engine enable this optimization by default.
> >>>> Currently
> >>>> >> for
> >>>> >> > > > source
> >>>> >> > > > > reuse, the default value of
> >>>>
> > > > think the engine should turn on Sink reuse optimization by
>>>> >> default.
>>>> >> > > > > 2. Regarding Sink Digest, you mentioned disregarding the sink
>>>> >> target
>>>> >> > > > &g
>> >> > > > can
>>> >> > > > > be done. I have a question: have you considered the technical
>>> >> > > > > implementation options and are they feasible?
>>> >> > > > >
>>> >> > > > &
> > > > > Regards,
>> >> > > > > > Xiangyu
>> >> > > > > >
>> >> > > > > > xiangyu feng 于2025年2月11日周二 14:17写道：
>> >> > > > > >
>> >> > > > &
; > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://paimon.apache.org/docs/master/maintenance/write-performance/#local-merging
> >> > > > > > >
> >> > > > > >
a structure to be processed
>> should
>> > be
>> > > > > > fixed."
>> > > > > > >>
>> > > > > > >> I'm not very sure why the data structure of SinkWriter
>> should be
>> > &
>> I'm not very sure why the data structure of SinkWriter
>> should be
>> > > > > fixed.
>> > > > > > >> Can you elaborate the scenario here?
>> > > > > > >>
>> > > > > > >> "Is there
By `filling in the inconsistent field from different sources`,
> > do
> > > > you
> > > > > > >> refer to implementations like the LocalMerge Operator [1] for
> > > > Paimon?
> > > > > > IMHO,
> > > > > > >> this should not be incl
> > >>
> > > > > >> Regards,
> > > > > >> Xiangyu Feng
> > > > > >>
> > > > > >> xiangyu feng 于2025年2月11日周二 13:46写道：
> > > > > >>
> > > > > >>> Hi Yanquan,
> > > > > >>>
&
ces. If not, a SQL validation exception
> > should
> > > > be
> > > > >>> raised for planner.
> > > > >>>
> > > > >>> Regards,
> > > > >>> Xiangyu Feng
> > > > >>>
> > > >
gt; > be
> > > >>> raised for planner.
> > > >>>
> > > >>> Regards,
> > > >>> Xiangyu Feng
> > > >>>
> > > >>>
> > > >>>
> > > >>> Yanquan Lv 于2025年2月10日周一 16:25写道：
&g
i, Xiangyu. Thanks for driving this.
> > >>>>
> > >>>> I have a question to confirm:
> > >>>> Considering the case that different Sources use different
> columns[1],
> > >>>> will the Schema of CatalogTable[2] contain all tar
rces use different columns[1],
> >>>> will the Schema of CatalogTable[2] contain all target columns for
> Sources?
> >>>> And for SinkWriter, the data structure to be processed should be
> fixed.
> >>>> Is there a node or a
field of Rowdata
>>>> that passed from different Sources?
>>>>
>>>> [1]
>>>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-506%3A+Support+Reuse+Multiple+Table+Sinks+in+Planner
>>>> [2]
>>>> https://nightlies.apache.org/flink/fl
rg/confluence/display/FLINK/FLIP-506%3A+Support+Reuse+Multiple+Table+Sinks+in+Planner
>> [2]
>> https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sourcessinks/#planning
>>
>>
>>
>> > 2025年2月6日 17:06，xiangyu feng 写道：
>> >
&g
Sources?
>>>
>>> [1]
>>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-506%3A+Support+Reuse+Multiple+Table+Sinks+in+Planner
>>> [2]
>>> https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sourcessinks/#planning
>>>
>>>
>>>
nning
>
>
>
> > 2025年2月6日 17:06，xiangyu feng 写道：
> >
> > Hi devs,
> >
> > I'm opening this thread to discuss FLIP-506: Support Reuse Multiple Table
> > Sinks in Planner[1].
> >
> > Currently if users want to partial-update a downst
/sourcessinks/#planning
> 2025年2月6日 17:06，xiangyu feng 写道：
>
> Hi devs,
>
> I'm opening this thread to discuss FLIP-506: Support Reuse Multiple Table
> Sinks in Planner[1].
>
> Currently if users want to partial-update a downstream table from multiple
> source tables in
ent here, I can't find that in the FLIP.
>
> Best regards,
>
> Martijn
>
> On Thu, Feb 6, 2025 at 10:06 AM xiangyu feng wrote:
>
> > Hi devs,
> >
> > I'm opening this thread to discuss FLIP-506: Support Reuse Multiple Table
> > Sinks in Planner[
Hi Xiangyu Feng,
Thanks for the FLIP. Could you elaborate on why Statement Sets aren't
sufficient here, I can't find that in the FLIP.
Best regards,
Martijn
On Thu, Feb 6, 2025 at 10:06 AM xiangyu feng wrote:
> Hi devs,
>
> I'm opening this thread to discuss FLIP-506
Hi devs,
I'm opening this thread to discuss FLIP-506: Support Reuse Multiple Table
Sinks in Planner[1].
Currently if users want to partial-update a downstream table from multiple
source tables in one datastream, they would have to manually union all
source tables and add lots of "ca
25 matches
Mail list logo
