We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am noticing PGSync indexing multiple times when a single record changes.
Given a schema.json file as the following:
schema.json
[ { "database": "default", "index": "my_index", "nodes": { "table": "my_table", "columns": [ "foo" ] } } ]
I have the following query which executes:
UPDATE my_table SET foo = "hello" WHERE id = 1;
Within the following snippet, 1 bulk request happens:
pgsync/pgsync/sync.py
Lines 1228 to 1231 in 1e4c3c7
Then, within this next snippet, 1 more bulk request happens:
Lines 1232 to 1233 in 1e4c3c7
I feel like there should only be 1 request only. Is there a valid reason to index multiple times in this case?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am noticing PGSync indexing multiple times when a single record changes.
Example
Given a
schema.json
file as the following:I have the following query which executes:
What is happening?
Within the following snippet, 1 bulk request happens:
pgsync/pgsync/sync.py
Lines 1228 to 1231 in 1e4c3c7
Then, within this next snippet, 1 more bulk request happens:
pgsync/pgsync/sync.py
Lines 1232 to 1233 in 1e4c3c7
What do I expect to happen instead?
I feel like there should only be 1 request only. Is there a valid reason to index multiple times in this case?
The text was updated successfully, but these errors were encountered: