GitHub user liancheng opened a pull request:

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

    [SPARK-6195] [SQL] Adds in-memory column type for fixed-precision decimals

    This PR adds a specialized in-memory column type for fixed-precision 
decimals.
    
    For all other column types, a single integer column type ID is enough to 
determine which column type to use. However, this doesn't apply to 
fixed-precision decimal types with different precision and scale parameters. 
Moreover, according to the previous design, there seems no trivial way to 
encode precision and scale information into the columnar byte buffer. On the 
other hand, considering we always know the data type of the column to be built 
/ scanned ahead of time. This PR no longer use column type ID to construct 
`ColumnBuilder`s and `ColumnAccessor`s, but resorts to the actual column data 
type. In this way, we can pass precision / scale information along the way.
    
    The column type ID is now not used anymore and can be removed in a future 
PR.

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

    $ git pull https://github.com/liancheng/spark decimal-column-type

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

    https://github.com/apache/spark/pull/4938.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 #4938
    
----
commit 4db713d51274c5f4d57de65b428ba57ee30c8255
Author: Cheng Lian <[email protected]>
Date:   2015-03-07T15:16:14Z

    Adds in-memory column type for fixed-precision decimals

----


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