[jira] [Commented] (CALCITE-2072) Allow specification of geospatial functions in connection string
[
https://issues.apache.org/jira/browse/CALCITE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284038#comment-16284038
]
Julian Hyde commented on CALCITE-2072:
--
Fix would be a couple of lines
[here|https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/config/CalciteConnectionConfigImpl.java#L102],
a test similar to JdbcTest.testFunOracle(), and the aforementioned doc changes.
> Allow specification of geospatial functions in connection string
>
>
> Key: CALCITE-2072
> URL: https://issues.apache.org/jira/browse/CALCITE-2072
> Project: Calcite
> Issue Type: Bug
> Components: core
>Reporter: Michael Mior
>Assignee: Julian Hyde
>
> Per Julian's suggestion, it would be good if in addition to {{fun=oracle}},
> we could allow fun={{spatial}} and also a comma-separated list of possible
> operator tables.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CALCITE-2072) Allow specification of geospatial functions in connection string
[
https://issues.apache.org/jira/browse/CALCITE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274943#comment-16274943
]
Julian Hyde commented on CALCITE-2072:
--
I think it's a sibling to the user-defined functions section. There are people
who would never write a UDF that would like to enable/disable tables of
functions that someone else has written. From the user's perspective it's more
akin to choosing a SQL dialect. Nevertheless it is a form of "extensibility".
> Allow specification of geospatial functions in connection string
>
>
> Key: CALCITE-2072
> URL: https://issues.apache.org/jira/browse/CALCITE-2072
> Project: Calcite
> Issue Type: Bug
> Components: core
>Reporter: Michael Mior
>Assignee: Julian Hyde
>
> Per Julian's suggestion, it would be good if in addition to {{fun=oracle}},
> we could allow fun={{spatial}} and also a comma-separated list of possible
> operator tables.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CALCITE-2072) Allow specification of geospatial functions in connection string
[
https://issues.apache.org/jira/browse/CALCITE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274445#comment-16274445
]
Michael Mior commented on CALCITE-2072:
---
it seems like this could just be added to the existing subsection on functions
and operators. Is anything more than a one-line pointer to the existence of
operator tables needed?
> Allow specification of geospatial functions in connection string
>
>
> Key: CALCITE-2072
> URL: https://issues.apache.org/jira/browse/CALCITE-2072
> Project: Calcite
> Issue Type: Bug
> Components: core
>Reporter: Michael Mior
>Assignee: Julian Hyde
>
> Per Julian's suggestion, it would be good if in addition to {{fun=oracle}},
> we could allow fun={{spatial}} and also a comma-separated list of possible
> operator tables.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CALCITE-2072) Allow specification of geospatial functions in connection string
[
https://issues.apache.org/jira/browse/CALCITE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273667#comment-16273667
]
Julian Hyde commented on CALCITE-2072:
--
We already support comma-separated lists, e.g. {{fun=standard,oracle}}; but
there are only two tables currently. See
{{CalciteConnectionConfigImpl.operatorTable(String)}}.
I should have added operator tables when I added the "Extensibility" section of
the [Adapters page|http://calcite.apache.org/docs/adapter.html] (this won't be
published until after 1.15 but you can see a
[preview|https://github.com/apache/calcite/blob/master/site/_docs/adapter.md#extensibility])
but I forgot. Can someone please add a sub-section?
> Allow specification of geospatial functions in connection string
>
>
> Key: CALCITE-2072
> URL: https://issues.apache.org/jira/browse/CALCITE-2072
> Project: Calcite
> Issue Type: Bug
> Components: core
>Reporter: Michael Mior
>Assignee: Julian Hyde
>
> Per Julian's suggestion, it would be good if in addition to {{fun=oracle}},
> we could allow fun={{spatial}} and also a comma-separated list of possible
> operator tables.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
