NDB Cluster Configuration Files Causes a replica  mysqld  to write the NDB transaction ID in each row of the binary log. The default value is  FALSE . This option is not supported in mainline MySQL Server 8.0. It is required to enable NDB Cluster Replication conflict detection and resolution using the  NDB$EPOCH_TRANS()  function (see NDB $EPOCH_TRANS()). For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . The deprecated  log_bin_use_v1_row_events  system variable, which defaults to  OFF , must not be set to  ON  when you use  --ndb-log-transaction-id . Whether updates on the source are written to the binary log as updates ( OFF ) or writes ( ON ). Used in NDB Replication conflict resolution; for more information, see Logging Changed Data as Updates. Whether  mysqld  writes complete rows ( ON ) or updates only ( OFF ) to the binary log. Used in NDB Replication conflict resolution; see Logging Full or Partial Rows, for more information. • --ndb-log-update-minimal • --ndb-log-updated-only • --ndb-log-update-as-write SET_VAR  Hint Applies No Type Boolean Default Value OFF Command-Line Format --ndb-log-update-as-write[={OFF|ON}] System Variable ndb_log_update_as_write Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value ON Command-Line Format --ndb-log-updated-only[={OFF|ON}] System Variable ndb_log_updated_only Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value ON Command-Line Format --ndb-log-update-minimal[={OFF|ON}] System Variable ndb_log_update_minimal Scope Global Dynamic Yes SET_VAR  Hint Applies No 4169