[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2024-04-11 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836172#comment-17836172 ] libopeng commented on CALCITE-5743: --- {code:java} LogicalProject(A=[$0])  

[jira] [Updated] (CALCITE-5570) Support nested map type for SqlDataTypeSpec

2023-08-28 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5570: -- Description: There was added a similar support for arrays/multisets at

[jira] [Assigned] (CALCITE-5583) JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column names

2023-08-22 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng reassigned CALCITE-5583: - Assignee: libopeng > JDBC adapter generates 'SELECT *', which is invalid SQL if there are >

[jira] [Updated] (CALCITE-5940) Add the Rules to optimize Limit

2023-08-20 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5940: -- Description: Now in calcite,the Limit will be represented using LogicalSort(fetch=[xx]),but there

[jira] [Commented] (CALCITE-5930) When sqlToRel is converted from in to join, condition '=' on both sides will have inconsistent data types.

2023-08-20 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756634#comment-17756634 ] libopeng commented on CALCITE-5930: --- Thanks for reminding. > When sqlToRel is converted from in to

[jira] [Commented] (CALCITE-5583) JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column names

2023-08-18 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755945#comment-17755945 ] libopeng commented on CALCITE-5583: --- I would appreciate it if you could help me review this

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755782#comment-17755782 ] libopeng commented on CALCITE-5743: --- [~shenlang] Unlike [CALCITE-5930], which records bugs caused by

[jira] [Commented] (CALCITE-5930) When sqlToRel is converted from in to join, condition '=' on both sides will have inconsistent data types.

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755779#comment-17755779 ] libopeng commented on CALCITE-5930: --- [~nobigo] Thank you for telling me, I will close this issue. >

[jira] [Closed] (CALCITE-5930) When sqlToRel is converted from in to join, condition '=' on both sides will have inconsistent data types.

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng closed CALCITE-5930. - Resolution: Duplicate > When sqlToRel is converted from in to join, condition '=' on both sides will

[jira] [Commented] (CALCITE-5583) JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column names

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1776#comment-1776 ] libopeng commented on CALCITE-5583: --- [~julianhyde] I'm sorry to bring up this issue again after such

[jira] [Comment Edited] (CALCITE-5930) When sqlToRel is converted from in to join, condition '=' on both sides will have inconsistent data types.

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755345#comment-17755345 ] libopeng edited comment on CALCITE-5930 at 8/17/23 11:52 AM: - calcite

[jira] [Closed] (CALCITE-5934) calcite avatica calculation error

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng closed CALCITE-5934. - Resolution: Duplicate > calcite avatica calculation error > - > >

[jira] [Commented] (CALCITE-5934) calcite avatica calculation error

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755412#comment-17755412 ] libopeng commented on CALCITE-5934: --- [~rubenql] Thanks for reminding me, I tried to run the above

[jira] [Comment Edited] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754397#comment-17754397 ] libopeng edited comment on CALCITE-5880 at 8/17/23 7:26 AM: I tried to

[jira] [Updated] (CALCITE-5934) calcite avatica calculation error

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5934: -- Description: Here's the raw data. {code:java} >

[jira] [Created] (CALCITE-5934) calcite avatica calculation error

2023-08-17 Thread libopeng (Jira)
libopeng created CALCITE-5934: - Summary: calcite avatica calculation error Key: CALCITE-5934 URL: https://issues.apache.org/jira/browse/CALCITE-5934 Project: Calcite Issue Type: Bug

[jira] [Updated] (CALCITE-5934) calcite avatica calculation error

2023-08-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5934: -- Description: {code:java} >

[jira] [Commented] (CALCITE-5930) When sqlToRel is converted from in to join, condition '=' on both sides will have inconsistent data types.

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755345#comment-17755345 ] libopeng commented on CALCITE-5930: --- calcite avatica has no type implicit conversion, so an error

[jira] [Commented] (CALCITE-5930) When sqlToRel is converted from in to join, condition '=' on both sides will have inconsistent data types.

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755341#comment-17755341 ] libopeng commented on CALCITE-5930: --- As far as I know, there are two places where the 'in' subquery

[jira] [Updated] (CALCITE-5930) When sqlToRel is converted from in to join, condition '=' on both sides will have inconsistent data types.

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5930: -- Description: Wrong calculation result {code:java} select * from dept where deptno in ( select

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754951#comment-17754951 ] libopeng commented on CALCITE-5743: --- [~shenlang]  {code:java} SELECT * FROM emp e WHERE cast(comm as

[jira] [Updated] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5743: -- Description: {code:java} SELECT a  FROM t1 t1  WHERE b IN (SELECT COUNT (*) FROM t2 WHERE

[jira] [Updated] (CALCITE-5930) When sqlToRel is converted from in to join, condition '=' on both sides will have inconsistent data types.

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5930: -- Summary: When sqlToRel is converted from in to join, condition '=' on both sides will have

[jira] [Commented] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754933#comment-17754933 ] libopeng commented on CALCITE-5930: --- I found that in sqlToRel, if the data type of the join condition

[jira] [Updated] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5930: -- Description: Wrong calculation result {code:java} select * from dept where deptno in ( select

[jira] [Updated] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5930: -- Description: Wrong calculation result {code:java} select * from dept where deptno in ( select

[jira] [Updated] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-15 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5930: -- Description: Wrong calculation result {code:java} select * from dept where deptno in ( select

[jira] [Comment Edited] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-15 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754661#comment-17754661 ] libopeng edited comment on CALCITE-5930 at 8/15/23 2:33 PM: [~shenlang] I

[jira] [Commented] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-15 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754661#comment-17754661 ] libopeng commented on CALCITE-5930: --- [~leepb] I have refined some information which I hope will be

[jira] [Updated] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-15 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5930: -- Description: Wrong calculation result {code:java} select * from dept where deptno in ( select

[jira] [Updated] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-15 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5930: -- Description: Wrong calculation result {code:java} select * from dept where deptno in ( select

[jira] [Updated] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-15 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5930: -- Description: {code:java} select * from dept where deptno in ( select count(*) from emp where

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-08-15 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754647#comment-17754647 ] libopeng commented on CALCITE-5743: --- Look at this issue [CALCITE-5930] > Query gives incorrect

[jira] [Created] (CALCITE-5930) When data types do not match, calcite may make a calculation error

2023-08-15 Thread libopeng (Jira)
libopeng created CALCITE-5930: - Summary: When data types do not match, calcite may make a calculation error Key: CALCITE-5930 URL: https://issues.apache.org/jira/browse/CALCITE-5930 Project: Calcite

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-08-15 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754530#comment-17754530 ] libopeng commented on CALCITE-5743: --- [~julianhyde] I think your case is caused by other bugs, and

[jira] [Commented] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754397#comment-17754397 ] libopeng commented on CALCITE-5880: --- I tried to verify 'null=null' using Quidem and found that Quidem

[jira] [Comment Edited] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754387#comment-17754387 ] libopeng edited comment on CALCITE-5880 at 8/15/23 3:46 AM: Sorry, I wasn't

[jira] [Commented] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754387#comment-17754387 ] libopeng commented on CALCITE-5880: --- Sorry, I wasn't aware of the problem. [~julianhyde] 

[jira] [Commented] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-13 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753870#comment-17753870 ] libopeng commented on CALCITE-5880: --- [~shenlang] I agree with the second case. You can try modifying

[jira] [Updated] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-13 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5880: -- Description: {code:java} select EMPNO from emp where EXISTS (select DEPTNO from dept where

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-08-10 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753023#comment-17753023 ] libopeng commented on CALCITE-5743: --- [~shenlang]  {code:java} select EMPNO from emp where EMPNO in

[jira] [Updated] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-10 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5880: -- Description: {code:java} select EMPNO from emp where EXISTS (select DEPTNO from dept where

[jira] [Commented] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-10 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753014#comment-17753014 ] libopeng commented on CALCITE-5880: --- I think the problem is caused by decorrelation > When the

[jira] [Commented] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-10 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753013#comment-17753013 ] libopeng commented on CALCITE-5880: --- [~shenlang] I doubt this fault caused by this filter condition.

[jira] [Assigned] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-08-07 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng reassigned CALCITE-5568: - Assignee: (was: libopeng) > Decorrelate will fail. If the RelNode tree has LogicalValues

[jira] [Comment Edited] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-07 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751479#comment-17751479 ] libopeng edited comment on CALCITE-5880 at 8/7/23 11:39 AM: [~asolimando]

[jira] [Comment Edited] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-07 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751479#comment-17751479 ] libopeng edited comment on CALCITE-5880 at 8/7/23 6:42 AM: --- [~asolimando]

[jira] [Commented] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-07 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751479#comment-17751479 ] libopeng commented on CALCITE-5880: --- [~asolimando] Take a look at this

[jira] [Commented] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-01 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750066#comment-17750066 ] libopeng commented on CALCITE-5880: --- !image-2023-08-02-10-15-00-455.png! [~shenlang] Calcite main

[jira] [Updated] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-01 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5880: -- Attachment: image-2023-08-02-10-15-00-455.png > When the association condition of the association

[jira] [Commented] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-08-01 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749581#comment-17749581 ] libopeng commented on CALCITE-5880: --- [~shenlang] The data type description you are right, all

[jira] [Updated] (CALCITE-5583) JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column names

2023-08-01 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5583: -- Description: JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column

[jira] [Updated] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-07-28 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5880: -- Description: {code:java} select EMPNO from emp where EXISTS (select DEPTNO from dept where

[jira] [Created] (CALCITE-5880) When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation.

2023-07-28 Thread libopeng (Jira)
libopeng created CALCITE-5880: - Summary: When the association condition of the association subquery is 'is not distinct from', the join condition becomes '=' after decorrelation. Key: CALCITE-5880 URL:

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-06-13 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731913#comment-17731913 ] libopeng commented on CALCITE-5743: --- [~shenlang] Thank you for providing the information, but it

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-06-08 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17730450#comment-17730450 ] libopeng commented on CALCITE-5743: --- OK! If the input of an aggregate produces correlated variables,

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-06-06 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729929#comment-17729929 ] libopeng commented on CALCITE-5743: ---

[jira] [Commented] (CALCITE-5743) Query gives incorrect result when COUNT appears in the correlated subquery select list

2023-06-06 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729919#comment-17729919 ] libopeng commented on CALCITE-5743: --- Rather than adding a join, could the existing join change from

[jira] [Commented] (CALCITE-5743) An error occurs when count appears in the correlated subquery select list

2023-06-06 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729691#comment-17729691 ] libopeng commented on CALCITE-5743: ---   {code:java} LogicalProject(A=[$0])  

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-06-05 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729350#comment-17729350 ] libopeng commented on CALCITE-5568: --- I don't know how to ignore this test case, so I removed it for

[jira] [Assigned] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-06-05 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng reassigned CALCITE-5568: - Assignee: libopeng > Decorrelate will fail. If the RelNode tree has LogicalValues >

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-06-02 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17728666#comment-17728666 ] libopeng commented on CALCITE-5568: --- I raised a new issue to record the problem

[jira] [Created] (CALCITE-5743) An error occurs when count appears in the correlated subquery select list

2023-06-02 Thread libopeng (Jira)
libopeng created CALCITE-5743: - Summary: An error occurs when count appears in the correlated subquery select list Key: CALCITE-5743 URL: https://issues.apache.org/jira/browse/CALCITE-5743 Project:

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-06-02 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17728636#comment-17728636 ] libopeng commented on CALCITE-5568: --- {code:java} SELECT `t0`.`_c0` FROM ( SELECT `t`.`_c0`, `t`.`_c1`

[jira] [Comment Edited] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-05-30 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727482#comment-17727482 ] libopeng edited comment on CALCITE-5568 at 5/30/23 11:11 AM: - {code:java}

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-05-30 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727482#comment-17727482 ] libopeng commented on CALCITE-5568: --- {code:java} with parts (PNum, OrderOnHand) as (select * from

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-05-29 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727115#comment-17727115 ] libopeng commented on CALCITE-5568: --- [~libenchao] [~julianhyde] Please help me review this

[jira] [Updated] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-05-29 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5568: -- Description: Decorrelate will fail. If the RelNode tree has LogicalValues case: {code:java} SELECT

[jira] [Updated] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-22 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5568: -- Description: Decorrelate will fail. If the RelNode tree has LogicalValues case: {code:java} SELECT

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-22 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703840#comment-17703840 ] libopeng commented on CALCITE-5568: --- Well,it reproduces the problem. Let me change the description.

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-22 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703569#comment-17703569 ] libopeng commented on CALCITE-5568: --- {code:java} select ( SELECT 1 ) AS c1 from EMP t1 where EXISTS

[jira] [Updated] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-21 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5568: -- Description: Decorrelate will fail. If the RelNode tree has LogicalValues case: {code:java} SELECT

[jira] [Updated] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-21 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5568: -- Description: Decorrelate will fail. If the RelNode tree has LogicalValues case: {code:java} SELECT

[jira] [Comment Edited] (CALCITE-5583) JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column names

2023-03-19 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17702086#comment-17702086 ] libopeng edited comment on CALCITE-5583 at 3/20/23 2:03 AM: "star" may be a

[jira] [Updated] (CALCITE-5583) JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column names

2023-03-18 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5583: -- Description: JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column

[jira] [Updated] (CALCITE-5583) JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column names

2023-03-18 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5583: -- Summary: JDBC adapter generates 'SELECT *', which is invalid SQL if there are duplicate column names

[jira] [Commented] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-18 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17702086#comment-17702086 ] libopeng commented on CALCITE-5583: --- "star" may be a property of the project that is passed from

[jira] [Comment Edited] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701705#comment-17701705 ] libopeng edited comment on CALCITE-5583 at 3/17/23 12:50 PM: -  I was wrong.

[jira] [Commented] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701705#comment-17701705 ] libopeng commented on CALCITE-5583: --- --- I was wrong. Cause is 'duplicate field names'. I agree with

[jira] [Commented] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-17 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701696#comment-17701696 ] libopeng commented on CALCITE-5583: --- Seeing so many errors, I was lost in thought :(. Sometimes

[jira] [Commented] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701523#comment-17701523 ] libopeng commented on CALCITE-5583: --- emmm... Maybe I got you drill into the details again. > Rel2Sql

[jira] [Comment Edited] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701521#comment-17701521 ] libopeng edited comment on CALCITE-5583 at 3/17/23 5:44 AM: Ok, so back to

[jira] [Commented] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-16 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701521#comment-17701521 ] libopeng commented on CALCITE-5583: --- Ok, so back to the original question, I don't know why we have

[jira] [Comment Edited] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700485#comment-17700485 ] libopeng edited comment on CALCITE-5583 at 3/15/23 3:55 AM: I changed the

[jira] [Comment Edited] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700485#comment-17700485 ] libopeng edited comment on CALCITE-5583 at 3/15/23 3:53 AM: I changed the

[jira] [Commented] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700485#comment-17700485 ] libopeng commented on CALCITE-5583: --- I changed the RelNode on it {code:java} LogicalProject(c0=[$0],

[jira] [Updated] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5583: -- Description: Rel2Sql will get an error when select * and join is present {code:java}

[jira] [Updated] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5583: -- Description: Rel2Sql will get an error when select * and join is present {code:java}

[jira] [Comment Edited] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700477#comment-17700477 ] libopeng edited comment on CALCITE-5583 at 3/15/23 3:08 AM: [~julianhyde] I

[jira] [Comment Edited] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700477#comment-17700477 ] libopeng edited comment on CALCITE-5583 at 3/15/23 3:07 AM: [~julianhyde] I

[jira] [Commented] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700477#comment-17700477 ] libopeng commented on CALCITE-5583: --- [~julianhyde] I wrote a unit test that you can take a look at,

[jira] [Updated] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5583: -- Description: Rel2Sql will get an error when select * and join is present {code:java}

[jira] [Updated] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5583: -- Description: Rel2Sql will get an error when select * and join is present {code:java}

[jira] [Created] (CALCITE-5583) Rel2Sql will get an error when select * and join is present

2023-03-14 Thread libopeng (Jira)
libopeng created CALCITE-5583: - Summary: Rel2Sql will get an error when select * and join is present Key: CALCITE-5583 URL: https://issues.apache.org/jira/browse/CALCITE-5583 Project: Calcite

[jira] [Comment Edited] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-14 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699940#comment-17699940 ] libopeng edited comment on CALCITE-5568 at 3/14/23 11:57 AM: - I submitted a

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-13 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699940#comment-17699940 ] libopeng commented on CALCITE-5568: --- I submitted a [PR|https://github.com/apache/calcite/pull/3110],

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-12 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699424#comment-17699424 ] libopeng commented on CALCITE-5568: --- [~libenchao] I've seen this solution on other

[jira] [Commented] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-10 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699156#comment-17699156 ] libopeng commented on CALCITE-5568: --- [~julianhyde] Thank you for reminding me, I changed the summary

[jira] [Updated] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-10 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5568: -- Description: Decorrelate will fail. If the RelNode tree has LogicalValues case: {code:java} SELECT

[jira] [Updated] (CALCITE-5568) Decorrelate will fail. If the RelNode tree has LogicalValues

2023-03-10 Thread libopeng (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] libopeng updated CALCITE-5568: -- Description: Decorrelate will fail. If the RelNode tree has LogicalValues   {code:java} SELECT (

  1   2   >