-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Include ksqldb-rocksdb-config-setter jar in distributed artifacts #6838
Comments
There's another workaround documented in #6644: besides building the config setter module themselves, users can copy the jar from our maven repo. |
@wcarlson5 should this be labeled for 0.18? |
specifically ,how to alter ksql-run-class in order to use ksqldb-rocksdb-config-setter? Do you mean download ksqldb code ,compile ksqldb-rocksdb-config-setter.jar,upload it to some dir on ksqldb server,then add dir path to KSQL_CLASSPATH in ksql-run-class? |
I download jar here : it works when I put it in dir /ksqldb/customclass |
by the way do you know the effect of setting
|
The How to Limit Memory Usage in ksqlDB blog post details the use of
KsqlBoundedMemoryRocksDBConfigSetter
, but the containing jar is not on the classpath – nor included at all in releases, including the standalone Docker image.This yields the following when the custom config setter is otherwise correctly configured:
At minimum, we should ensure that the
ksqldb-rocksdb-config-setter
jar is included in distributed artifacts. We should consider alteringksql-run-class
to automatically add it to the classpath.As a workaround, users of the standalone Docker image would need to build the
ksqldb-rocksdb-config-setter
jar at the release version, mount it in the container, and ensure it is added to the classpath.The text was updated successfully, but these errors were encountered: