Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 07-07-2022 09:30 AM - edited 07-07-2022 09:33 AM
Hi,
how to define "Table Name Pattern" for more than 1 table in ChangeCaptureMySql processor configuration file. I tried below patterns where "product_types" and "user_subscription" table names. I want to read data only from these tables.
[product_types|user_subscription]_ or [product_types|user_subscription]%
Created 07-07-2022 03:37 PM
The pattern expression must be a regular expression (regex).
The regex equivalent to your LIKE pattern is:
(product_types|user_subscription).*
Cheers,
André
Created 07-07-2022 03:37 PM
The pattern expression must be a regular expression (regex).
The regex equivalent to your LIKE pattern is:
(product_types|user_subscription).*
Cheers,
André
Created 06-06-2023 01:00 AM
Hello @araujo
This does not work, i tried to use the above expression and the changeMySql does not use it.
So far i can do the following
- whitelist individual tables
- include all tables (by setting the table name pattern to empty)
This is a problem for us, we need to whitelist tables, since the dB user we use does not have access to all tables and the processor complains without the filtering.
Manually filtering one table at a time, is not a scalable approach since we need to extract data from multiple tables and this processor does not support incoming connections.
Did anyone find a solution where one instance of "CaptureChangeMySQL" can extract data for multiple tables ?
Created 06-20-2023 01:57 AM
Anyone else experienced this issue ? is there a solution that does not involve creating one CaptureChangeMySQL processor instance per source table ?
Created 08-30-2023 01:08 AM
Anyone else experienced this issue ? is there a solution that does not involve creating one CaptureChangeMySQL processor instance per source table ?