Skip to content

Conversation

@liukun4515
Copy link
Contributor

Which issue does this PR close?

Closes #2782

Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

@github-actions github-actions bot added the physical-expr Changes to the physical-expr crates label Jun 27, 2022
@liukun4515 liukun4515 force-pushed the inList_UTF_null_#2782 branch from 305c606 to 68566b0 Compare June 27, 2022 09:00
ColumnarValue::Scalar(s) => match s {
ScalarValue::$SCALAR_VALUE(Some(v)) => Some(*v),
ScalarValue::$SCALAR_VALUE(None) => None,
ScalarValue::Utf8(None) => None,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

#2764 merged, we don't need to treat Null as UTF8(None).

ScalarValue::$SCALAR_VALUE(None) => None,
ScalarValue::Utf8(None) => None,
datatype => unimplemented!("Unexpected type {} for InList", datatype),
datatype => unreachable!("InList can't reach other data type {} for {}.", datatype, s),
Copy link
Contributor Author

Choose a reason for hiding this comment

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

the expr and list_expr has the same data type, the code can't reach this point

@viirya viirya merged commit 7617d78 into apache:master Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

physical-expr Changes to the physical-expr crates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

InList: Don't treat Null as UTF8(None)

3 participants