apache / apache/parquet-java

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

Offen
#2,321 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Component: Java Component: Parquet Priority: Major Type: enhancement
Vorherrschende Sprache
Java
Sterne
3.1k
Forks
1.6k
Ø Merge
3 T. 12 Std.
Gemergte PRs (30 T.)
33

Beschreibung

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

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
java
Bereich
data-engineering
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
38/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.