Make ParquetReader(List<InputFile>, ParquetReadOptions, ReadSupport<T>) constructor public
- Lenguaje dominante
- Java
- Estrellas
- 3.1k
- Forks
- 1.6k
- Merge medio
- 3 d 12 h
- PR fusionados (30 d)
- 33
Descripción
My application uses s3 storage to store parquet files. The problem is that there is not ability to get rid from `new Configuration(true);` which load configuration from files:
`core-default.xml` and `core-site.xml` every time when ParquetReader instance is created.
I suggest just make ParquetReader(List, ParquetReadOptions, ReadSupport) constructor public then there will be ability to do custom builder.
**Reporter**: [Dmitry Sysolyatin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmsysolyatin)
#### PRs and other links:
- [GitHub Pull Request #707](https://github.com/apache/parquet-mr/pull/707)
**Note**: *This issue was originally created as [PARQUET-1719](https://issues.apache.org/jira/browse/PARQUET-1719). 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
Start at the ParquetReader(List, ParquetReadOptions, ReadSupport) constructor and inspect how the existing builder creates readers. Make the constructor publicly accessible so callers can create a custom builder without the unwanted Configuration loading, then verify the existing reader behavior remains intact.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- data
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 25/100