sun.misc.Unsafe usage in Zero-Allocation-Hashing will be deprecated - what is Parquet's plan?
- Langage dominant
- Java
- Étoiles
- 3.1k
- Forks
- 1.6k
- Merge moyen
- 3 j 12 h
- PR mergées (30 j)
- 33
Description
### Describe the bug, including details regarding any error messages, version, and platform.
The parquet-java repo depends on the [Zero-Allocation-Hashing](https://github.com/OpenHFT/Zero-Allocation-Hashing) library. That library uses `sun.misc.Unsafe`, which is being deprecated. As of the already-released JDK 24, uses of that library emit warnings (see [JEP 498](https://openjdk.org/jeps/498)). The library is slated to be deprecated after JDK 26, which probably means JDK 27 (or later). JDK 27 is scheduled to be released in September 2026.
So, parquet-java has two options:
1) Wait for Zero-Allocation-Hashing to migrate away from uses of `sun.misc.Unsafe`. There is [an issue](https://github.com/OpenHFT/Zero-Allocation-Hashing/issues/94) in that repo for this work. However, it's unclear to me how much attention the repo gets. The last release was in 2021, and the last commit was 5 months ago. So, parquet-java may or may not be able to rely on that repo to do the required fixes.
2) Use another library, which does not use sun.misc.Unsafe.
3) Write a new version, inside the parquet-java repo.
I want to bring this issue up so the contributors here are aware of the issue. What should the next steps be?
### Component(s)
_No response_
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Aucun fichier source ni test n’est identifié dans l’issue. Commencez par examiner la dépendance de parquet-java à Zero-Allocation-Hashing et l’issue upstream liée au remplacement de sun.misc.Unsafe, puis comparez les trois options proposées. Le travail est considéré comme terminé lorsque le projet s’est accordé sur la prochaine étape pour éviter le risque de dépréciation.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- data-engineering
- Type d'issue
- Bug
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 30/100