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

[duckdb] Fixed multi-store bug #1459

Merged

Conversation

FelixGV
Copy link
Contributor

@FelixGV FelixGV commented Jan 21, 2025

The view created by DuckDBDVRT was called current_version, so it could not work with multiple stores. Changed it so that the view inherits the store name instead.

Miscellaneous build changes:

  • Fixed the duckdb exclusion rule in all-modules.
  • Bumped up the duckdb snapshot dep to the current latest one.

How was this PR tested?

New unit test.

Does this PR introduce any user-facing changes?

  • No. You can skip the rest of this section.
  • Yes. Make sure to explain your proposed changes and call out the behavior change.

The view created by DuckDBDVRT was called current_version, so it could
not work with multiple stores. Changed it so that the view inherits the
store name instead.

Miscellaneous build changes:

- Fixed the duckdb exclusion rule in all-modules.
- Bumped up the duckdb snapshot dep to the current latest one.
@FelixGV FelixGV enabled auto-merge (squash) January 21, 2025 21:33
@FelixGV FelixGV disabled auto-merge January 21, 2025 22:14
@FelixGV FelixGV enabled auto-merge (squash) January 21, 2025 22:57
@FelixGV FelixGV merged commit d300c52 into linkedin:main Jan 21, 2025
57 checks passed
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.

2 participants