Panic when handle schema evolution in vortex file #6264
Unanswered
haohuaijin
asked this question in
Issue Triage
Replies: 2 comments
-
|
thank you for your report! it seems like there's some deeper issue here as we've had other reports, I'll add this issue to that list. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think I'll track this thing here, I'll make this case into a testcase in my branch. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
In datafusion, parquet use
DefaultPhysicalExprAdapterFactorythat can register toListingTableto handle the schema evolution, for vortex i also register theDefaultPhysicalExprAdapterFactory, but it still have panic.Reproduction
Run the examples in this repo https://github.com/haohuaijin/schema-evolution
Scenario: Two files with different types for the
codecolumn:codeisUtf8(string: "A100", "B200", "C300")codeisInt64(integer: 400, 500, 600)Both examples use
DefaultPhysicalExprAdapterFactoryto handle schema evolution.Expected Behavior (Parquet)
Query succeeds with automatic type coercion (Int64 → Utf8):
Actual Behavior (Vortex)
Application panics:
Environment
Beta Was this translation helpful? Give feedback.
All reactions