-filtering.enabled
On Wed, Sep 27, 2023 at 9:57 AM Bonnie Arogyam Varghese <
bvargh...@confluent.io> wrote:
> Hi Martjin,
> Yes, the suggestion for the configuration name made by Jark sounds good.
>
> Also, thanks to everyone who participated in this discussion.
>
> On Tue, Sep 19, 2023 a
t; > >
> > > >
> > >
> https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/
> > > > > > >
> > > > > > > On Sat, 9 Sept 2023 at 17:33, Jing Ge
>
> > > > > > wrote:
> > > > > &
affect security. If
> users don't need to use hint, then they won't care about it and I don't
> think it's going to be a nuisance. On top of that, Lookup Join Hint is very
> useful for streaming jobs, and disabling the hint would result in users not
> being able to use
Hi Liu Ron,
To answer your question,
Security might not be the main reason for disabling this option but
other arguments brought forward by Timo. Let me know if you have any
further questions or concerns.
On Tue, Sep 5, 2023 at 9:35 PM Bonnie Arogyam Varghese <
bvargh...@confluent.io>
because they are
> an
> >>> extension to the SQL standard. It might also be the case that custom
> >>> rules would be overwritten otherwise. Setting hints could also be the
> >>> exclusive task of a DevOp team.
> >>>
> >>> Regards,
>
u ron wrote:
> Hi,
>
> Thanks for driving this proposal.
>
> Can you explain why you would need to disable query hints because of
> security issues? I don't really understand why query hints affects
> security.
>
> Best,
> Ron
>
> Bonnie Arogyam Varghese 于20
Platform providers may want to disable hints completely for security
reasons.
Currently, there is a configuration to disable OPTIONS hint -
https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/config/#table-dynamic-table-options-enabled
However, there is no configuration available
