[
https://issues.apache.org/jira/browse/CALCITE-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400479#comment-17400479
]
keaton drebes commented on CALCITE-4744:
----------------------------------------
Fixed the title, sorry.
That approach seems more reasonable, I'll try and make a PR that does this.
Is the best practice to make a new Jira issue? Or should I revise this one?
> Add config for StandardConvertlet table to change if windowed aggregation
> functions are decomposed
> --------------------------------------------------------------------------------------------------
>
> Key: CALCITE-4744
> URL: https://issues.apache.org/jira/browse/CALCITE-4744
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Reporter: keaton drebes
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I have a project that is working with windowed functions and we want to avoid
> the decomposition of certain aggregate functions (i.e. stddev) in the process
> of converting from an SqlNode to a RelNode. We have currently supported this
> by copying the entire StandardConvertlet table, and removing the convertlets
> responsible for this.
> It seems reasonable to control this behavior with a configuration for the
> StandardConvertlet table. Is this something that people would accept being
> merged into Calcite?
> I opened a draft PR to show the changes here:
> https://github.com/apache/calcite/pull/2496
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
