[
https://issues.apache.org/jira/browse/CALCITE-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15442111#comment-15442111
]
Julian Hyde commented on CALCITE-1349:
--------------------------------------
I've been thinking some more about this. Maybe we could move {{SqlFunctions}}
into the {{calcite-linq4j}} module, and solve the issue of its dependency on
{{DataContext}}. That module has only a few dependencies. (It does depend on
Guava, but it can use any reasonable version of Guava, so it shouldn't be an
issue.) Let me know what you think.
> Make runtime packages less depend on other libraries
> ----------------------------------------------------
>
> Key: CALCITE-1349
> URL: https://issues.apache.org/jira/browse/CALCITE-1349
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Jungtaek Lim
> Assignee: Julian Hyde
>
> I'm working on Storm SQL which uses Calcite to compile SQL to topology.
> Current implementation uses SqlFunctions to cover some operators so
> calcite-core and transitive dependencies are needed even though compiled
> topology in runtime.
> [~julianhyde] confirms that SqlFunctions depends on several classes from
> other libraries and some of them also pull other dependencies.
> So it would be better to address runtime package to less depend on other
> libraries (or modules). After doing that we could even maintain runtime
> package to separate module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
