[jira] [Comment Edited] (CALCITE-6317) Optimization CoreRules.PROJECT_REDUCE_EXPRESSIONS is unsound

[ https://issues.apache.org/jira/browse/CALCITE-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825487#comment-17825487 ] Jiajun Xie edited comment on CALCITE-6317 at 3/12/24 1:55 AM: -- For calcite

[jira] [Commented] (CALCITE-6317) Optimization CoreRules.PROJECT_REDUCE_EXPRESSIONS is unsound

[ https://issues.apache.org/jira/browse/CALCITE-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825487#comment-17825487 ] Jiajun Xie commented on CALCITE-6317: - For calcite user, the message maybe better: "Incorrect

[jira] [Created] (CALCITE-6318) Add some rules that WeTune discovers and verifies

Jiajun Xie created CALCITE-6318: --- Summary: Add some rules that WeTune discovers and verifies Key: CALCITE-6318 URL: https://issues.apache.org/jira/browse/CALCITE-6318 Project: Calcite Issue

[jira] [Commented] (CALCITE-6193) If a query has more than one subexpression that matches a materialized view, only the first is substituted

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824257#comment-17824257 ] Jiajun Xie commented on CALCITE-6193: - I was worried about side effects that from your PR, so I

[jira] [Updated] (CALCITE-6193) If a query has more than one subexpression that matches a materialized view, only the first is substituted

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6193: Fix Version/s: (was: 1.37.0) > If a query has more than one subexpression that matches a

[jira] [Comment Edited] (CALCITE-6193) If a query has more than one subexpression that matches a materialized view, only the first is substituted

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822079#comment-17822079 ] Jiajun Xie edited comment on CALCITE-6193 at 2/29/24 11:01 AM: --- [~4wei]

[jira] [Commented] (CALCITE-6193) If a query has more than one subexpression that matches a materialized view, only the first is substituted

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822079#comment-17822079 ] Jiajun Xie commented on CALCITE-6193: - [~4wei] Your thinking is too one-sided.   There are two

[jira] [Commented] (CALCITE-6193) If a query has more than one subexpression that matches a materialized view, only the first is substituted

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821912#comment-17821912 ] Jiajun Xie commented on CALCITE-6193: - [~4wei] , `undo` is another issue. Please create a new Jira

[jira] [Commented] (CALCITE-6193) If a query has more than one subexpression that matches a materialized view, only the first is substituted

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820966#comment-17820966 ] Jiajun Xie commented on CALCITE-6193: - [~4wei] , Can you answer my question in PR?

[jira] [Resolved] (CALCITE-6273) Add sqrt negative test in SqlOperatorTest

[ https://issues.apache.org/jira/browse/CALCITE-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6273. - Resolution: Fixed > Add sqrt negative test in SqlOperatorTest >

[jira] [Commented] (CALCITE-6273) Add sqrt negative test in SqlOperatorTest

[ https://issues.apache.org/jira/browse/CALCITE-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818608#comment-17818608 ] Jiajun Xie commented on CALCITE-6273: - Fixed in

[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=17816494#comment-17816494 ] Jiajun Xie commented on CALCITE-6214: - Fixed in

[jira] [Resolved] (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:all-tabpanel ] Jiajun Xie resolved CALCITE-6214. - Fix Version/s: 1.37.0 Resolution: Fixed > Remove DISTINCT in aggregate function if

[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-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

[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=17813676#comment-17813676 ] Jiajun Xie commented on CALCITE-6214: - Yes, empno is unique key, we can remove distinct for it. I

[jira] [Commented] (CALCITE-6193) If a query has more than one subexpression that matches a materialized view, only the first is substituted

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813203#comment-17813203 ] Jiajun Xie commented on CALCITE-6193: - BTW, [~4wei] Do you have benchmark for you PR? I would like

[jira] [Commented] (CALCITE-6193) If a query has more than one subexpression that matches a materialized view, only the first is substituted

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813202#comment-17813202 ] Jiajun Xie commented on CALCITE-6193: - [~4wei] Sorry, I don't have enough time to read your code.

[jira] [Commented] (CALCITE-6175) Upgrade OpenCSV to version 5

[ https://issues.apache.org/jira/browse/CALCITE-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811708#comment-17811708 ] Jiajun Xie commented on CALCITE-6175: - Look good. [~ymlai87416] , I am very interested in the

[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=17811647#comment-17811647 ] Jiajun Xie commented on CALCITE-6214: - I removed `AggregateRemoveDistinctRule` and added

[jira] [Resolved] (CALCITE-6199) Trim unused fields for SNAPSHOT and SAMPLE if table has VIRTUAL column

[ https://issues.apache.org/jira/browse/CALCITE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6199. - Fix Version/s: 1.37.0 Resolution: Fixed > Trim unused fields for SNAPSHOT and SAMPLE

[jira] [Commented] (CALCITE-6199) Trim unused fields for SNAPSHOT and SAMPLE if table has VIRTUAL column

[ https://issues.apache.org/jira/browse/CALCITE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811479#comment-17811479 ] Jiajun Xie commented on CALCITE-6199: - Fixed in

[jira] [Commented] (CALCITE-6222) Mysql does not have to_char function

[ https://issues.apache.org/jira/browse/CALCITE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811250#comment-17811250 ] Jiajun Xie commented on CALCITE-6222: - Calcite has many users, and any compatibility changes should

[jira] [Commented] (CALCITE-6222) Mysql does not have to_char function

[ https://issues.apache.org/jira/browse/CALCITE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811245#comment-17811245 ] Jiajun Xie commented on CALCITE-6222: - MariaDB have it: [https://mariadb.com/kb/en/to_char/] If

[jira] [Comment Edited] (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=17809214#comment-17809214 ] Jiajun Xie edited comment on CALCITE-6214 at 1/22/24 2:29 AM: -- 1. Changed

[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=17809214#comment-17809214 ] Jiajun Xie commented on CALCITE-6214: - 1. Changed `COUNT` to `aggregate function`. 2. RelBuilder

[jira] [Updated] (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:all-tabpanel ] Jiajun Xie updated CALCITE-6214: Summary: Remove DISTINCT in aggregate function if field is unique (was: Remove `DISTINCT` in

[jira] [Resolved] (CALCITE-3952) Improve SortRemoveRule to remove Sort based on rowcount

[ https://issues.apache.org/jira/browse/CALCITE-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-3952. - Resolution: Fixed > Improve SortRemoveRule to remove Sort based on rowcount >

[jira] [Commented] (CALCITE-6201) Merge Aggregate node if count distinct column has been deduplicated

[ https://issues.apache.org/jira/browse/CALCITE-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809092#comment-17809092 ] Jiajun Xie commented on CALCITE-6201: - Remove `DISTINCT` in count is a better solution. So I

[jira] [Resolved] (CALCITE-6201) Merge Aggregate node if count distinct column has been deduplicated

[ https://issues.apache.org/jira/browse/CALCITE-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6201. - Resolution: Duplicate > Merge Aggregate node if count distinct column has been deduplicated >

[jira] [Created] (CALCITE-6214) Remove `DISTINCT` in `COUNT` if field is unique

Jiajun Xie created CALCITE-6214: --- Summary: Remove `DISTINCT` in `COUNT` if field is unique Key: CALCITE-6214 URL: https://issues.apache.org/jira/browse/CALCITE-6214 Project: Calcite Issue

[jira] [Commented] (CALCITE-6206) Add library operator mapping for unparsing

[ https://issues.apache.org/jira/browse/CALCITE-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808006#comment-17808006 ] Jiajun Xie commented on CALCITE-6206: - I have seen similar features before. There are

[jira] [Updated] (CALCITE-6206) Add library operator mapping for unparsing

[ https://issues.apache.org/jira/browse/CALCITE-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6206: Attachment: image-2024-01-18-13-13-02-636.png > Add library operator mapping for unparsing >

[jira] [Updated] (CALCITE-6206) Add library operator mapping for unparsing

[ https://issues.apache.org/jira/browse/CALCITE-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6206: Attachment: (was: image-2024-01-18-13-13-02-636.png) > Add library operator mapping for

[jira] [Created] (CALCITE-6201) Merge Aggregate node if count distinct column has been deduplicated

Jiajun Xie created CALCITE-6201: --- Summary: Merge Aggregate node if count distinct column has been deduplicated Key: CALCITE-6201 URL: https://issues.apache.org/jira/browse/CALCITE-6201 Project: Calcite

[jira] [Created] (CALCITE-6200) RelJson throw UnsupportedOperationException for RexDynamicParam

Jiajun Xie created CALCITE-6200: --- Summary: RelJson throw UnsupportedOperationException for RexDynamicParam Key: CALCITE-6200 URL: https://issues.apache.org/jira/browse/CALCITE-6200 Project: Calcite

[jira] [Resolved] (CALCITE-3952) Improve SortRemoveRule to remove Sort based on rowcount

[ https://issues.apache.org/jira/browse/CALCITE-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-3952. - Resolution: Fixed > Improve SortRemoveRule to remove Sort based on rowcount >

[jira] [Updated] (CALCITE-3952) Improve SortRemoveRule to remove Sort based on rowcount

[ https://issues.apache.org/jira/browse/CALCITE-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-3952: Fix Version/s: 1.36.0 > Improve SortRemoveRule to remove Sort based on rowcount >

[jira] [Reopened] (CALCITE-3952) Improve SortRemoveRule to remove Sort based on rowcount

[ https://issues.apache.org/jira/browse/CALCITE-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie reopened CALCITE-3952: - > Improve SortRemoveRule to remove Sort based on rowcount >

[jira] [Commented] (CALCITE-3952) Improve SortRemoveRule to remove Sort based on rowcount

[ https://issues.apache.org/jira/browse/CALCITE-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17806419#comment-17806419 ] Jiajun Xie commented on CALCITE-3952: - I think that we solved it in 1.36 and I add two links. If

[jira] [Created] (CALCITE-6199) Trim unused fields for SNAPSHOT and SAMPLE if table has VIRTUAL column

Jiajun Xie created CALCITE-6199: --- Summary: Trim unused fields for SNAPSHOT and SAMPLE if table has VIRTUAL column Key: CALCITE-6199 URL: https://issues.apache.org/jira/browse/CALCITE-6199 Project:

[jira] [Updated] (CALCITE-6199) Trim unused fields for SNAPSHOT and SAMPLE if table has VIRTUAL column

[ https://issues.apache.org/jira/browse/CALCITE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6199: Description: RelFieldTrimmer not support SNAPSHOT( So do Sample) * Here is a SQL example

[jira] [Commented] (CALCITE-6193) SubstitutionVisitor stop trying incorrect subtree because of wrong parent relationship when replace query

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17806244#comment-17806244 ] Jiajun Xie commented on CALCITE-6193: - I think the root cause is always

[jira] [Comment Edited] (CALCITE-6193) SubstitutionVisitor stop trying incorrect subtree because of wrong parent relationship when replace query

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805862#comment-17805862 ] Jiajun Xie edited comment on CALCITE-6193 at 1/12/24 2:30 AM: -- [~4wei] ,

[jira] [Commented] (CALCITE-6193) SubstitutionVisitor stop trying incorrect subtree because of wrong parent relationship when replace query

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805862#comment-17805862 ] Jiajun Xie commented on CALCITE-6193: - [~4wei] , Do you try to use

[jira] [Commented] (CALCITE-6193) SubstitutionVisitor stop trying incorrect subtree because of wrong parent relationship when replace query

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804970#comment-17804970 ] Jiajun Xie commented on CALCITE-6193: - [~4wei] Yes, your PR is at work for that simple case. >

[jira] [Comment Edited] (CALCITE-6193) SubstitutionVisitor stop trying incorrect subtree because of wrong parent relationship when replace query

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804944#comment-17804944 ] Jiajun Xie edited comment on CALCITE-6193 at 1/10/24 2:22 AM: -- The issue

[jira] [Commented] (CALCITE-6193) SubstitutionVisitor stop trying incorrect subtree because of wrong parent relationship when replace query

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804944#comment-17804944 ] Jiajun Xie commented on CALCITE-6193: - The issue is not related to the filter condition.   The

[jira] [Comment Edited] (CALCITE-6193) SubstitutionVisitor stop trying incorrect subtree because of wrong parent relationship when replace query

[ https://issues.apache.org/jira/browse/CALCITE-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804944#comment-17804944 ] Jiajun Xie edited comment on CALCITE-6193 at 1/10/24 2:22 AM: -- The issue

[jira] [Resolved] (CALCITE-6191) Remove join if input is one row literal

[ https://issues.apache.org/jira/browse/CALCITE-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6191. - Resolution: Fixed > Remove join if input is one row literal >

[jira] [Created] (CALCITE-6191) Remove join if input is one row literal

Jiajun Xie created CALCITE-6191: --- Summary: Remove join if input is one row literal Key: CALCITE-6191 URL: https://issues.apache.org/jira/browse/CALCITE-6191 Project: Calcite Issue Type:

[jira] [Commented] (CALCITE-6131) There are duplicate sample tests in SqlTypeUtilTest

[ https://issues.apache.org/jira/browse/CALCITE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795565#comment-17795565 ] Jiajun Xie commented on CALCITE-6131: - Fixed in

[jira] [Resolved] (CALCITE-6131) There are duplicate sample tests in SqlTypeUtilTest

[ https://issues.apache.org/jira/browse/CALCITE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6131. - Resolution: Fixed > There are duplicate sample tests in SqlTypeUtilTest >

[jira] [Resolved] (CALCITE-5811) Error messages produced for constant out-of-bounds arguments are confusing

[ https://issues.apache.org/jira/browse/CALCITE-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-5811. - Resolution: Fixed > Error messages produced for constant out-of-bounds arguments are confusing

[jira] [Updated] (CALCITE-5811) Error messages produced for constant out-of-bounds arguments are confusing

[ https://issues.apache.org/jira/browse/CALCITE-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-5811: Fix Version/s: 1.37.0 > Error messages produced for constant out-of-bounds arguments are

[jira] [Commented] (CALCITE-5811) Error messages produced for constant out-of-bounds arguments are confusing

[ https://issues.apache.org/jira/browse/CALCITE-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795562#comment-17795562 ] Jiajun Xie commented on CALCITE-5811: - Fixed in

[jira] [Commented] (CALCITE-5791) DDL commands ceased to work in 1.23-1.24 transition

[ https://issues.apache.org/jira/browse/CALCITE-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795558#comment-17795558 ] Jiajun Xie commented on CALCITE-5791: - I removed the label and 'Fix Versions'.   [~josefspillner]

[jira] [Updated] (CALCITE-5791) DDL commands ceased to work in 1.23-1.24 transition

[ https://issues.apache.org/jira/browse/CALCITE-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-5791: Fix Version/s: (was: 1.23.0) Labels: (was: newbie) > DDL commands ceased to

[jira] [Updated] (CALCITE-6145) Function 'TRIM' without parameters throw NullPointerException

[ https://issues.apache.org/jira/browse/CALCITE-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6145: Labels: newbie (was: easy-fix) > Function 'TRIM' without parameters throw NullPointerException

[jira] [Updated] (CALCITE-5525) GROUPING_ID() should be rewritten to GROUPING() for some dialects in RelToSqlConverter

[ https://issues.apache.org/jira/browse/CALCITE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-5525: Labels: newbie (was: easy-fix) > GROUPING_ID() should be rewritten to GROUPING() for some

[jira] [Updated] (CALCITE-6145) Function 'TRIM' without parameters throw NullPointerException

[ https://issues.apache.org/jira/browse/CALCITE-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6145: Labels: easy-fix (was: ) > Function 'TRIM' without parameters throw NullPointerException >

[jira] [Updated] (CALCITE-5525) GROUPING_ID() should be rewritten to GROUPING() for some dialects in RelToSqlConverter

[ https://issues.apache.org/jira/browse/CALCITE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-5525: Labels: easy-fix (was: ) > GROUPING_ID() should be rewritten to GROUPING() for some dialects in

[jira] [Commented] (CALCITE-6161) The equalsDeep of sqlCall should compare sqlOperator's sqlKind

[ https://issues.apache.org/jira/browse/CALCITE-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794928#comment-17794928 ] Jiajun Xie commented on CALCITE-6161: - [~jiefei30] I'm worried that the change will cause damage to

[jira] [Commented] (CALCITE-6123) DruidAdapterIT#testInterleaveBetweenAggregateAndGroupOrderByOnMetrics fails

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793695#comment-17793695 ] Jiajun Xie commented on CALCITE-6123: - [~zabetak], Nice work. After running CI again, I confirmed

[jira] [Resolved] (CALCITE-6093) Unstable unit test in Druid tests

[ https://issues.apache.org/jira/browse/CALCITE-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6093. - Resolution: Duplicate > Unstable unit test in Druid tests > -

[jira] [Commented] (CALCITE-6123) DruidAdapter2IT is failing

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792632#comment-17792632 ] Jiajun Xie commented on CALCITE-6123: - Thank you for your suggestion, [~libenchao]    Upgrading

[jira] [Commented] (CALCITE-6093) Unstable unit test in Druid tests

[ https://issues.apache.org/jira/browse/CALCITE-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792517#comment-17792517 ] Jiajun Xie commented on CALCITE-6093: - Zulu JDK8 seems to be stable and successful - Zulu JDK8: 3

[jira] [Commented] (CALCITE-6123) DruidAdapter2IT is failing

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792502#comment-17792502 ] Jiajun Xie commented on CALCITE-6123: - calcite-druid-dataset is innocent. The bug should be in

[jira] [Commented] (CALCITE-6140) Add percentile test on SqlParserTest

[ https://issues.apache.org/jira/browse/CALCITE-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790842#comment-17790842 ] Jiajun Xie commented on CALCITE-6140: - [~caicancai]  What do you mean the results?   You only

[jira] [Commented] (CALCITE-6123) DruidAdapter2IT is failing

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789626#comment-17789626 ] Jiajun Xie commented on CALCITE-6123: - Oh, I found the

[jira] [Commented] (CALCITE-6130) Transformation optimization of different physical conventions on the production of new physical nodes

[ https://issues.apache.org/jira/browse/CALCITE-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789288#comment-17789288 ] Jiajun Xie commented on CALCITE-6130: - I removed fix version 1.36.0 because 1.36.0 has been

[jira] [Updated] (CALCITE-6130) Transformation optimization of different physical conventions on the production of new physical nodes

[ https://issues.apache.org/jira/browse/CALCITE-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6130: Fix Version/s: (was: 1.36.0) > Transformation optimization of different physical conventions

[jira] [Commented] (CALCITE-6121) Invalid unparse for TIMESTAMP with SparkSqlDialect

[ https://issues.apache.org/jira/browse/CALCITE-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788216#comment-17788216 ] Jiajun Xie commented on CALCITE-6121: - Fixed in

[jira] [Resolved] (CALCITE-6121) Invalid unparse for TIMESTAMP with SparkSqlDialect

[ https://issues.apache.org/jira/browse/CALCITE-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6121. - Fix Version/s: 1.37.0 Resolution: Fixed > Invalid unparse for TIMESTAMP with

[jira] [Commented] (CALCITE-6123) DruidAdapter2IT is failing

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787571#comment-17787571 ] Jiajun Xie commented on CALCITE-6123: - It seems that there were many changes in the GitHub action

[jira] [Comment Edited] (CALCITE-6123) DruidAdapter2IT is failing

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787567#comment-17787567 ] Jiajun Xie edited comment on CALCITE-6123 at 11/19/23 7:25 AM: --- The first

[jira] [Commented] (CALCITE-6123) DruidAdapter2IT is failing

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787567#comment-17787567 ] Jiajun Xie commented on CALCITE-6123: - The first failed in the main branch is

[jira] [Updated] (CALCITE-6123) DruidAdapter2IT is failing

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6123: Attachment: image-2023-11-19-15-17-53-699.png > DruidAdapter2IT is failing >

[jira] [Commented] (CALCITE-6123) DruidAdapter2IT is failing

[ https://issues.apache.org/jira/browse/CALCITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787559#comment-17787559 ] Jiajun Xie commented on CALCITE-6123: - [~libenchao], I rerun *Druid Tests* in your PR:

[jira] [Commented] (CALCITE-6121) Invalid unparse for TIMESTAMP with SparkSqlDialect

[ https://issues.apache.org/jira/browse/CALCITE-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787467#comment-17787467 ] Jiajun Xie commented on CALCITE-6121: - +1, Presto does not support TIMESTAMP with precision.

[jira] [Assigned] (CALCITE-6121) Invalid unparse for TIMESTAMP with SparkSqlDialect

[ https://issues.apache.org/jira/browse/CALCITE-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie reassigned CALCITE-6121: --- Assignee: Jiajun Xie > Invalid unparse for TIMESTAMP with SparkSqlDialect >

[jira] [Commented] (CALCITE-6102) SqlWriter in SqlInsert's unparse start a list but does not end it

[ https://issues.apache.org/jira/browse/CALCITE-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786573#comment-17786573 ] Jiajun Xie commented on CALCITE-6102: - Fixed in

[jira] [Resolved] (CALCITE-6102) SqlWriter in SqlInsert's unparse start a list but does not end it

[ https://issues.apache.org/jira/browse/CALCITE-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6102. - Resolution: Fixed > SqlWriter in SqlInsert's unparse start a list but does not end it >

[jira] [Commented] (CALCITE-6102) SqlWriter in SqlInsert's unparse start a list but does not end it

[ https://issues.apache.org/jira/browse/CALCITE-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785716#comment-17785716 ] Jiajun Xie commented on CALCITE-6102: - [~jiefei30] You clearly explained the reason. If there were

[jira] [Resolved] (CALCITE-6088) SqlItemOperator fails in RelToSqlConverter

[ https://issues.apache.org/jira/browse/CALCITE-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie resolved CALCITE-6088. - Fix Version/s: 1.36.0 Resolution: Fixed > SqlItemOperator fails in RelToSqlConverter >

[jira] [Commented] (CALCITE-6088) SqlItemOperator fails in RelToSqlConverter

[ https://issues.apache.org/jira/browse/CALCITE-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782967#comment-17782967 ] Jiajun Xie commented on CALCITE-6088: - Fixed in

[jira] [Assigned] (CALCITE-6088) SqlItemOperator fails in RelToSqlConverter

[ https://issues.apache.org/jira/browse/CALCITE-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie reassigned CALCITE-6088: --- Assignee: Jiajun Xie > SqlItemOperator fails in RelToSqlConverter >

[jira] [Updated] (CALCITE-6093) Unstable unit test in Druid tests

[ https://issues.apache.org/jira/browse/CALCITE-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6093: Summary: Unstable unit test in Druid tests (was: Unstable unit tes in Druid tests) > Unstable

[jira] [Updated] (CALCITE-6093) Unstable unit tes in Druid tests

[ https://issues.apache.org/jira/browse/CALCITE-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6093: Description: FAILURE 38.6sec, 235 completed, 1 failed, 6 skipped,

[jira] [Created] (CALCITE-6093) Unstable unit tes in Druid tests

Jiajun Xie created CALCITE-6093: --- Summary: Unstable unit tes in Druid tests Key: CALCITE-6093 URL: https://issues.apache.org/jira/browse/CALCITE-6093 Project: Calcite Issue Type: Improvement

[jira] [Updated] (CALCITE-6091) Char that in array or map is truncated if CASE WHEN statement contains null

[ https://issues.apache.org/jira/browse/CALCITE-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6091: Summary: Char that in array or map is truncated if CASE WHEN statement contains null (was: Char

[jira] [Updated] (CALCITE-6091) Char that in array or map is truncated in CASE WHEN statement

[ https://issues.apache.org/jira/browse/CALCITE-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6091: Description: {code:java} select case when true then array('abc') when false then

[jira] [Commented] (CALCITE-6091) Char that in array or map is truncated in CASE WHEN statement

[ https://issues.apache.org/jira/browse/CALCITE-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782824#comment-17782824 ] Jiajun Xie commented on CALCITE-6091: - In fact, the issue has been resolved by

[jira] [Updated] (CALCITE-6091) Char that in array or map is truncated in CASE WHEN statement

[ https://issues.apache.org/jira/browse/CALCITE-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6091: Description: {code:java} select case when true then array('abc') when false then

[jira] [Updated] (CALCITE-6091) Char that in array is truncated in CASE WHEN statement

[ https://issues.apache.org/jira/browse/CALCITE-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6091: Description: {code:java} select case when true then array('abc') when false then

[jira] [Updated] (CALCITE-6091) Char that in array is truncated in CASE WHEN statement

[ https://issues.apache.org/jira/browse/CALCITE-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajun Xie updated CALCITE-6091: Affects Version/s: (was: 1.34.0) (was: 1.35.0)

[jira] [Created] (CALCITE-6091) Char that in array is truncated in CASE WHEN statement

Jiajun Xie created CALCITE-6091: --- Summary: Char that in array is truncated in CASE WHEN statement Key: CALCITE-6091 URL: https://issues.apache.org/jira/browse/CALCITE-6091 Project: Calcite

  1   2   3   4   5   6   >