+1 (binding) verified sigs/sums/build/test
I did have some problems with the tests. It appears that you cannot run
specific project tests in isolation in some cases (e.g. mvn test -pl
parquet-tools fails, but works in conjunction with other tests). Nothing to
hold up the release for, but appe
shangxinli commented on pull request #808:
URL: https://github.com/apache/parquet-mr/pull/808#issuecomment-672148979
@gszadovszky Thanks for the correction of PARQUET-1784! Regarding the
serialized/deserialized, it is not done. I was aware of that when I use
ExtType. But that is somethi
shangxinli commented on pull request #808:
URL: https://github.com/apache/parquet-mr/pull/808#issuecomment-672093542
@ggershinsky, from what we have discussed above I think now the different
opinions narrow to 'how to transport the settings from the extended
ParquetWriteSupport to CryptoPr
[
https://issues.apache.org/jira/browse/PARQUET-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Szadovszky resolved PARQUET-1793.
---
Resolution: Won't Fix
> Support writing INT96 timestamp from avro
> ---
gszadovszky commented on pull request #808:
URL: https://github.com/apache/parquet-mr/pull/808#issuecomment-671925400
@shangxinli, The column-wise configuration you are talking about
(PARQUET-1784: Column-wise configuration (#754)) is only a specified key format
and the related helper impl
ggershinsky commented on pull request #808:
URL: https://github.com/apache/parquet-mr/pull/808#issuecomment-671793784
Yep, a couple of concerns related to encryption.
The stated goal of the crypto factory design is to be "transparent to
analytic frameworks, so they can leverage Parquet
