[
https://issues.apache.org/jira/browse/KAFKA-15193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743865#comment-17743865
]
Bruno Cadonna commented on KAFKA-15193:
---------------------------------------
This reduction would only apply to Kafka Streams users, since RocksDB is only
used there. The brokers do not use RocksDB. The Kafka Streams jar is usually
directly imported into Java applications and does not contain RocksDB. RocksDB
is merely a dependency of the Kafka Streams jar that is downloaded when the
client application that uses the Kafka Streams jar is built. That means the
size of the Kafka Streams jar would not be reduced. So, I think the right place
to optimize the size is in the client application and not in Kafka Streams. The
jar of the client application will benefit from the size reduction of the
platform-dependent RocksDB jar.
> Allow choosing Platform specific rocksDBJNI jar
> -----------------------------------------------
>
> Key: KAFKA-15193
> URL: https://issues.apache.org/jira/browse/KAFKA-15193
> Project: Kafka
> Issue Type: Improvement
> Components: build
> Reporter: Utkarsh Khare
> Assignee: Utkarsh Khare
> Priority: Major
>
> RocksDBJNI uber jar is currently at ~58MBs.
> There are smaller platform-specific jars available for RocksDB.
> This ticket is created to allow developers to choose platform-specific
> RocksDB jar via build arguments, which is much smaller and can considerably
> reduce the generated RPM size.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
