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

fix: Use correct schema when opening transformed partitioned tables #5305

Merged
merged 3 commits into from
Apr 2, 2024

Conversation

mofojed
Copy link
Member

@mofojed mofojed commented Mar 28, 2024

- We were using the schema from the constituent table when trying to reference the key columns instead of the keys table
- Was not a problem when the schemas matched, but if there was a transform on the table removing one of the key columns, it would throw an error
- Fixes deephaven#5304
@mofojed mofojed added NoDocumentationNeeded NoReleaseNotesNeeded No release notes are needed. labels Mar 28, 2024
@mofojed mofojed requested a review from niloc132 March 28, 2024 17:32
@mofojed mofojed self-assigned this Mar 28, 2024
niloc132
niloc132 previously approved these changes Mar 28, 2024
Copy link
Member

@niloc132 niloc132 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved - if it doesn't need to land right away, write a test for this?

- Just tests for static JsPartitionedTable for now
@mofojed mofojed merged commit 765934b into deephaven:main Apr 2, 2024
15 checks passed
@mofojed mofojed deleted the 5304-partitioned-transform branch April 2, 2024 20:48
@github-actions github-actions bot locked and limited conversation to collaborators Apr 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

JsPartitionedTable breaks if raw partitioned table schema does not match the constituent tables
2 participants