CHENXCHEN opened a new pull request #35734:
URL: https://github.com/apache/spark/pull/35734


   ### What changes were proposed in this pull request?
   
   1. Add support for reading ORC/Parquet files with SymlinkTextInputFormat 
table
   2. Fix analyze table size for SymlinkTextInputFormat
   
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   1. Both trino(prestosql) and prestodb support reading ORC/Parquet, but Spark 
does not, Spark support other formats except ORC/Parquet format, and this PR 
add support for ORC/Parquet
   2. As follows example, analyze the table size will be 100 instead of 19999, 
which affects the join optimization, and it will attempt to deliver a large 
table broadcast if `manifest` file size is less than 
`spark.sql.autoBroadcastJoinThreshold`, and after this PR, analyze the table 
size will be 19999
   we have files:
   ```
   size      filepath
   100      hdfs:///path/to/table/manifest
   9999   hdfs:////path/to/other/part-1.parquet.orc
   10000  hdfs://path/to/other/part-2.parquet.orc
   
   content of `hdfs:///path/to/table/manifest` :
   hdfs:///path/to/other/part-1.parquet.orc
   hdfs:///path/to/other/part-2.parquet.orc
   
   
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as 
the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes 
- provide the console output, description and/or an example to show the 
behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to 
the released Spark versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some 
test cases that check the changes thoroughly including negative and positive 
cases if possible.
   If it was tested in a way different from regular unit tests, please clarify 
how you tested step by step, ideally copy and paste-able, so that other 
reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why 
it was difficult to add.
   If benchmark tests were added, please run the benchmarks in GitHub Actions 
for the consistent environment, and the instructions could accord to: 
https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
   -->
   


-- 
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