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

DBZ-4000 Add Oracle docs; remove internal names

Browse Source
This commit is contained in:
Jiri Pechanec 2021-10-20 16:32:04 +02:00 committed by Gunnar Morling
parent 1915534fc7
commit a6ae15d0ca
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -2475,7 +2475,7 @@ endif::community[]
|[[mysql-property-include-schema-comments]]<<mysql-property-include-schema-comments, `+include.schema.comments+`>>
|`false`
|Boolean value that specifies whether the connector should parse and publish table and column comments on metadata objects. Enabling this option will bring the implications on memory usage. The number and size of `ColumnImpl` objects is what largely impacts how much memory is consumed by the Debezium connectors, and adding a String to each of them can potentially be quite expensive.
|Boolean value that specifies whether the connector should parse and publish table and column comments on metadata objects. Enabling this option will bring the implications on memory usage. The number and size of logical schema objects is what largely impacts how much memory is consumed by the Debezium connectors, and adding potentially large string data to each of them can potentially be quite expensive.
|[[mysql-property-include-query]]<<mysql-property-include-query, `+include.query+`>>
|`false`

6
documentation/modules/ROOT/pages/connectors/oracle.adoc
View File

@ -39,7 +39,7 @@ If you need assistance with this feature, you can engage with the https://debezi
Information and procedures for using a {prodname} Oracle connector are organized as follows:
* xref:how-debezium-mysql-connectors-work[]
* xref:how-debezium-oracle-connectors-work[]
* xref:descriptions-of-debezium-oracle-connector-data-change-events[]
* xref:how-debezium-oracle-connectors-map-data-types[]
* xref:setting-up-oracle-to-work-with-debezium[]
@ -2055,6 +2055,10 @@ In the resulting snapshot, the connector includes only the records for which `de
|An optional, comma-separated list of regular expressions that match names of schemas for which you *want* to capture changes. Any schema name not included in `schema.include.list` is excluded from having its changes captured. By default, all non-system schemas have their changes captured. Do not also set the `schema.exclude.list` property.
In environments that use the LogMiner implementation, you must use POSIX regular expressions only.
|[[oracle-property-include-schema-comments]]<<oracle-property-include-schema-comments, `+include.schema.comments+`>>
|`false`
|Boolean value that specifies whether the connector should parse and publish table and column comments on metadata objects. Enabling this option will bring the implications on memory usage. The number and size of logical schema objects is what largely impacts how much memory is consumed by the Debezium connectors, and adding potentially large string data to each of them can potentially be quite expensive.
|[[oracle-property-schema-exclude-list]]<<oracle-property-schema-exclude-list, `+schema.exclude.list+`>>
|No default
|An optional, comma-separated list of regular expressions that match names of schemas for which you *do not* want to capture changes. Any schema whose name is not included in `schema.exclude.list` has its changes captured, with the exception of system schemas. Do not also set the `schema.include.list` property.