ListTableNames 2025.3.28.13-SNAPSHOT¶
BUNDLE¶
com.snowflake.openflow.runtime | runtime-database-cdc-processors-nar
DESCRIPTION¶
Fetches all source table names and matches them with one of the possible configurations:- regexp expression e.g. “(?i)customer.(orders|payments)” - it matches names in case insensitive way. It would match both “CUSTOMER.ORDERS” and “customer.orders” source table names.- comma separated list of source table names. e.g. “customer.orders, customer.payments”. It matches source table names in case sensitive way i.e. “customer.orders” source table will beforwarded to MATCH relationship but “customer.ORDERS” won’t match and will be farwarded to UNMATCHED relationship.Configuration is passed as a FlowFile attribute. Source table name is represented as <schema_name>.<table_name> so both inputs should take that into consideration.Matched source table names are forwarded to MATCHED relationship with matching result attribute equal to ‘MATCHED’. The unmatched ones are moved to the UNMATCHED relationship with thematching result attribute equal to ‘UNMATCHED’. Processor generates a separate flow file for each discovered source table.Disclaimers- Postgresql allows to define database object names in case sensitive or case insensitive way. When user creates a table using following query ‘CREATE TABLE ORDERS(id int not null)’ theninternally Postgresql stores it using lower case letters i.e. orders. To enforce case sensitivity user has to wrap the table name with double quotes i.e. ‘CREATE TABLE “ORDERS”(id int notnull)’. This is important aspect when configuring table that we would like to replicate.
INPUT REQUIREMENT¶
REQUIRED
Supports Sensitive Dynamic Properties¶
false
PROPERTIES¶
Property |
Description |
---|---|
Connection Pool |
The Controller Service that is used to obtain a connection to the database. |
Included Comma Separated Source Table Names |
The list of comma separated list of tables to replicate. A single table should be formatted as <schema_name>.<table_name> e.g. customer.orders, customer.payments. This is combined with the regular expression to include any matching table. |
Included Source Table Pattern |
Regular Expression for specifying table names to replicate e.g. customer.(orders|payments). This is combined with the comma-separated list to include any matching table. |
RELATIONSHIPS¶
NAME |
DESCRIPTION |
---|---|
failure |
If a FlowFile attribute cannot be read or is incorrect, it will be routed to this Relationship. |
matched |
Successfully created FlowFiles, one for each matching table found in the source database. |
unmatched |
If a table name does not match it will be routed to this Relationship. |
WRITES ATTRIBUTES¶
NAME |
DESCRIPTION |
---|---|
source.schema.name |
Name of the schema of the table from which an event originated |
source.table.name |
Name of the table from which an event originated |
source.table.matching.result |
The result of the matching process. Matched FlowFiles will be marked with the value ‘MATCHED’, otherwisethey are marked with value ‘UNMATCHED’ |