Skip to content

Conversation

@ableegoldman
Copy link
Contributor

@ableegoldman ableegoldman commented May 1, 2025

Followup to #453 to make the filterBitsPerKey (and any future rs3/storage related settings) configurable by users for individual stores

@ableegoldman ableegoldman requested review from hachikuji and rodesai May 1, 2025 00:11
@ableegoldman ableegoldman force-pushed the RS3-RS3ConfigSetter branch from 4172ec4 to 58e01cb Compare May 1, 2025 00:12
*
* @return the configs to override for this store
*/
RS3StoreParams windowStoreConfig(String storeName, WindowSchema schema);
Copy link
Contributor

Choose a reason for hiding this comment

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

Perhaps we could return a more specific type (e.g. RS3WindowStoreParams) in case there are different configurations for the respective store?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah, that's probably the right thing to do...I considered that but ended up consolidating them to reduce API surface. But the problem with a generic RS3StoreParams is that it's up to the user to use the correct base/default configs for the given store type. Which will only become worse if we do have different configs for different store types in the furure

i'll go back to the store-specific params

@ableegoldman ableegoldman merged commit b3c32dc into main May 2, 2025
1 check passed
@ableegoldman ableegoldman deleted the RS3-RS3ConfigSetter branch May 2, 2025 03:46
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.

3 participants