[
https://issues.apache.org/jira/browse/CALCITE-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608128#comment-17608128
]
Bertil Chapuis edited comment on CALCITE-5280 at 9/22/22 7:58 AM:
------------------------------------------------------------------
I added some aggregate functions in the following draft PR:
[https://github.com/apache/calcite/pull/2917]
To me, it is currently unclear how I should register these with !geo. My
initial thought was to do this in SqlOperatorTable.createSpatial, but the root
schema is only accessible in the CalciteCatalogReader.operatorTable method.
was (Author: bchapuis):
I added some aggregate functions in the following PR:
[https://github.com/apache/calcite/pull/2917]
To me, it is currently unclear how I should register these with !geo. My
initial thought was to do this in SqlOperatorTable.createSpatial, but the root
schema is only accessible in the CalciteCatalogReader.operatorTable method.
> 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)
