sun.misc.Unsafe usage in Zero-Allocation-Hashing will be deprecated - what is Parquet's plan?
- Lenguaje dominante
- Java
- Estrellas
- 3.1k
- Forks
- 1.6k
- Merge medio
- 3 d 12 h
- PR fusionados (30 d)
- 33
Descripción
### 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_
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
En el issue no se identifican archivos fuente ni pruebas. Empieza revisando la dependencia de parquet-java respecto de Zero-Allocation-Hashing y el issue upstream vinculado sobre el reemplazo de sun.misc.Unsafe; después, compara las tres opciones propuestas. Se considera terminado cuando el proyecto haya acordado el siguiente paso para evitar el riesgo de deprecación.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- data-engineering
- Tipo de issue
- Error
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 30/100