[ 
https://issues.apache.org/jira/browse/PARQUET-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694309#comment-17694309
 ] 

ASF GitHub Bot commented on PARQUET-2230:
-----------------------------------------

wgtmac opened a new pull request, #1036:
URL: https://github.com/apache/parquet-mr/pull/1036

   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [x] My PR addresses the following [Parquet 
Jira](https://issues.apache.org/jira/browse/PARQUET/) issues and references 
them in the PR title. 
     - https://issues.apache.org/jira/browse/PARQUET-2230
   
   ### Tests
   
   - [x] My PR does not need testing.
   
   ### Commits
   
   - [x] My commits all reference Jira issues in their subject lines. In 
addition, my commits follow the guidelines from "[How to write a good git 
commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [x] In case of new functionality, my PR adds documentation that describes 
how to use it.
     - Remove all deprecated commands supported by parquet-cli from README.md.




> Add a new rewrite command powered by ParquetRewriter
> ----------------------------------------------------
>
>                 Key: PARQUET-2230
>                 URL: https://issues.apache.org/jira/browse/PARQUET-2230
>             Project: Parquet
>          Issue Type: Sub-task
>          Components: parquet-cli
>            Reporter: Gang Wu
>            Assignee: Gang Wu
>            Priority: Major
>
> parquet-cli has several commands for rewriting files but missing a 
> consolidated one to provide the full features of ParquetRewriter.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to