apache / apache/parquet-java

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

Ouverte
#2,321 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Component: Java Component: Parquet Priority: Major Type: enhancement
Langage dominant
Java
Étoiles
3.1k
Forks
1.6k
Merge moyen
3 j 12 h
PR mergées (30 j)
33

Description

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.*

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
java
Domaine
data-engineering
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
38/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.