lsyldliu opened a new pull request, #21966:
URL: https://github.com/apache/flink/pull/21966

   ## What is the purpose of the change
   
   *As the issue description, currently we can't get Hadoop-related 
authentication information from flink-conf.yaml when create `ParquetReader` 
using S3AFileSystem in TM, but in JM, `SourceCoordinator` works well when 
getFileStatus from s3a. After taking a deep analysis of the source code, I 
found that on the JM side, we use Flink's own FileSystem to get `FileStatus`, 
which can get the authentication information from flink-conf.yaml; but on the 
TM side, we use Hadoop's own FileSystem to create footer, which can't get the 
authentication information, which is an inconsistent behavior and causes the 
problem of the issue description. So we should use Flink's FileSystem on both 
JM side and TM side.  This PR is a bugfix.*
   
   ## Brief change log
   
     - *Extracting the public class `ParquetInputFile`*
     - *Using the Flink FileSystem to create ParquetFileReader in TM*
   
   
   ## Verifying this change
   
   This change is already covered by existing tests in the parquet module.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (JavaDocs)
   


-- 
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: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to