[
https://issues.apache.org/jira/browse/CALCITE-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608434#comment-17608434
]
Julian Hyde commented on CALCITE-5280:
--------------------------------------
{quote}
it is currently unclear how I should register these with !geo
{quote}
Is the problem that they are user-defined aggregate functions (UDAFs), and
UDAFs must be in a {{Schema}}, and can't be in a {{SqlOperatorTable}} (such as
the one built by {{fun=spatial}})?
The test infrastructure has things like
{{ConnectionFactories.AddSchemaPostProcessor}} for this kind of hackery.
> Implement geometry aggregate functions
> --------------------------------------
>
> Key: CALCITE-5280
> URL: https://issues.apache.org/jira/browse/CALCITE-5280
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Bertil Chapuis
> Assignee: Bertil Chapuis
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Geometry aggregate functions (ST_Accum, ST_Collect, and ST_Union) are
> currently missing in Calcite. Using an AggregateFunctionImpl looks be pretty
> straightforward, but many aggregate function implement SqlAggFunction
> directly.
> [~julianhyde] What would be the best way to implement them?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
