You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of PR #5358, we have done a significant refactoring of APIs in ParquetTools and marked a number of APIs as deprecated, which will be removed soon as part of issue #5362.
Once we have removed the deprecated APIs, we should do another round of refactoring with the following ideas:
Right now ParquetInstructions is used for reading and writing. We should consider bifurcating into an ImmutableStyle ReadInstructions and WriteInstructions and move instructions like isRefreshing into read-only instructions, and index columns as write-only instructions, and so on.
Right now, we have writeTable for writing a single table, writeTables for writing Table[] and writeKeyValuePartitionedTable for partitioned writing of Table or PartitionedTable. We can refactor them to only expose a writeTable. writeTables should be covered by accepting a PartitionedTableFactory.of(Table[]) and writing them out as a flat partitioned table. Partitioned writing should be indicated by providing a KV_PARTITIONED layout instead of a separate API.
The text was updated successfully, but these errors were encountered:
As part of PR #5358, we have done a significant refactoring of APIs in ParquetTools and marked a number of APIs as deprecated, which will be removed soon as part of issue #5362.
Once we have removed the deprecated APIs, we should do another round of refactoring with the following ideas:
writeTable
for writing a single table,writeTables
for writingTable[]
andwriteKeyValuePartitionedTable
for partitioned writing ofTable
orPartitionedTable
. We can refactor them to only expose awriteTable
.writeTables
should be covered by accepting aPartitionedTableFactory.of(Table[])
and writing them out as a flat partitioned table. Partitioned writing should be indicated by providing a KV_PARTITIONED layout instead of a separate API.The text was updated successfully, but these errors were encountered: