You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2016/08/05 07:40:20 UTC
[jira] [Commented] (STORM-2023) Add calcite-core to
storm-sql-runtime
[ https://issues.apache.org/jira/browse/STORM-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409073#comment-15409073 ]
Jungtaek Lim commented on STORM-2023:
-------------------------------------
Compiled topology refers SqlFunctions on calcite-core which also depends on several sub-projects like avatica, linq4j, and so on.
I asked dev group of Calcite to how others handle such things (there seems no user group on Calcite) and would like to see suggested answers.
> Add calcite-core to storm-sql-runtime
> -------------------------------------
>
> Key: STORM-2023
> URL: https://issues.apache.org/jira/browse/STORM-2023
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-sql
> Affects Versions: 1.0.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
>
> storm-sql provides both "storm-sql-core" and "storm-sql-runtime". Former is for compiling sql to trident topology, and latter is for running compiled trident topology.
> While testing storm-sql feature I found compiled class codes refers calcite so calcite-core is needed at runtime.
> I'm not sure we can make calcite-core get out of storm-sql-runtime, so for now we can add calcite-core to storm-sql-runtime so that it can be available on transitive dependencies for storm-sql-runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)