gaoshihang opened a new pull request, #7941:
URL: https://github.com/apache/hudi/pull/7941
### Change Logs
In BaseSparkCommitActionExecutor.java, This RDD is hardcoded as
persist(MEMORY_AND_DISK_SER)
` // TODO: Consistent contract in HoodieWriteClient regarding
preppedRecord storage level handling
JavaRDD<HoodieRecord<T>> inputRDD =
HoodieJavaRDD.getJavaRDD(inputRecords);
if (inputRDD.getStorageLevel() == StorageLevel.NONE()) {
inputRDD.persist(StorageLevel.MEMORY_AND_DISK_SER());
} else {
LOG.info("RDD PreppedRecords was persisted at: " +
inputRDD.getStorageLevel());
}`
But if we want to change its storage level, we have no way to use a
parameter.
### Impact
Add a new config: hoodie.spark.write.storage.level.
To specific the storage level of this RDD.
1. the config's default value is MEMORY_AND_DISK_SER
2. If set the config to another storage level
"hoodie.spark.write.storage.level": "DISK_ONLY"
3. If the storage level is wrong, It will throw exception
like set "hoodie.spark.write.storage.level": "DISKE_ONLY"
Caused by: java.lang.IllegalArgumentException: Invalid StorageLevel:
DISKE_ONLY
### Risk level (write none, low medium or high below)
Low
### Documentation Update
_Describe any necessary documentation update if there is any new feature,
config, or user-facing change_
- _The config description must be updated if new configs are added or the
default value of the configs are changed_
- _Any new feature or user-facing change requires updating the Hudi website.
Please create a Jira ticket, attach the
ticket number here and follow the
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to
make
changes to the website._
### Contributor's checklist
- [ ] Read through [contributor's
guide](https://hudi.apache.org/contribute/how-to-contribute)
- [ ] Change Logs and Impact were stated clearly
- [ ] Adequate tests were added if applicable
- [ ] CI passed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
