JingsongLi opened a new pull request #10277: [FLINK-14595][orc] Move flink-orc 
to flink-formats from flink-connectors
URL: https://github.com/apache/flink/pull/10277
 
 
   
   ## What is the purpose of the change
   
   We already have the parent model of formats. we have put other 
formats(flink-avro, flink-json, flink-parquet, flink-json, flink-csv, 
flink-sequence-file) to flink-formats. flink-orc is a format too. So we can 
move it to flink-formats.
    
   In theory, there should be no compatibility problem, only the parent model 
needs to be changed, and no other changes are needed. 
    
   Discuss thread: 
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Move-flink-orc-to-flink-formats-from-flink-connectors-td34438.html
   Vote thread: 
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Move-flink-orc-to-flink-formats-from-flink-connectors-td34496.html
   
   ## Brief change log
   
   - Move flink-orc to flink-formats from flink-connectors
   - modify stage.sh
   
   ## Verifying this change
   
   This change is a code cleanup without any test coverage.
   
   ## 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, Yarn/Mesos, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to