[
https://issues.apache.org/jira/browse/CALCITE-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722673#comment-17722673
]
Tanner Clary commented on CALCITE-5564:
---------------------------------------
[~julianhyde] I realized that currently PERCENTILE_CONT and PERCENTILE_DISC are
able to be parsed/validated but are not actually implemented (commit
[here|https://github.com/apache/calcite/commit/85953ceb99e07b95129f4934797760a88709fcf6].)
The case for their implementation is CALCITE-4666.
I was wondering whether it makes to sense to have this issue be the addition of
parsing/validation for BigQuery syntax and then the implementation for both the
standard and BigQuery could be added under CALCITE-4666. Let me know what you
think about this.
> Support 2-argument PERCENTILE_CONT, PERCENTILE_DISC aggregate functions (as
> in BigQuery)
> ----------------------------------------------------------------------------------------
>
> Key: CALCITE-5564
> URL: https://issues.apache.org/jira/browse/CALCITE-5564
> Project: Calcite
> Issue Type: Improvement
> Reporter: Tanner Clary
> Assignee: Tanner Clary
> Priority: Major
>
> Calcite currently has implementations for the {{PERCENTILE_CONT}} and
> {{PERCENTILE_DISC}} functions. Their syntax may be found
> [here|https://learn.microsoft.com/en-us/sql/t-sql/functions/percentile-cont-transact-sql?view=sql-server-ver16].
>
> BigQuery offers these functions as well, but the syntax is slightly
> different, and may be found
> [here|https://cloud.google.com/bigquery/docs/reference/standard-sql/functions-and-operators#percentile_cont].
> The main difference is that instead of using a {{WITHIN GROUP}} clause, the
> array is passed in directly as the first argument to the function.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
