Baymine opened a new issue, #66121:
URL: https://github.com/apache/doris/issues/66121

   ### Search before asking
   
   - [x] I had searched in the [issues](https://github.com/apache/doris/issues) 
and found no similar issues.
   
   ### Description
   
   A column-pruned Hive `TEXTFILE` query reads only the columns listed in 
`_col_idxs`, but the field splitter still scans every separator of each line — 
including trailing fields that are never used. For wide tables with many unused 
trailing columns this is wasted work proportional to the unused tail length of 
every row.
   
   ### Proposal
   
   On the query path, after the reader resolves `_col_idxs`, compute 
`max(_col_idxs) + 1` and pass it to the splitter as a split limit. The 
single-char, non-escape path of `HiveTextFieldSplitter` then stops as soon as 
it has emitted that many fields. Each emitted field is still bounded by its own 
separator, so the produced prefix is byte-identical to a full split, and the 
reader only needs those prefix columns — query results are unchanged.
   
   The escape-configured path, the multi-char (KMP) path, and 
`EncloseCsvTextFieldSplitter` ignore the limit and split fully, so escaped 
separators and enclose quoting are unaffected. The load path is unaffected.
   
   ### Use case
   
   Faster scans of wide Hive `TEXTFILE` tables when queries select only a 
prefix of the columns.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to