org.apache.flink.table.planner.plan.nodes.exec.common.CommonExecSink. ˓→createSinkFunctionTransformation(CommonExecSink.java:331) at org.apache.flink.table.planner.plan.nodes.exec.common.CommonExecSink at org.apache.flink.table.planner.plan.nodes.exec.common.CommonExecSink. ˓→createSinkTransformation(CommonExecSink.java:146) at org.apache.flink.table.planner.plan.nodes.exec.stream.StreamExecSink. ˓→translateToPlanInternal(StreamExecSink.java:140) at org.apache.flink.table.planner.plan.nodes.exec.ExecNodeBase. ˓→translateToPlan(ExecNodeBase.java:134) This is an issue around Java 17. It still

org.apache.flink.table.planner.plan.nodes.exec.common.CommonExecSink. ˓→createSinkFunctionTransformation(CommonExecSink.java:331) at org.apache.flink.table.planner.plan.nodes.exec.common.CommonExecSink at org.apache.flink.table.planner.plan.nodes.exec.common.CommonExecSink. ˓→createSinkTransformation(CommonExecSink.java:146) at org.apache.flink.table.planner.plan.nodes.exec.stream.StreamExecSink. ˓→translateToPlanInternal(StreamExecSink.java:140) at org.apache.flink.table.planner.plan.nodes.exec.ExecNodeBase. ˓→translateToPlan(ExecNodeBase.java:134) This is an issue around Java 17. It still

monitors input rates or other system metrics and can access information about the running query plan • It detects overload and decides what actions to take in order to maintain acceptable latency • detect overload quickly to avoid latency increase • monitor input rates • Where in the query plan? • dropping at the sources vs. dropping at bottleneck operators • How much load to shed? • enough Where in the query plan to drop tuples, which tuples, and how many • The question of where is equivalent to placing special drop operators in the best positions in the query plan • Drop operators

ace,UseStat ement,SetN amespaceC ommand,Set Command, ResetComm and Comma-separated list of query plan names, in the form of simple class names, i.e, for SET abc=xyz, the value will be SetCommand. For Meaning Type Since use this config to exclude them and let them take effect. See also kyuubi.operation.plan.only.mode. kyuubi.operation.pl an.only.mode none Configures the statement performed mode, The value filter condition as city='${{USER.born_city}}' will be transformed to city='Guangzhou' in execution plan. More supported macros and usage refer to RANGER-3605 [https://issues.apache.org/jira/browse/RANGER-3605]

ace,UseStat ement,SetN amespaceC ommand,Set Command, ResetComm and Comma-separated list of query plan names, in the form of simple class names, i.e, for SET abc=xyz, the value will be SetCommand. For Meaning Type Since use this config to exclude them and let them take effect. See also kyuubi.operation.plan.only.mode. kyuubi.operation.pl an.only.mode none Configures the statement performed mode, The value filter condition as city='${{USER.born_city}}' will be transformed to city='Guangzhou' in execution plan. More supported macros and usage refer to RANGER-3605 [https://issues.apache.org/jira/browse/RANGER-3605]

ace,UseStat ement,SetN amespaceC ommand,Set Command, ResetComm and Comma-separated list of query plan names, in the form of simple class names, i.e, for SET abc=xyz, the value will be SetCommand. For Meaning Type Since use this config to exclude them and let them take effect. See also kyuubi.operation.plan.only.mode. kyuubi.operation.pl an.only.mode none Configures the statement performed mode, The value filter condition as city='${{USER.born_city}}' will be transformed to city='Guangzhou' in execution plan. More supported macros and usage refer to RANGER-3605 [https://issues.apache.org/jira/browse/RANGER-3605]

mand,SetNa mespaceCo mmand,Use Statement,S etCatalogA ndNamespa ce Comma-separated list of query plan names, in the form of simple class names, i.e, for SET abc=xyz, the value will be SetCommand. For queries, we can use this config to exclude them and let them take effect. See also kyuubi.operation.plan.only.mode. seq 1.5.0 kyuubi.operation.pl an.only.mode none Configures the statement performed mode filter condition as city='${{USER.born_city}}' will be transformed to city='Guangzhou' in execution plan. More supported macros and usage refer to RANGER-3605 [https://issues.apache.org/jira/browse/RANGER-3605]

mand,SetNa mespaceCo mmand,Use Statement,S etCatalogA ndNamespa ce Comma-separated list of query plan names, in the form of simple class names, i.e, for SET abc=xyz, the value will be SetCommand. For queries, we can use this config to exclude them and let them take effect. See also kyuubi.operation.plan.only.mode. seq 1.5.0 kyuubi.operation.pl an.only.mode none Configures the statement performed mode filter condition as city='${{USER.born_city}}' will be transformed to city='Guangzhou' in execution plan. More supported macros and usage refer to RANGER-3605 [https://issues.apache.org/jira/browse/RANGER-3605]

mand,SetNa mespaceCo mmand,Use Statement,S etCatalogA ndNamespa ce Comma-separated list of query plan names, in the form of simple class names, i.e, for SET abc=xyz, the value will be SetCommand. For queries, we can use this config to exclude them and let them take effect. See also kyuubi.operation.plan.only.mode. seq 1.5.0 kyuubi.operation.pl an.only.mode none Configures the statement performed mode filter condition as city='${{USER.born_city}}' will be transformed to city='Guangzhou' in execution plan. More supported macros and usage refer to RANGER-3605 [https://issues.apache.org/jira/browse/RANGER-3605]

mand,SetNa mespaceCo mmand,Use Statement,S etCatalogA ndNamespa ce Comma-separated list of query plan names, in the form of simple class names, i.e, for SET abc=xyz, the value will be SetCommand. For queries, we can use this config to exclude them and let them take effect. See also kyuubi.operation.plan.only.mode. seq 1.5.0 kyuubi.operation.pl an.only.mode none Configures the statement performed mode filter condition as city='${{USER.born_city}}' will be transformed to city='Guangzhou' in execution plan. More supported macros and usage refer to RANGER-3605 [https://issues.apache.org/jira/browse/RANGER-3605]