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

Get last modified from data #596

Merged
merged 3 commits into from
Nov 2, 2024
Merged

Get last modified from data #596

merged 3 commits into from
Nov 2, 2024

Conversation

spbnick
Copy link
Collaborator

@spbnick spbnick commented Nov 1, 2024

Now that we're not going to be loading data in KCIDB directly from the submission queue, remove the rate throttling (which was inactive anyway due to particular database drivers being used).

Instead solely targeting the get_last_modified() method to databases which have load rate limit, make all of them support it, and return the maximum _timestamp value across all tables, if the schema has it.

Concerns #541

Now that we're not going to be loading data in KCIDB directly from the
submission queue, remove the rate throttling (which was inactive anyway
due to particular database drivers being used).
Instead solely targeting the get_last_modified() method to databases
which have load rate limit, make all of them support it, and return the
maximum `_timestamp` value across all tables, if the schema has it.
@spbnick spbnick merged commit bbe6529 into main Nov 2, 2024
6 checks passed
@spbnick spbnick deleted the get_last_modified_from_data branch November 2, 2024 05:54
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

Successfully merging this pull request may close these issues.

1 participant