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: DH-18803: Add qst Type find support for componentType #6667

Merged
merged 1 commit into from
Mar 4, 2025

Conversation

devinrsmith
Copy link
Member

This adds the needed, centralized logic for adapting to qst Type when componentType is not null. This allows downstream callers, such as the Sql adapter layer, to correctly construct the appropriate Types.

This adds the needed, centralized logic for adapting to qst Type when componentType is not null. This allows downstream callers, such as the Sql adapter layer, to correctly construct the appropriate Types.
@devinrsmith devinrsmith self-assigned this Feb 27, 2025

@Override
public String visit(BooleanType booleanType) {
return null;
Copy link
Member

Choose a reason for hiding this comment

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

Is it possible (or necessary?) to map this to ObjectVector<Boolean> -- this is what a groupBy will do for both boxed and unboxed booleans.

Copy link
Member Author

Choose a reason for hiding this comment

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

So, this is mostly a modelling Q; ObjectVector<Integer> is not the same as IntVector. In that vain, ObjectVector<Boolean> is a valid io.deephaven.qst.type.GenericVectorType, but there is no io.deephaven.qst.type.PrimitiveVectorType equivalent (just as there is no BoolVector).

@devinrsmith devinrsmith merged commit 68d7bdc into deephaven:main Mar 4, 2025
18 of 21 checks passed
@devinrsmith devinrsmith deleted the dh-18803-sql-vector-types branch March 4, 2025 16:59
@github-actions github-actions bot locked and limited conversation to collaborators Mar 4, 2025
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.

2 participants