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

Row group pruning predicate does not coerce data types. #992

Closed
v0y4g3r opened this issue Feb 14, 2023 · 0 comments · Fixed by #1839
Closed

Row group pruning predicate does not coerce data types. #992

v0y4g3r opened this issue Feb 14, 2023 · 0 comments · Fixed by #1839
Assignees
Labels
C-bug Category Bugs

Comments

@v0y4g3r
Copy link
Contributor

v0y4g3r commented Feb 14, 2023

What type of bug is this?

Unexpected error

What subsystems are affected?

Datanode

What happened?

When passing time range predicate with a time unit differs from timestamp column time unit to prune row groups, it will fail to prune row groups since built binary expression does not coerce time units (arrow considers timestamp with different unit as different data types).

What operating system did you use?

macOS Montery

Relevant log output and stack trace

2023-02-14T08:47:31.317143Z ERROR table::predicate: Failed to create predicate for expr, error: Internal("The type of Timestamp(Millisecond, None) >= Timestamp(Second, None) of binary physical should be same")


### How can we reproduce the bug?

```bash
1. Create a table with ts column in milliseconds;
2. Create a query condition on ts column with time unit seconds;
3. Using that query condition to prune row groups and it will report an error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category Bugs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant