EMsnap commented on code in PR #8117:
URL: https://github.com/apache/inlong/pull/8117#discussion_r1209659371
##########
inlong-sort/sort-common/src/main/java/org/apache/inlong/sort/configuration/Constants.java:
##########
@@ -97,6 +97,31 @@ public class Constants {
*/
public static final String PIPELINE_NAME = "pipeline.name";
+ /**
+ *
https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/config/
+ * default AUTO
+ */
+ public static final String TABLE_EXEC_SINK_UPSERT_MATERIALIZE =
"table.exec.sink.upsert-materialize";
+
+ public static final ConfigOption<String> UPSERT_MATERIALIZE =
+
key("table.exec.sink.upsert-materialize").defaultValue("AUTO").withDescription("Because
of the disorder "
+ + "of ChangeLog data caused by Shuffle in distributed
system, the data received by Sink may not "
+ + "be the order of global upsert. So add upsert
materialize operator before upsert sink. It "
+ + "receives the upstream changelog records and generate an
upsert view for the downstream.\n"
+ + "By default, the materialize operator will be added when
a distributed disorder occurs on "
+ + "unique keys. You can also choose no
materialization(NONE) or force materialization(FORCE).");
+
+ public static final String TABLE_EXEC_SINK_NOT_NULL_ENFORCER =
"table.exec.sink.not-null-enforcer";
+
+ public static final ConfigOption<String> NOT_NULL_ENFORCER =
+
key("table.exec.sink.not-null-enforcer").defaultValue("ERROR").withDescription("Determines
how Flink "
+ + "enforces NOT NULL column constraints when inserting
null values.\n"
+ + "\n"
Review Comment:
extra \n
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
