Open yl-lisen opened 3 months ago
This is because it uses the columns from SELECT
to create the InputFormat
. For formats with schema information, like Protobuf, Avro, etc. they know how to get the wanted columns.
In order to make formats like CSV works, we will need to either initialize such format with the full table schema ( which means it will generate the full chunk of columns no matter how many columns are selected by the query. So it will be less efficient, but this will be a simpler change ), or we will need to refactor such formats and make them be able to skip reading some fields ( they will need to know the column mapping to figure out which fields to skip. The format will still need to parse the data, but it does not need to generate the unneeded columns).
agree it, we can make this scenario works first, next, do partial parsing optimization
Describe what's wrong
How to reproduce
there is error log
Error message and/or stacktrace
Additional context