Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

filtering pattern not work, the docker container panic #2057

Open
chengcxy opened this issue Oct 23, 2023 · 8 comments
Open

filtering pattern not work, the docker container panic #2057

chengcxy opened this issue Oct 23, 2023 · 8 comments

Comments

@chengcxy
Copy link

maxwell-1.27.1
docker.config.properties is

exclude: .,include:base_elements.company_inv,include:z_pe.base_entity_zid,include:z_pe.base_entity_basic_info.

Maxwell suddenly reported an error.

06:41:32,138 INFO BinlogConnectorReplicator - Binlog connected.
06:41:32,178 INFO BinlogConnectorReplicator - Binlog disconnected.
06:41:32,184 INFO TaskManager - Stopping 4 tasks
06:41:32,184 ERROR TaskManager - cause:
java.lang.RuntimeException: Couldn't find table algo_finance_event in database z_etl
at com.zendesk.maxwell.replication.TableCache.processEvent(TableCache.java:31) ~[maxwell-1.27.1.jar:1.27.1].

config.properties is filter the database z_etl, Why still prompt for an error where the z_etl table does not exist.

image

@ZeeshanIbrahim1
Copy link

can you share more about your problem? how are you using the filter command?

@chengcxy
Copy link
Author

can you share more about your problem? how are you using the filter command?

config like:

exclude: .,include:base_elements.company_inv,include:z_pe.base_entity_zid,include:z_pe.base_entity_basic_info

it don't work

@ZeeshanIbrahim1
Copy link

ZeeshanIbrahim1 commented Feb 28, 2024

I am using yaml (docker) file having maxwell config and in that I have defined a command with 'filter' tag which is working perfectly. I can share that with you. you may have to change this according to where you are running this command.
My maxwell config look like this:
maxwell:
image: zendesk/maxwell:latest
links:
- kafka
command: >
./bin/maxwell
//other config related to host db config
--filter='exclude:.,include:base_elements.company_inv,include:z_pe.base_entity_zid,include:z_pe.base_entity_basic_info'

First of all you are not using the 'filter' tag and if you want to exclude every database with every table use " . "
Also one crucial thing to check is that there are no spaces between filter command and equal to (=)

If the error still exists then ping me . I will try to recreate this error and give you more info regarding this.

@chengcxy
Copy link
Author

I am using yaml (docker) file having maxwell config and in that I have defined a command with 'filter' tag which is working perfectly. I can share that with you. you may have to change this according to where you are running this command. My maxwell config look like this: maxwell: image: zendesk/maxwell:latest links: - kafka command: > ./bin/maxwell //other config related to host db config --filter='exclude:.,include:base_elements.company_inv,include:z_pe.base_entity_zid,include:z_pe.base_entity_basic_info'

First of all you are not using the 'filter' tag and if you want to exclude every database with every table use " . " Also one crucial thing to check is that there are no spaces between filter command and equal to (=)

If the error still exists then ping me . I will try to recreate this error and give you more info regarding this.

thanks.

the config.properties.filter tag no spaces between filter command and equal to (=),like the picture

image

The Maxwell also send msgs to RabbimtMq, we consume the mq then write to mysql.

for example,datafeed.company_ar_socialfee is excluded,but mysql also write data.

image

@chengcxy
Copy link
Author

I changed the content order of the config.properties.filter It looks like it's working now。

old_config is exclude:datafeed.A,include:datafeed.*

new_config is include:datafeed.*,exclude:datafeed.A

😄 It's really a pit。

@ZeeshanIbrahim1
Copy link

I am not quite sure but maybe this is the behavior of the filter command. The new commands (e.g., exclude, include) overwrite the previous ones. This means that the order in which filters are applied can affect the final result. So, yes, the sequence does matter.

If you have any further queries related to this, feel free to ask. Considering the explanation provided, it seems like the behavior of the filter command has been clarified. Therefore, we can consider closing this issue. Let me know if you agree.

@chengcxy
Copy link
Author

Thanks.
You can close this issue

@ZeeshanIbrahim1
Copy link

Kindly close this issue. @osheroff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants