[jira] [Updated] (CALCITE-5950) Default column constraint is erroneously processed.

[ https://issues.apache.org/jira/browse/CALCITE-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated CALCITE-5950: Fix Version/s: 1.36.0 > Default column constraint is erroneously processed. > ---

[jira] [Updated] (CALCITE-6038) Remove 'Order By x Limit n' when the input is guaranteed that is at most one row

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Description: When a Sort represents 'Order By x Limit n',and its input is guaranteed that is at most

[jira] [Comment Edited] (CALCITE-6038) Remove 'Order By x Limit n' when the input is guaranteed that is at most one row

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774309#comment-17774309 ] LakeShen edited comment on CALCITE-6038 at 10/12/23 5:43 AM:

[jira] [Updated] (CALCITE-6038) Remove 'Order By x Limit n' when the input is guaranteed that is at most one row

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Description: When a Sort represents 'Order By x Limit n',and its input is guaranteed that is at most

[jira] [Updated] (CALCITE-6038) Remove 'Order By x Limit n' when the input is guaranteed that is at most one row

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Summary: Remove 'Order By x Limit n' when the input is guaranteed that is at most one row (was: Rem

[jira] [Updated] (CALCITE-6038) Remove 'Order By x Limit n' when the input is guaranteed that is at most one row

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Description: When a Sort represents 'Order By x Limit n',and its input source row count is provably

[jira] [Updated] (CALCITE-6038) Remove 'Order By x Limit n'' when the input is guaranteed that is at most one row

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Description: When a Sort is ''TopN's input source row count is provably at most one row,then we coul

[jira] [Updated] (CALCITE-6038) Remove 'Order By x Limit n'' when the input is guaranteed that is at most one row

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Summary: Remove 'Order By x Limit n'' when the input is guaranteed that is at most one row (was: Re

[jira] [Updated] (CALCITE-6042) Add test cases for ARRAY-related functions by using spark array function(Spark Library)

[ https://issues.apache.org/jira/browse/CALCITE-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ran Tao updated CALCITE-6042: - Summary: Add test cases for ARRAY-related functions by using spark array function(Spark Library) (was:

[jira] [Commented] (CALCITE-6046) quoteStringLiteralUnicode returns unparsed string with u&' prefix, which will cause the SqlLiteral

[ https://issues.apache.org/jira/browse/CALCITE-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774311#comment-17774311 ] xiaogang zhou commented on CALCITE-6046: I understood, the problem is the parse

[jira] [Updated] (CALCITE-6038) Remove 'Limit n' when the input is guaranteed to never return more than 'n' rows

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Issue Type: Improvement (was: New Feature) > Remove 'Limit n' when the input is guaranteed to never

[jira] [Commented] (CALCITE-6038) Remove 'Limit n' when the input is guaranteed to never return more than 'n' rows

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774309#comment-17774309 ] LakeShen commented on CALCITE-6038: --- Hi [~julianhyde] ,thank you for reminding me.You

[jira] [Commented] (CALCITE-6046) quoteStringLiteralUnicode returns unparsed string with u&' prefix, which will cause the SqlLiteral

[ https://issues.apache.org/jira/browse/CALCITE-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774304#comment-17774304 ] xiaogang zhou commented on CALCITE-6046: [~julianhyde]  Hi, I found this probl

[jira] [Created] (CALCITE-6047) Release Calcite 1.36.0

Benchao Li created CALCITE-6047: --- Summary: Release Calcite 1.36.0 Key: CALCITE-6047 URL: https://issues.apache.org/jira/browse/CALCITE-6047 Project: Calcite Issue Type: Task Reporte

[jira] [Commented] (CALCITE-6044) Column uniqueness for single-row relations

[ https://issues.apache.org/jira/browse/CALCITE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774298#comment-17774298 ] Julian Hyde commented on CALCITE-6044: -- I see; every other combination of columns

[jira] [Commented] (CALCITE-6044) Column uniqueness for single-row relations

[ https://issues.apache.org/jira/browse/CALCITE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774297#comment-17774297 ] Paul Jackson commented on CALCITE-6044: --- It would make sense to me if {{getUnique

[jira] [Updated] (CALCITE-6021) Add CURRENT_DATETIME function (enabled in BigQuery library)

[ https://issues.apache.org/jira/browse/CALCITE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-6021: - Fix Version/s: 1.36.0 > Add CURRENT_DATETIME function (enabled in BigQuery library) > -

[jira] [Commented] (CALCITE-6044) Column uniqueness for single-row relations

[ https://issues.apache.org/jira/browse/CALCITE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774267#comment-17774267 ] Julian Hyde commented on CALCITE-6044: -- This sounds right. However, beware trying

[jira] [Commented] (CALCITE-6045) CURRENT_TIMESTAMP has incorrect return type

[ https://issues.apache.org/jira/browse/CALCITE-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774265#comment-17774265 ] Julian Hyde commented on CALCITE-6045: -- This all sounds right. I have been feeling

[jira] [Commented] (CALCITE-6009) Add optimization to remove redundant LIMIT that is more than input row count

[ https://issues.apache.org/jira/browse/CALCITE-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774237#comment-17774237 ] Julian Hyde commented on CALCITE-6009: -- The way that this was combined with SORT_R

[jira] [Commented] (CALCITE-6038) Remove 'Limit n' when the input is guaranteed to never return more than 'n' rows

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774234#comment-17774234 ] Julian Hyde commented on CALCITE-6038: -- I am thoroughly confused. Does 'TopN' mean

[jira] [Commented] (CALCITE-6046) quoteStringLiteralUnicode returns unparsed string with u&' prefix, which will cause the SqlLiteral

[ https://issues.apache.org/jira/browse/CALCITE-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774227#comment-17774227 ] Julian Hyde commented on CALCITE-6046: -- Can you talk about the behavior rather tha

[jira] [Updated] (CALCITE-6038) Remove 'Limit n' when the input is guaranteed to never return more than 'n' rows

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-6038: - Summary: Remove 'Limit n' when the input is guaranteed to never return more than 'n' rows (was

[jira] [Commented] (CALCITE-6038) Remove redundant TopN when its input's row count is provably at most one row.

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774225#comment-17774225 ] Julian Hyde commented on CALCITE-6038: -- I changed the summary from "Remove redunda

[jira] [Updated] (CALCITE-5658) Collection types are un-parsed incorrectly for Apache Spark

[ https://issues.apache.org/jira/browse/CALCITE-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Massé updated CALCITE-5658: - Description: See [https://spark.apache.org/docs/latest/sql-ref-datatypes.html] Complex

[jira] [Resolved] (CALCITE-5993) Add CODE_POINTS_TO_STRING, TO_CODE_POINTS function (enabled in BigQuery library)

[ https://issues.apache.org/jira/browse/CALCITE-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanner Clary resolved CALCITE-5993. --- Resolution: Fixed Merged via [77b3689|https://github.com/apache/calcite/commit/77b3689e907

[jira] [Updated] (CALCITE-6038) Remove redundant TopN when its input's row count is provably at most one row.

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Fix Version/s: 1.36.0 > Remove redundant TopN when its input's row count is provably at most one row.

[jira] [Updated] (CALCITE-6038) Remove redundant TopN when its input's row count is provably at most one row.

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-6038: Labels: pull-request-available (was: ) > Remove redundant TopN when its input's row coun

[jira] [Created] (CALCITE-6046) quoteStringLiteralUnicode returns unparsed string with u&' prefix, which will cause the SqlLiteral

xiaogang zhou created CALCITE-6046: -- Summary: quoteStringLiteralUnicode returns unparsed string with u&' prefix, which will cause the SqlLiteral Key: CALCITE-6046 URL: https://issues.apache.org/jira/browse/CALCIT

[jira] [Updated] (CALCITE-6038) Remove redundant TopN when its input's row count is provably at most one row.

[ https://issues.apache.org/jira/browse/CALCITE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LakeShen updated CALCITE-6038: -- Component/s: core > Remove redundant TopN when its input's row count is provably at most one row. > -