Deprecate parquet-thrift
- Lenguaje dominante
- Java
- Estrellas
- 3.1k
- Forks
- 1.6k
- Merge medio
- 3 d 12 h
- PR fusionados (30 d)
- 33
Descripción
I was in the process of updating to [the latest version of Thrift](https://github.com/apache/parquet-mr/pull/1138) (from 0.16.0 to 0.19.0). Mostly because it contains CVEs and makes the release process easier because you don't have to install Thrift from source (it is just available on homebrew etc).
While working on this, I ran into an issue with Elephantbird, which is using a very old version of Thrift (0.7.0). Trying to bump this I noticed that a lot of classes that we use in the tests [have](https://github.com/apache/parquet-mr/pull/1156) [ been made private](https://github.com/apache/parquet-mr/pull/1156). Therefore it is hard to test if we break anything.
It looks like parquet-thrift [is not used by anyone anymore](https://mvnrepository.com/artifact/org.apache.parquet/parquet-thrift). I would suggest removing this from the repository unless anyone objects.
**Reporter**: [Fokko Driesprong](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fokko) / @Fokko
**Assignee**: [Fokko Driesprong](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fokko) / @Fokko
**Note**: *This issue was originally created as [PARQUET-2355](https://issues.apache.org/jira/browse/PARQUET-2355). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Comienza localizando el módulo parquet-thrift y comprobando sus usos en el repositorio; después, lee la documentación de migración enlazada y el contexto relacionado con la actualización de Thrift. La tarea estará terminada cuando parquet-thrift se haya eliminado del repositorio sin romper los módulos restantes ni la ruta de migración documentada.
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
- Refactorización
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 25/100