[
https://issues.apache.org/jira/browse/HUDI-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Guo updated HUDI-5892:
----------------------------
Description:
See [https://github.com/apache/hudi/pull/7912/files] for more details
Note that this ticket may be split into separate improvement areas for clarify.
Configs in scope:
DYNAMODB_ENDPOINT_URL
AWS_ACCESS_KEY, AWS_SECRET_KEY (These configs should only be necessary if no
environmental variables are not set (to confirm with code))
CLEANER_COMMITS_RETAINED: when either "hoodie.cleaner.commits.retained",
"hoodie.cleaner.hours.retained", or "hoodie.cleaner.fileversions.retained" is
set, should we automatically use the corresponding clean policy?
PLAN_STRATEGY_CLASS_NAME to enum
Clustering around group size: PLAN_STRATEGY_MAX_BYTES_PER_OUTPUT_FILEGROUP
LAYOUT_TYPE
ORDERING_FIELD (PAYLOAD_ORDERING_FIELD_PROP_KEY)
PAYLOAD_CLASS_NAME ("hoodie.compaction.payload.class")
EQUALITY_SQL_QUERIES
KEYGENERATOR_TYPE (auto inference)
was:
See [https://github.com/apache/hudi/pull/7912/files] for more details
Note that this ticket may be split into separate improvement areas for clarify.
Configs in scope:
DYNAMODB_ENDPOINT_URL
AWS_ACCESS_KEY, AWS_SECRET_KEY (These configs should only be necessary if no
environmental variables are not set (to confirm with code))
CLEANER_COMMITS_RETAINED: when either "hoodie.cleaner.commits.retained",
"hoodie.cleaner.hours.retained", or "hoodie.cleaner.fileversions.retained" is
set, should we automatically use the corresponding clean policy?
PLAN_STRATEGY_CLASS_NAME to enum
Clustering around group size: PLAN_STRATEGY_MAX_BYTES_PER_OUTPUT_FILEGROUP
LAYOUT_TYPE
ORDERING_FIELD (PAYLOAD_ORDERING_FIELD_PROP_KEY)
PAYLOAD_CLASS_NAME ("hoodie.compaction.payload.class")
EQUALITY_SQL_QUERIES
> Code refactoring for config defaults and wiring
> -----------------------------------------------
>
> Key: HUDI-5892
> URL: https://issues.apache.org/jira/browse/HUDI-5892
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Ethan Guo
> Priority: Major
> Fix For: 0.14.0
>
>
> See [https://github.com/apache/hudi/pull/7912/files] for more details
> Note that this ticket may be split into separate improvement areas for
> clarify.
> Configs in scope:
> DYNAMODB_ENDPOINT_URL
> AWS_ACCESS_KEY, AWS_SECRET_KEY (These configs should only be necessary if no
> environmental variables are not set (to confirm with code))
> CLEANER_COMMITS_RETAINED: when either "hoodie.cleaner.commits.retained",
> "hoodie.cleaner.hours.retained", or "hoodie.cleaner.fileversions.retained" is
> set, should we automatically use the corresponding clean policy?
> PLAN_STRATEGY_CLASS_NAME to enum
> Clustering around group size: PLAN_STRATEGY_MAX_BYTES_PER_OUTPUT_FILEGROUP
> LAYOUT_TYPE
> ORDERING_FIELD (PAYLOAD_ORDERING_FIELD_PROP_KEY)
> PAYLOAD_CLASS_NAME ("hoodie.compaction.payload.class")
> EQUALITY_SQL_QUERIES
> KEYGENERATOR_TYPE (auto inference)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
