[jira] [Resolved] (PARQUET-1739) Make Spark SQL support Column indexes

2021-01-29 Thread Yuming Wang (Jira)
[ https://issues.apache.org/jira/browse/PARQUET-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuming Wang resolved PARQUET-1739. -- Fix Version/s: 1.11.1 Resolution: Fixed > Make Spark SQL support Column indexes >

[jira] [Commented] (PARQUET-1967) Upgrade Zstd-jni to 1.4.8-2

2021-01-29 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/PARQUET-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17275478#comment-17275478 ] ASF GitHub Bot commented on PARQUET-1967: - dongjoon-hyun opened a new pull request #859: URL:

[GitHub] [parquet-mr] dongjoon-hyun opened a new pull request #859: PARQUET-1967: Upgrade Zstd-jni to 1.4.8-2

2021-01-29 Thread GitBox
dongjoon-hyun opened a new pull request #859: URL: https://github.com/apache/parquet-mr/pull/859 Make sure you have checked _all_ steps below. ### Jira - [ ] My PR addresses the following [Parquet Jira](https://issues.apache.org/jira/browse/PARQUET/) issues and references

[jira] [Created] (PARQUET-1967) Upgrade Zstd-jni to 1.4.8-2

2021-01-29 Thread Dongjoon Hyun (Jira)
Dongjoon Hyun created PARQUET-1967: -- Summary: Upgrade Zstd-jni to 1.4.8-2 Key: PARQUET-1967 URL: https://issues.apache.org/jira/browse/PARQUET-1967 Project: Parquet Issue Type: Improvement

[jira] [Commented] (PARQUET-1966) Fix build with JDK11 for JDK8

2021-01-29 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/PARQUET-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274556#comment-17274556 ] ASF GitHub Bot commented on PARQUET-1966: - gszadovszky opened a new pull request #858: URL:

[GitHub] [parquet-mr] gszadovszky opened a new pull request #858: PARQUET-1966: Fix build with JDK11 for JDK8

2021-01-29 Thread GitBox
gszadovszky opened a new pull request #858: URL: https://github.com/apache/parquet-mr/pull/858 Make sure you have checked _all_ steps below. ### Jira - [ ] My PR addresses the following [Parquet Jira](https://issues.apache.org/jira/browse/PARQUET/) issues and references them

Re: [RESULT] Release Apache Parquet 1.12.0 RC1

2021-01-29 Thread Gidon Gershinsky
Thanks Gabor, a cool solution to this problem. I think it should be fine for the encryption feature. The writing path I've mentioned below, is rather atypical; we don't need this function in most cases. A framework that does use this path, would override the default implementation. Cheers, Gidon

[jira] [Created] (PARQUET-1966) Fix build with JDK11 for JDK8

2021-01-29 Thread Gabor Szadovszky (Jira)
Gabor Szadovszky created PARQUET-1966: - Summary: Fix build with JDK11 for JDK8 Key: PARQUET-1966 URL: https://issues.apache.org/jira/browse/PARQUET-1966 Project: Parquet Issue Type: Bug

[RESULT] Release Apache Parquet 1.12.0 RC1

2021-01-29 Thread Gabor Szadovszky
Thanks a lot, Yuming, Aaron. This is clearly a show stopper. Let me give a -1 (binding) and therefore FAIL this vote. Thanks a lot everyone who took the time to validate. About the compatibility issue. I agree with Gidon that this change is necessary for the feature. The question is whether we

Re: [VOTE] Release Apache Parquet 1.12.0 RC1

2021-01-29 Thread Aaron Niskode-Dossett
I haven't seen this java.lang.NoSuchMethodError: java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer; problem before, but some research suggest that this can happen with JDK > 8 is used to compile code that gets run with JDK 8. Setting --source and --target alone do not address the problem, but

Re: [VOTE] Release Apache Parquet 1.12.0 RC1

2021-01-29 Thread Wang, Yuming
It seems there is something wrong with JDK 8: java.lang.NoSuchMethodError: java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer; at org.apache.parquet.bytes.CapacityByteArrayOutputStream.write(CapacityByteArrayOutputStream.java:197) at

Re: [VOTE] Release Apache Parquet 1.12.0 RC1

2021-01-29 Thread Gidon Gershinsky
Regarding the technical reason behind this addition - we needed it to enable encryption in one of the writing paths. Cheers, Gidon On Thu, Jan 28, 2021 at 7:09 PM Aaron Niskode-Dossett wrote: > My (non-binding) is that this is ok. In a different Apache project, we > didn't allow a change