jayzhan211 commented on issue #11513:
URL: https://github.com/apache/datafusion/issues/11513#issuecomment-2247320498
> // logical_string_view will be:
// LogicalPhysicalType(Arc(NativeType { logical: Utf8, physical: StringView
}))
What I would like to know is whether we really need `LogicalPhysicalType `
for tracking the arrow::DataType. If we only get the logical type from
arrow::DataType. These logical types are for logical planning, where we don't
care about the actual decoding. When we need to know the decoding in physical
planning stage, could we get the information from DFSchema (Arrow's Schema)?
For example, `StringView` is the actual decoding we used and we could find it
in `DFSchema`, we also know it's logical type is Utf8 based on the `into()`
called.
Instead of `LogicalPhysicalType` + `LogicalPhysicalSchema` to keep track of
the relation ship between the logical and physical type for one type, could we
get the unidirectional mapping of logical type from physical type? Lookup
`DFSchema` for the actual physical type.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org
