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

Support for custom sorting order #340

Open
aelfric opened this issue Jul 9, 2024 · 0 comments
Open

Support for custom sorting order #340

aelfric opened this issue Jul 9, 2024 · 0 comments

Comments

@aelfric
Copy link

aelfric commented Jul 9, 2024

Using the JDBC source connector, we have a use-case where we have a composite primary key comprised of an ID and a version. When an update is made, previous rows are marked as inactive and new row with an incremented version is created. All effected rows will be updated with a modification timestamp. By default, when using the timestamp strategy for the JDBC source, the query that is build appends ORDER BY timestamp_column to the query. We would like this to be more deterministic and have the ordering depend first on the version column. Would a use-case like this be a valid case to open a PR?

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

1 participant