[
https://issues.apache.org/jira/browse/STORM-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193911#comment-15193911
]
Robert Joseph Evans commented on STORM-1625:
--------------------------------------------
OK So I looked at how the code works for submission, and we should still be
able to move the SQL off to its own location and not be a part of lib, I
propose {{./sql-lib/}}. When running {{storm sql}} we would add everything in
that directory to the classpath. Additionally in
{{StormSqlImpl.packageTopology}} instead of just dumping out the generated code
we would also walk all of the jars in sql-lib and package them with it too.
This also opens up the possibility of having UDFs because we could add the UDF
jar to the classpath and to the newly packaged topology jar.
> guava dependency is being shipped inside storm distribution
> -----------------------------------------------------------
>
> Key: STORM-1625
> URL: https://issues.apache.org/jira/browse/STORM-1625
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core, storm-sql
> Reporter: Abhishek Agarwal
> Assignee: Abhishek Agarwal
>
> We shade guava classes inside storm-core so that client can work with any
> version of guava without any clashes. However, storm-sql-core has a
> transitive dependency on guava and thus the guava jar is still getting
> shipped in lib folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
