[GitHub] [parquet-mr] dbtsai commented on pull request #793: PARQUET-1866: Replace Hadoop ZSTD with JNI-ZSTD

dbtsai commented on pull request #793: URL: https://github.com/apache/parquet-mr/pull/793#issuecomment-637195534 @shangxinli do we have benchmark comparing to native hadoop codec both in size and speed? Thanks. This is an

[jira] [Commented] (PARQUET-1866) Replace Hadoop ZSTD with JNI-ZSTD

[ https://issues.apache.org/jira/browse/PARQUET-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121423#comment-17121423 ] ASF GitHub Bot commented on PARQUET-1866: - dbtsai commented on pull request #793: URL:

[jira] [Commented] (PARQUET-1866) Replace Hadoop ZSTD with JNI-ZSTD

[ https://issues.apache.org/jira/browse/PARQUET-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121421#comment-17121421 ] ASF GitHub Bot commented on PARQUET-1866: - dbtsai commented on pull request #793: URL:

[GitHub] [parquet-mr] dbtsai commented on pull request #793: PARQUET-1866: Replace Hadoop ZSTD with JNI-ZSTD

dbtsai commented on pull request #793: URL: https://github.com/apache/parquet-mr/pull/793#issuecomment-637193519 +1 @shangxinli and thank you for this contribution. This will allow users who are on order versions of hadoop that don't support native ZSTD to use ZSTD compression in

[jira] [Commented] (PARQUET-1684) [parquet-protobuf] default protobuf field values are stored as nulls

[ https://issues.apache.org/jira/browse/PARQUET-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121420#comment-17121420 ] ASF GitHub Bot commented on PARQUET-1684: - bagipriyank commented on pull request #702: URL:

[GitHub] [parquet-mr] bagipriyank commented on pull request #702: PARQUET-1684: dont store default protobuf values as null for proto3

bagipriyank commented on pull request #702: URL: https://github.com/apache/parquet-mr/pull/702#issuecomment-637192988 I submitted this pr after we started using it in production :) This is an automated message from the

[jira] [Resolved] (PARQUET-1850) toParquetMetadata method in ParquetMetadataConverter does not set dictionary page offset bit

[ https://issues.apache.org/jira/browse/PARQUET-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aniket Namadeo Mokashi resolved PARQUET-1850. - Resolution: Fixed > toParquetMetadata method in

[jira] [Assigned] (PARQUET-1850) toParquetMetadata method in ParquetMetadataConverter does not set dictionary page offset bit

[ https://issues.apache.org/jira/browse/PARQUET-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aniket Namadeo Mokashi reassigned PARQUET-1850: --- Assignee: Srinivas S T > toParquetMetadata method in

[jira] [Commented] (PARQUET-1850) toParquetMetadata method in ParquetMetadataConverter does not set dictionary page offset bit

[ https://issues.apache.org/jira/browse/PARQUET-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121187#comment-17121187 ] ASF GitHub Bot commented on PARQUET-1850: - asfgit closed pull request #789: URL:

[GitHub] [parquet-mr] asfgit closed pull request #789: PARQUET-1850: Fix dictionaryPageOffset flag setting in toParquetMetadata method

asfgit closed pull request #789: URL: https://github.com/apache/parquet-mr/pull/789 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

[jira] [Commented] (PARQUET-1684) [parquet-protobuf] default protobuf field values are stored as nulls

[ https://issues.apache.org/jira/browse/PARQUET-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121131#comment-17121131 ] ASF GitHub Bot commented on PARQUET-1684: - Fokko commented on pull request #702: URL:

[GitHub] [parquet-mr] Fokko commented on pull request #702: PARQUET-1684: dont store default protobuf values as null for proto3

Fokko commented on pull request #702: URL: https://github.com/apache/parquet-mr/pull/702#issuecomment-636951813 The main issue here is that there are no Protobuf committers active on the project anymore. Did someone already this patch already in a production environment?