Open cyrilou242 opened 10 months ago
I can look into it, to make it slim. Thanks
Another approach is to remove the dependencies of pinot-common
, only pinot-spi
.
This might take longer time to finish.
We need to extract the SqlParser
out from the pinot-common
@cyrilou242 I think for now you may need to explicitly exclude libs from pinot-jdbc-client
Another approach is to remove the dependencies of
pinot-common
, onlypinot-spi
. This might take longer time to finish. We need to extract theSqlParser
out from thepinot-common
I can start looking into this, if it's the approach we want to take.
Some improvement to remove pinot-core
dependency from pinot-jdbc-client
: https://github.com/apache/pinot/pull/11620
Problem
Since 0.11.0,
pinot-jdbc-client
and pinotpinot-java-client
have a dependency onpinot-common
. See introductions: https://github.com/apache/pinot/commit/15e939818ca913bd9a5f0162300057c1a8b20f39 https://github.com/apache/pinot/commit/23a81d07b52dad6181b696562e07cdfa0932d191This introduces the following new dependencies to the clients:
This is a lot of new, unused dependencies for the client. Also notice that an implementation of log4j is included
org.apache.logging.log4j:log4j-slf4j-impl:jar:2.17.1:compile
, which is bad practice but easy to quickfix with an exclusion in the pom.Then for
pinot-jdbc-client
a dependency onpinot-core
was introduced: https://github.com/apache/pinot/commit/caf8d755820d6bf27bc7daeb74ac35d2e70caa61This introduces the following dependencies in the client
Impact: The pinot clients are too heavy and introduce too many unused dependencies that can conflict with the users's project. We are stuck on client
0.10.0
.Suggestion
From what I understand of the commits the goal of importing pinot-common and pinot-core was to get access to a few utils, and almost all of the dependencies are not used. I'd be nice to refactor dependencies to make the pinot clients light again.