Interface IcebergCompactionConfiguration.Builder
- All Superinterfaces:
Buildable
,CopyableBuilder<IcebergCompactionConfiguration.Builder,
,IcebergCompactionConfiguration> SdkBuilder<IcebergCompactionConfiguration.Builder,
,IcebergCompactionConfiguration> SdkPojo
- Enclosing class:
IcebergCompactionConfiguration
-
Method Summary
Modifier and TypeMethodDescriptiondeleteFileThreshold
(Integer deleteFileThreshold) The minimum number of deletes that must be present in a data file to make it eligible for compaction.minInputFiles
(Integer minInputFiles) The minimum number of data files that must be present in a partition before compaction will actually compact files.The strategy to use for compaction.strategy
(CompactionStrategy strategy) The strategy to use for compaction.Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder
copy
Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder
applyMutation, build
Methods inherited from interface software.amazon.awssdk.core.SdkPojo
equalsBySdkFields, sdkFieldNameToField, sdkFields
-
Method Details
-
strategy
The strategy to use for compaction. Valid values are:
-
binpack
: Combines small files into larger files, typically targeting sizes over 100MB, while applying any pending deletes. This is the recommended compaction strategy for most use cases. -
sort
: Organizes data based on specified columns which are sorted hierarchically during compaction, improving query performance for filtered operations. This strategy is recommended when your queries frequently filter on specific columns. To use this strategy, you must first define a sort order in your Iceberg table properties using thesort_order
table property. -
z-order
: Optimizes data organization by blending multiple attributes into a single scalar value that can be used for sorting, allowing efficient querying across multiple dimensions. This strategy is recommended when you need to query data across multiple dimensions simultaneously. To use this strategy, you must first define a sort order in your Iceberg table properties using thesort_order
table property.
If an input is not provided, the default value 'binpack' will be used.
- Parameters:
strategy
- The strategy to use for compaction. Valid values are:-
binpack
: Combines small files into larger files, typically targeting sizes over 100MB, while applying any pending deletes. This is the recommended compaction strategy for most use cases. -
sort
: Organizes data based on specified columns which are sorted hierarchically during compaction, improving query performance for filtered operations. This strategy is recommended when your queries frequently filter on specific columns. To use this strategy, you must first define a sort order in your Iceberg table properties using thesort_order
table property. -
z-order
: Optimizes data organization by blending multiple attributes into a single scalar value that can be used for sorting, allowing efficient querying across multiple dimensions. This strategy is recommended when you need to query data across multiple dimensions simultaneously. To use this strategy, you must first define a sort order in your Iceberg table properties using thesort_order
table property.
If an input is not provided, the default value 'binpack' will be used.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-
strategy
The strategy to use for compaction. Valid values are:
-
binpack
: Combines small files into larger files, typically targeting sizes over 100MB, while applying any pending deletes. This is the recommended compaction strategy for most use cases. -
sort
: Organizes data based on specified columns which are sorted hierarchically during compaction, improving query performance for filtered operations. This strategy is recommended when your queries frequently filter on specific columns. To use this strategy, you must first define a sort order in your Iceberg table properties using thesort_order
table property. -
z-order
: Optimizes data organization by blending multiple attributes into a single scalar value that can be used for sorting, allowing efficient querying across multiple dimensions. This strategy is recommended when you need to query data across multiple dimensions simultaneously. To use this strategy, you must first define a sort order in your Iceberg table properties using thesort_order
table property.
If an input is not provided, the default value 'binpack' will be used.
- Parameters:
strategy
- The strategy to use for compaction. Valid values are:-
binpack
: Combines small files into larger files, typically targeting sizes over 100MB, while applying any pending deletes. This is the recommended compaction strategy for most use cases. -
sort
: Organizes data based on specified columns which are sorted hierarchically during compaction, improving query performance for filtered operations. This strategy is recommended when your queries frequently filter on specific columns. To use this strategy, you must first define a sort order in your Iceberg table properties using thesort_order
table property. -
z-order
: Optimizes data organization by blending multiple attributes into a single scalar value that can be used for sorting, allowing efficient querying across multiple dimensions. This strategy is recommended when you need to query data across multiple dimensions simultaneously. To use this strategy, you must first define a sort order in your Iceberg table properties using thesort_order
table property.
If an input is not provided, the default value 'binpack' will be used.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-
minInputFiles
The minimum number of data files that must be present in a partition before compaction will actually compact files. This parameter helps control when compaction is triggered, preventing unnecessary compaction operations on partitions with few files. If an input is not provided, the default value 100 will be used.
- Parameters:
minInputFiles
- The minimum number of data files that must be present in a partition before compaction will actually compact files. This parameter helps control when compaction is triggered, preventing unnecessary compaction operations on partitions with few files. If an input is not provided, the default value 100 will be used.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
deleteFileThreshold
The minimum number of deletes that must be present in a data file to make it eligible for compaction. This parameter helps optimize compaction by focusing on files that contain a significant number of delete operations, which can improve query performance by removing deleted records. If an input is not provided, the default value 1 will be used.
- Parameters:
deleteFileThreshold
- The minimum number of deletes that must be present in a data file to make it eligible for compaction. This parameter helps optimize compaction by focusing on files that contain a significant number of delete operations, which can improve query performance by removing deleted records. If an input is not provided, the default value 1 will be used.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-