apache / apache/parquet-java

ParquetWriter.Builder (and subclasses) instances are hard to reuse

Abierto
#2,321 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Component: Java Component: Parquet Priority: Major Type: enhancement
Lenguaje dominante
Java
Estrellas
3.1k
Forks
1.6k
Merge medio
3 d 12 h
PR fusionados (30 d)
33

Descripción

Hi,

The builders to create ParquetWriter and AvroParquetWriter are very useful, but unfortunately their instance are very hard to reuse when you want to build multiple instance of ParquetWriter for different files but similar settings.

This is a shame because that's one of the concern solved by the builder pattern: from one builder you can build multiple things with similar parameters.

It would be useful if either:
- it was possible to create a builder from a pre-existing builder (except for the file name)
- it was possible to change the file name specified in the builder (and not have it definable only via constructor of the builder).

This would allow people to pass a set of options in the form of a builder to an object responsible of generically instantiating a PaquetWriter for multiple files for example.

 

**Reporter**: [Victor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=victor.noel)

**Note**: *This issue was originally created as [PARQUET-1562](https://issues.apache.org/jira/browse/PARQUET-1562). 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 by locating ParquetWriter.Builder and the AvroParquetWriter builder subclasses. Compare the two requested reuse approaches and their builder state; done means one builder can create multiple writers for different files while preserving shared settings, with coverage for the supported builder types.

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
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
38/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.