[jira] [Comment Edited] (CALCITE-6242) The "exists" library function throws a "param not found" error when a column is used in lambda evaluation logic.

[ https://issues.apache.org/jira/browse/CALCITE-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814021#comment-17814021 ] hongyu guo edited comment on CALCITE-6242 at 2/4/24 3:26 AM: - Thanks for

[jira] [Updated] (CALCITE-6242) The "exists" library function throws a "param not found" error when a column is used in lambda evaluation logic.

[ https://issues.apache.org/jira/browse/CALCITE-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanumath Rao Maduri updated CALCITE-6242: - Description: The following query is throwing a "param not found" in calcite

[jira] [Commented] (CALCITE-6242) The "exists" library function throws a "param not found" error when a column is used in lambda evaluation logic.

[ https://issues.apache.org/jira/browse/CALCITE-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814021#comment-17814021 ] hongyu guo commented on CALCITE-6242: - Thanks for report this! In CALCITE-3679, referencing columns

[jira] [Updated] (CALCITE-6242) The "exists" library function throws a "param not found" error when a column is used in lambda evaluation logic.

[ https://issues.apache.org/jira/browse/CALCITE-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongyu guo updated CALCITE-6242: Component/s: core (was: spark) > The "exists" library function throws a

[jira] [Commented] (CALCITE-1317) Rewrite "MAX" as "ORDER BY ... LIMIT ..."

[ https://issues.apache.org/jira/browse/CALCITE-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814003#comment-17814003 ] Julian Hyde commented on CALCITE-1317: -- [~jiajunbernoulli], I agree that those optimizations make

[jira] [Created] (CALCITE-6242) The "exists" library function throws a "param not found" error when a column is used in lambda evaluation logic.

Hanumath Rao Maduri created CALCITE-6242: Summary: The "exists" library function throws a "param not found" error when a column is used in lambda evaluation logic. Key: CALCITE-6242 URL:

[jira] [Updated] (CALCITE-6241) Add a few existing functions to Spark library

[ https://issues.apache.org/jira/browse/CALCITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] EveyWu updated CALCITE-6241: Description: Add Spark as a supported library for functions that have already been implemented for

[jira] [Updated] (CALCITE-6241) Add a few existing functions to Spark library

[ https://issues.apache.org/jira/browse/CALCITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-6241: Labels: pull-request-available (was: ) > Add a few existing functions to Spark library

[jira] [Updated] (CALCITE-6241) Add a few existing functions to Spark library

[ https://issues.apache.org/jira/browse/CALCITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] EveyWu updated CALCITE-6241: Description: Add Spark as a supported library for functions that have already been implemented for

[jira] [Updated] (CALCITE-6241) Add a few existing functions to Spark library

[ https://issues.apache.org/jira/browse/CALCITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] EveyWu updated CALCITE-6241: Priority: Minor (was: Major) > Add a few existing functions to Spark library >

[jira] [Created] (CALCITE-6241) Add a few existing functions to Spark library

EveyWu created CALCITE-6241: Summary: Add a few existing functions to Spark library Key: CALCITE-6241 URL: https://issues.apache.org/jira/browse/CALCITE-6241 Project: Calcite Issue Type:

[jira] [Updated] (CALCITE-6241) Add a few existing functions to Spark library

[ https://issues.apache.org/jira/browse/CALCITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] EveyWu updated CALCITE-6241: Description: Add Spark as a supported library for functions that have already been implemented for

[jira] [Commented] (CALCITE-1317) Rewrite "MAX" as "ORDER BY ... LIMIT ..."

[ https://issues.apache.org/jira/browse/CALCITE-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813895#comment-17813895 ] Jiajun Xie commented on CALCITE-1317: - Oh, I am thinking about similar optimizations recently: -

[jira] [Updated] (CALCITE-6240) Remove ROW_NUMBER if OVER PARTITION BY unique key

[ https://issues.apache.org/jira/browse/CALCITE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6240: Priority: Minor (was: Major) > Remove ROW_NUMBER if OVER PARTITION BY unique key >

[jira] [Updated] (CALCITE-6240) Remove ROW_NUMBER if OVER PARTITION BY unique key

[ https://issues.apache.org/jira/browse/CALCITE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6240: Summary: Remove ROW_NUMBER if OVER PARTITION BY unique key (was: Removed ROW_NUMBER if OVER

[jira] [Created] (CALCITE-6240) Removed ROW_NUMBER if OVER PARTITION BY unique key

Jiajun Xie created CALCITE-6240: --- Summary: Removed ROW_NUMBER if OVER PARTITION BY unique key Key: CALCITE-6240 URL: https://issues.apache.org/jira/browse/CALCITE-6240 Project: Calcite Issue

[jira] [Commented] (CALCITE-6237) Using fractions in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813889#comment-17813889 ] Alessandro Solimando commented on CALCITE-6237: --- Calcite is a powerful but complex SW,

[jira] [Commented] (CALCITE-6214) Remove DISTINCT in aggregate function if field is unique

[ https://issues.apache.org/jira/browse/CALCITE-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813884#comment-17813884 ] Jiajun Xie commented on CALCITE-6214: - Sorry, I misunderstood. The distinct can be removed if we