You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2017/11/30 23:44:00 UTC

[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&focusedCommentId=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)