[
https://issues.apache.org/jira/browse/CALCITE-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411114#comment-15411114
]
Julian Hyde commented on CALCITE-1349:
--------------------------------------
It's not clear to me that it's worth it to create a calcite-runtime module, or
indeed what would be in it. So far Storm is the only user of this; other
projects might need a runtime, but they're likely to need a slightly different
runtime. Let's wait and see what they need.
The {{SqlFunctions}} class should not depend on {{DataContext}}, because
{{DataContext}} depends on {{SchemaPlus}} and brings a lot else in.
It's OK that {{SqlFunctions}} depends on things in org.apache.calcite.linq4j.
> 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)
