Class TableOptimizerRun
- All Implemented Interfaces:
Serializable,SdkPojo,ToCopyableBuilder<TableOptimizerRun.Builder,TableOptimizerRun>
Contains details for a table optimizer run.
- See Also:
-
Nested Class Summary
Nested Classes -
Method Summary
Modifier and TypeMethodDescriptionstatic TableOptimizerRun.Builderbuilder()final CompactionMetricsACompactionMetricsobject containing metrics for the optimizer run.final CompactionStrategyThe strategy used for the compaction run.final StringThe strategy used for the compaction run.final InstantRepresents the epoch timestamp at which the compaction job ended.final booleanfinal booleanequalsBySdkFields(Object obj) final Stringerror()An error that occured during the optimizer run.final TableOptimizerEventTypeAn event type representing the status of the table optimizer run.final StringAn event type representing the status of the table optimizer run.final <T> Optional<T>getValueForField(String fieldName, Class<T> clazz) final inthashCode()final RunMetricsmetrics()Deprecated.Metrics has been replaced by optimizer type specific metrics such as IcebergCompactionMetricsAnOrphanFileDeletionMetricsobject containing metrics for the optimizer run.final RetentionMetricsARetentionMetricsobject containing metrics for the optimizer run.static Class<? extends TableOptimizerRun.Builder>final InstantRepresents the epoch timestamp at which the compaction job was started within Lake Formation.final StringtoString()Returns a string representation of this object.Methods inherited from class java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, waitMethods inherited from interface software.amazon.awssdk.utils.builder.ToCopyableBuilder
copy
-
Method Details
-
eventType
An event type representing the status of the table optimizer run.
If the service returns an enum value that is not available in the current SDK version,
eventTypewill returnTableOptimizerEventType.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available fromeventTypeAsString().- Returns:
- An event type representing the status of the table optimizer run.
- See Also:
-
eventTypeAsString
An event type representing the status of the table optimizer run.
If the service returns an enum value that is not available in the current SDK version,
eventTypewill returnTableOptimizerEventType.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available fromeventTypeAsString().- Returns:
- An event type representing the status of the table optimizer run.
- See Also:
-
startTimestamp
Represents the epoch timestamp at which the compaction job was started within Lake Formation.
- Returns:
- Represents the epoch timestamp at which the compaction job was started within Lake Formation.
-
endTimestamp
Represents the epoch timestamp at which the compaction job ended.
- Returns:
- Represents the epoch timestamp at which the compaction job ended.
-
metrics
Deprecated.Metrics has been replaced by optimizer type specific metrics such as IcebergCompactionMetricsA
RunMetricsobject containing metrics for the optimizer run.This member is deprecated. See the individual metric members for compaction, retention, and orphan file deletion.
- Returns:
- A
RunMetricsobject containing metrics for the optimizer run.This member is deprecated. See the individual metric members for compaction, retention, and orphan file deletion.
-
error
An error that occured during the optimizer run.
- Returns:
- An error that occured during the optimizer run.
-
compactionMetrics
A
CompactionMetricsobject containing metrics for the optimizer run.- Returns:
- A
CompactionMetricsobject containing metrics for the optimizer run.
-
compactionStrategy
The strategy used for the compaction run. Indicates which algorithm was applied to determine how files were selected and combined during the compaction process. 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_ordertable 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_ordertable property.
If the service returns an enum value that is not available in the current SDK version,
compactionStrategywill returnCompactionStrategy.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available fromcompactionStrategyAsString().- Returns:
- The strategy used for the compaction run. Indicates which algorithm was applied to determine how files
were selected and combined during the compaction process. 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_ordertable 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_ordertable property.
-
- See Also:
-
-
compactionStrategyAsString
The strategy used for the compaction run. Indicates which algorithm was applied to determine how files were selected and combined during the compaction process. 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_ordertable 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_ordertable property.
If the service returns an enum value that is not available in the current SDK version,
compactionStrategywill returnCompactionStrategy.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available fromcompactionStrategyAsString().- Returns:
- The strategy used for the compaction run. Indicates which algorithm was applied to determine how files
were selected and combined during the compaction process. 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_ordertable 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_ordertable property.
-
- See Also:
-
-
retentionMetrics
A
RetentionMetricsobject containing metrics for the optimizer run.- Returns:
- A
RetentionMetricsobject containing metrics for the optimizer run.
-
orphanFileDeletionMetrics
An
OrphanFileDeletionMetricsobject containing metrics for the optimizer run.- Returns:
- An
OrphanFileDeletionMetricsobject containing metrics for the optimizer run.
-
toBuilder
- Specified by:
toBuilderin interfaceToCopyableBuilder<TableOptimizerRun.Builder,TableOptimizerRun>
-
builder
-
serializableBuilderClass
-
hashCode
public final int hashCode() -
equals
-
equalsBySdkFields
- Specified by:
equalsBySdkFieldsin interfaceSdkPojo
-
toString
Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be redacted from this string using a placeholder value. -
getValueForField
-
sdkFields
-
sdkFieldNameToField
- Specified by:
sdkFieldNameToFieldin interfaceSdkPojo
-