alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-2966 Correct anchor id to exclude-list vs. include-list

Browse Source
This commit is contained in:
Bob Roldan 2021-01-22 10:22:43 -05:00 committed by roldanbob
parent 23e8eeb854
commit 68882fec1b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/modules/ROOT/pages/connectors/cassandra.adoc
View File

@ -1004,7 +1004,7 @@ refreshing the cached Cassandra table schemas.
|`false`
|Whether deletion events should have a subsequent tombstone event (true) or not (false). It's important to note that in Cassandra, two events with the same key may be updating different columns of a given table. So this could potentially result in records being lost during compaction if they have not been consumed by the consumer yet. In other words, do NOT set this to true if you have Kafka compaction turned on.
|[[cassandra-property-field-include-list]]
|[[cassandra-property-field-exclude-list]]
[[cassandra-property-field-exclude-list]]<<cassandra-property-field-exclude-list, `field.exclude.list`>>
|
|A comma-separated list of fully-qualified names of fields that should be excluded from change event message values. Fully-qualified names for fields are in the form keyspace_name>.<field_name>.<nested_field_name>.