GitHub user liancheng opened a pull request:

    https://github.com/apache/spark/pull/8988

    [SPARK-8848] [SQL] Refactors Parquet write path to follow parquet-format

    This PR refactors Parquet write path to follow parquet-format spec.  It's a 
successor of PR #7679, but with less non-essential changes.
    
    Major changes include:
    
    1.  Replaces `RowWriteSupport` and `MutableRowWriteSupport` with 
`CatalystWriteSupport`
    
        - Eliminates per value data type dispatching costs via prebuilt 
composed writer functions
        - Supports legacy mode which is compatible with Parquet format used by 
Spark 1.5 and prior versions
    
          The legacy mode is now by default on, and can be turned off by 
flipping SQL option `spark.sql.parquet.writeLegacyFormat` to `false`.
    
    1.  Cleans up the last pieces of old Parquet support code
    
    As pointed out by @rxin, we probably want to rename all those `Catalyst*` 
Parquet classes to `Parquet*` for clarity.  But I'd like to do this in a 
follow-up PR to minimize code review noises in this one.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/liancheng/spark 
spark-8848/standard-parquet-write-path

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/8988.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #8988
    
----
commit d1583f88507a32afb509d33313d0cbe02de4897a
Author: Cheng Lian <[email protected]>
Date:   2015-10-05T22:42:44Z

    Refactors Parquet write path to follow parquet-format

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

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

Reply via email to