[
https://issues.apache.org/jira/browse/PARQUET-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394773#comment-14394773
]
Boris Peltekov commented on PARQUET-226:
----------------------------------------
I decided to do it by exposing ParquetProperties to the user. It was already
public. I just had to change once static method and its corresponding
invocations.
It also turned out that the constructors of ParquetWriter are way too many and
I decided to add a builder while marking the regular constructors for
deprecation.
Here is the pull request:
https://github.com/apache/incubator-parquet-mr/pull/157
> Introduce an interface for controlling the encoding per column
> --------------------------------------------------------------
>
> Key: PARQUET-226
> URL: https://issues.apache.org/jira/browse/PARQUET-226
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-mr
> Reporter: Boris Peltekov
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> There are use-cases in which it is advantageous to have control over the type
> of encoding used for a given column. To achieve this, the ParquetProperties
> class must be refactored to facilitate its subclassing. The constructors of
> ParquetWriter and (probably) InternalParquetRecordWriter have to be modified
> as well. All the internal parquet classes have to refrain from directly
> instantiating ParquetProperties and should accept the instance from outside.
> Currently me and my team are using a good amount of reflection and
> unenforceable assumptions in order to gain control of this behavior. I'd like
> to implement the interface change. Are you interested in this feature?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
