Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more options in HoodieWriteConfig #341

Merged
merged 1 commit into from Mar 14, 2018

Conversation

jianxu
Copy link
Contributor

@jianxu jianxu commented Mar 6, 2018

Adding two more options in HoodieWriteConfig.

  1. Change getParquetMaxFileSize from int to long.
  2. Expose withInputRecordStorageLevel, so that HoodieBloomIndex can persist the input record using user's configuration.

@@ -58,6 +58,8 @@
private static final String DEFAULT_ASSUME_DATE_PARTITIONING = "false";
private static final String HOODIE_WRITE_STATUS_CLASS_PROP = "hoodie.writestatus.class";
private static final String DEFAULT_HOODIE_WRITE_STATUS_CLASS = WriteStatus.class.getName();
private static final String INPUT_RECORD_STORAGE_LEVEL = "hoodie.input.record.storage.level";
private static final String DEFAULT_INPUT_RECORD_STORAGE_LEVEL = "MEMORY_AND_DISK_SER";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This must be a BloomIndex level config, since other indexes won't respect it anyway. lets move to HoodieIndexConfig

lets rename to hoodie.bloom.index.input.storage.level and relevant methods as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, will update.

@jianxu
Copy link
Contributor Author

jianxu commented Mar 13, 2018

@vinothchandar A new config hoodie.bloom.index.input.storage.level is added to HoodieIndexConfig. Please take another pass, thanks!

@vinothchandar vinothchandar merged commit ba7c258 into apache:master Mar 14, 2018
vinishjail97 pushed a commit to vinishjail97/hudi that referenced this pull request Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants