Skip to content

Fix in clause handling of varchars in filter pushdown#9181

Merged
hashhar merged 1 commit intotrinodb:masterfrom
elonazoulay:fix_in_clause_filter
Sep 9, 2021
Merged

Fix in clause handling of varchars in filter pushdown#9181
hashhar merged 1 commit intotrinodb:masterfrom
elonazoulay:fix_in_clause_filter

Conversation

@elonazoulay
Copy link
Copy Markdown
Member

@elonazoulay elonazoulay commented Sep 9, 2021

In and not in clauses did not handle varchar correctly.

Fixes #9133

Copy link
Copy Markdown
Member

@hashhar hashhar left a comment

Choose a reason for hiding this comment

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

LGTM.

@elonazoulay Can you please add a "Fixes #xxx" to the PR description (would help when adding release notes).

else if (type instanceof VarcharType) {
return ((Slice) value).toStringUtf8();
}
return value;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In future we should handle all types explicitly here to avoid surprises.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

sounds good, will do!

@hashhar hashhar added this to the 362 milestone Sep 9, 2021
@hashhar hashhar merged commit b065b01 into trinodb:master Sep 9, 2021
@hashhar hashhar mentioned this pull request Sep 9, 2021
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

[Pinot connector] The IN condition does not work correctly for string values when using aggregate pushdown

2 participants