[jira] [Commented] (CALCITE-6747) Multiple SLF4J bindings in Spark unit test

[ https://issues.apache.org/jira/browse/CALCITE-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908387#comment-17908387 ] xiong duan commented on CALCITE-6747: - If you can add some description after applyi

[jira] [Commented] (CALCITE-6649) Enhance RelMdPredicates pull up predicate from PROJECT

[ https://issues.apache.org/jira/browse/CALCITE-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908233#comment-17908233 ] xiong duan commented on CALCITE-6649: - This issue has been fixed in CALCITE-6586. T

[jira] [Resolved] (CALCITE-6649) Enhance RelMdPredicates pull up predicate from PROJECT

[ https://issues.apache.org/jira/browse/CALCITE-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6649. - Fix Version/s: 1.39.0 Resolution: Fixed > Enhance RelMdPredicates pull up predicate from

[jira] [Commented] (CALCITE-6740) Case statements may generate too many same code

[ https://issues.apache.org/jira/browse/CALCITE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908060#comment-17908060 ] xiong duan commented on CALCITE-6740: - Nice catch. +1 > Case statements may genera

[jira] [Commented] (CALCITE-6467) Performance of RelMdUtil.checkInputForCollationAndLimit when using `where col in (large literal set)`

[ https://issues.apache.org/jira/browse/CALCITE-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908056#comment-17908056 ] xiong duan commented on CALCITE-6467: - [~gortiz] Hi, I have reverted changes in CAC

[jira] [Commented] (CALCITE-5036) `RelMetadataQuery#getPulledUpPredicates` support to analyze constant key for the operator of IS_NOT_DISTINCT_FROM

[ https://issues.apache.org/jira/browse/CALCITE-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908055#comment-17908055 ] xiong duan commented on CALCITE-5036: - Revert changes in [d9363a9|https://github.c

[jira] [Resolved] (CALCITE-4860) In Elasticsearch adapter, support NULLS FIRST and NULLS LAST query

[ https://issues.apache.org/jira/browse/CALCITE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-4860. - Fix Version/s: 1.39.0 Resolution: Fixed > In Elasticsearch adapter, support NULLS FIRST

[jira] [Commented] (CALCITE-4860) In Elasticsearch adapter, support NULLS FIRST and NULLS LAST query

[ https://issues.apache.org/jira/browse/CALCITE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908017#comment-17908017 ] xiong duan commented on CALCITE-4860: - Fixed in [a88b1e8|https://github.com/apache

[jira] [Commented] (CALCITE-5036) `RelMetadataQuery#getPulledUpPredicates` support to analyze constant key for the operator of IS_NOT_DISTINCT_FROM

[ https://issues.apache.org/jira/browse/CALCITE-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907376#comment-17907376 ] xiong duan commented on CALCITE-5036: - [~julianhyde] I have prepared a PR for this

[jira] [Assigned] (CALCITE-6649) Enhance RelMdPredicates pull up predicate from PROJECT

[ https://issues.apache.org/jira/browse/CALCITE-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan reassigned CALCITE-6649: --- Assignee: xiong duan > Enhance RelMdPredicates pull up predicate from PROJECT > --

[jira] [Commented] (CALCITE-6741) The type of a comparison is nullable when either operand is nullable

[ https://issues.apache.org/jira/browse/CALCITE-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907251#comment-17907251 ] xiong duan commented on CALCITE-6741: - When we convert IN to OR condition, it is de

[jira] [Comment Edited] (CALCITE-6741) Incorrect type inference in AbstractTypeCoercion.commonTypeForBinaryComparison

[ https://issues.apache.org/jira/browse/CALCITE-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907250#comment-17907250 ] xiong duan edited comment on CALCITE-6741 at 12/20/24 1:12 AM: --

[jira] [Commented] (CALCITE-6741) Incorrect type inference in AbstractTypeCoercion.commonTypeForBinaryComparison

[ https://issues.apache.org/jira/browse/CALCITE-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907250#comment-17907250 ] xiong duan commented on CALCITE-6741: - I get it. We add the condition when unknownA

[jira] [Comment Edited] (CALCITE-6741) Incorrect type inference in AbstractTypeCoercion.commonTypeForBinaryComparison

[ https://issues.apache.org/jira/browse/CALCITE-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907248#comment-17907248 ] xiong duan edited comment on CALCITE-6741 at 12/20/24 1:01 AM: --

[jira] [Commented] (CALCITE-6741) Incorrect type inference in AbstractTypeCoercion.commonTypeForBinaryComparison

[ https://issues.apache.org/jira/browse/CALCITE-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907248#comment-17907248 ] xiong duan commented on CALCITE-6741: - If we think it is right, then the expression

[jira] [Assigned] (CALCITE-6665) Add isEmpty metadata to check if a relational expression returns no rows

[ https://issues.apache.org/jira/browse/CALCITE-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan reassigned CALCITE-6665: --- Assignee: xiong duan > Add isEmpty metadata to check if a relational expression returns no

[jira] [Commented] (CALCITE-6730) Add CONVERT function(enabled in Oracle library)

[ https://issues.apache.org/jira/browse/CALCITE-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906575#comment-17906575 ] xiong duan commented on CALCITE-6730: - If we use non-Oracle syntax in Calcite, we c

[jira] [Commented] (CALCITE-6725) The caching mechanism key in ElasticsearchSchemaFactory is affected by the order of hosts

[ https://issues.apache.org/jira/browse/CALCITE-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906404#comment-17906404 ] xiong duan commented on CALCITE-6725: - Fixed in [dbf4ff8|https://github.com/apache

[jira] [Resolved] (CALCITE-6725) The caching mechanism key in ElasticsearchSchemaFactory is affected by the order of hosts

[ https://issues.apache.org/jira/browse/CALCITE-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6725. - Fix Version/s: 1.39.0 Resolution: Fixed > The caching mechanism key in ElasticsearchSche

[jira] [Commented] (CALCITE-6665) Add isEmpty metadata to check if a relational expression returns no rows

[ https://issues.apache.org/jira/browse/CALCITE-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906229#comment-17906229 ] xiong duan commented on CALCITE-6665: - If this method returns NULL, it means we don

[jira] [Commented] (CALCITE-4860) In Elasticsearch adapter, support NULLS FIRST and NULLS LAST query

[ https://issues.apache.org/jira/browse/CALCITE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905857#comment-17905857 ] xiong duan commented on CALCITE-4860: - If this PR can throw unsupport exceptions wh

[jira] [Commented] (CALCITE-6690) Refactor the Arrow adapter type system

[ https://issues.apache.org/jira/browse/CALCITE-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905854#comment-17905854 ] xiong duan commented on CALCITE-6690: - Does this PR support `Arrow adapter support

[jira] [Resolved] (CALCITE-6566) JDBC adapter should generate PI function with parentheses in most dialects

[ https://issues.apache.org/jira/browse/CALCITE-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6566. - Resolution: Fixed > JDBC adapter should generate PI function with parentheses in most dialects

[jira] [Commented] (CALCITE-6566) JDBC adapter should generate PI function with parentheses in most dialects

[ https://issues.apache.org/jira/browse/CALCITE-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904712#comment-17904712 ] xiong duan commented on CALCITE-6566: - Fixed in [cd0b8da|https://github.com/apache

[jira] [Closed] (CALCITE-6719) CODE_POINTS_TO_STRING、CODE_POINTS_TO_BYTES and TO_CODE_POINTS's return type should be nullable when return the NULL value

[ https://issues.apache.org/jira/browse/CALCITE-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan closed CALCITE-6719. --- Resolution: Duplicate Duplicate with CALCITE-6711. > CODE_POINTS_TO_STRING、CODE_POINTS_TO_BYTES an

[jira] [Commented] (CALCITE-6711) Functions whose output value can be null should return a nullable type

[ https://issues.apache.org/jira/browse/CALCITE-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903989#comment-17903989 ] xiong duan commented on CALCITE-6711: - Fixed in [e2e7ce1|https://github.com/apache

[jira] [Assigned] (CALCITE-6711) Functions whose output value can be null should return a nullable type

[ https://issues.apache.org/jira/browse/CALCITE-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan reassigned CALCITE-6711: --- Assignee: xiong duan > Functions whose output value can be null should return a nullable t

[jira] [Resolved] (CALCITE-6711) Functions whose output value can be null should return a nullable type

[ https://issues.apache.org/jira/browse/CALCITE-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6711. - Resolution: Fixed > Functions whose output value can be null should return a nullable type > --

[jira] [Commented] (CALCITE-4758) When SOME sub-query is SqlNodeList and converted to VALUES, Calcite returns incorrect result

[ https://issues.apache.org/jira/browse/CALCITE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903630#comment-17903630 ] xiong duan commented on CALCITE-4758: - Fixed in [84ea4be|https://github.com/apache

[jira] [Resolved] (CALCITE-4758) When SOME sub-query is SqlNodeList and converted to VALUES, Calcite returns incorrect result

[ https://issues.apache.org/jira/browse/CALCITE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-4758. - Fix Version/s: 1.39.0 Resolution: Fixed > When SOME sub-query is SqlNodeList and convert

[jira] [Created] (CALCITE-6719) CODE_POINTS_TO_STRING、CODE_POINTS_TO_BYTES and TO_CODE_POINTS's return type should be nullable when return the NULL value

xiong duan created CALCITE-6719: --- Summary: CODE_POINTS_TO_STRING、CODE_POINTS_TO_BYTES and TO_CODE_POINTS's return type should be nullable when return the NULL value Key: CALCITE-6719 URL: https://issues.apache.org/j

[jira] [Commented] (CALCITE-6688) Allow operators of SqlKind.SYMMETRICAL to be reversed

[ https://issues.apache.org/jira/browse/CALCITE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903161#comment-17903161 ] xiong duan commented on CALCITE-6688: - Fixed in [0eb83b1|https://github.com/apache

[jira] [Resolved] (CALCITE-6688) Allow operators of SqlKind.SYMMETRICAL to be reversed

[ https://issues.apache.org/jira/browse/CALCITE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6688. - Fix Version/s: 1.39.0 Resolution: Fixed > Allow operators of SqlKind.SYMMETRICAL to be r

[jira] [Updated] (CALCITE-6688) Allow operators of SqlKind.SYMMETRICAL to be reversed

[ https://issues.apache.org/jira/browse/CALCITE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-6688: Summary: Allow operators of SqlKind.SYMMETRICAL to be reversed (was: Allow operators of SqlKind.

[jira] [Commented] (CALCITE-6713) NVL2's return data type should be nullable if and only if at least one of the second and third parameters are nullable

[ https://issues.apache.org/jira/browse/CALCITE-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902905#comment-17902905 ] xiong duan commented on CALCITE-6713: - Fixed in [0a96bee|https://github.com/apache

[jira] [Resolved] (CALCITE-6713) NVL2's return data type should be nullable if and only if at least one of the second and third parameters are nullable

[ https://issues.apache.org/jira/browse/CALCITE-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6713. - Fix Version/s: 1.39.0 Resolution: Fixed > NVL2's return data type should be nullable if

[jira] [Commented] (CALCITE-6711) Functions whose output value can be null should return a nullable type

[ https://issues.apache.org/jira/browse/CALCITE-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902472#comment-17902472 ] xiong duan commented on CALCITE-6711: - After fix these function, I will remove `{{

[jira] [Comment Edited] (CALCITE-6712) FROM_BASE64 and PARSE_URL's return data type should always be nullable

[ https://issues.apache.org/jira/browse/CALCITE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902140#comment-17902140 ] xiong duan edited comment on CALCITE-6712 at 12/1/24 10:46 PM: --

[jira] [Commented] (CALCITE-6712) FROM_BASE64 and PARSE_URL's return data type should always be nullable

[ https://issues.apache.org/jira/browse/CALCITE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902140#comment-17902140 ] xiong duan commented on CALCITE-6712: - Before this PR. from_base64('-1'); return NU

[jira] [Commented] (CALCITE-6712) FROM_BASE64 and PARSE_URL's return data type should always be nullable

[ https://issues.apache.org/jira/browse/CALCITE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902139#comment-17902139 ] xiong duan commented on CALCITE-6712: - This PR addresses the issue that a function'

[jira] [Resolved] (CALCITE-6712) FROM_BASE64 and PARSE_URL's return data type should always be nullable

[ https://issues.apache.org/jira/browse/CALCITE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6712. - Fix Version/s: 1.39.0 Resolution: Fixed > FROM_BASE64 and PARSE_URL's return data type s

[jira] [Commented] (CALCITE-6712) FROM_BASE64 and PARSE_URL's return data type should always be nullable

[ https://issues.apache.org/jira/browse/CALCITE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902075#comment-17902075 ] xiong duan commented on CALCITE-6712: - [~julianhyde] I added the test method in CAL

[jira] [Commented] (CALCITE-6712) FROM_BASE64 and PARSE_URL's return data type should always be nullable

[ https://issues.apache.org/jira/browse/CALCITE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902074#comment-17902074 ] xiong duan commented on CALCITE-6712: - Fixed in [c9724b6|https://github.com/apache

[jira] [Created] (CALCITE-6713) NVL2's return data type should be nullable if and only if at least one of the second and third parameters are nullable

xiong duan created CALCITE-6713: --- Summary: NVL2's return data type should be nullable if and only if at least one of the second and third parameters are nullable Key: CALCITE-6713 URL: https://issues.apache.org/jira

[jira] [Created] (CALCITE-6712) FROM_BASE64 and PARSE_URL's return data type should always be nullable

xiong duan created CALCITE-6712: --- Summary: FROM_BASE64 and PARSE_URL's return data type should always be nullable Key: CALCITE-6712 URL: https://issues.apache.org/jira/browse/CALCITE-6712 Project: Calci

[jira] [Updated] (CALCITE-6712) FROM_BASE64 and PARSE_URL's return data type should always be nullable

[ https://issues.apache.org/jira/browse/CALCITE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-6712: Description: The return values of these two functions are related to the specific parameter valu

[jira] [Commented] (CALCITE-6711) Functions whose output value can be null should return a nullable type

[ https://issues.apache.org/jira/browse/CALCITE-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901906#comment-17901906 ] xiong duan commented on CALCITE-6711: - The incorrect data types of functions are ca

[jira] [Created] (CALCITE-6711) Functions whose output value can be null should return a nullable type

xiong duan created CALCITE-6711: --- Summary: Functions whose output value can be null should return a nullable type Key: CALCITE-6711 URL: https://issues.apache.org/jira/browse/CALCITE-6711 Project: Calci

[jira] [Commented] (CALCITE-6707) Type inference for CHR function is wrong

[ https://issues.apache.org/jira/browse/CALCITE-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901824#comment-17901824 ] xiong duan commented on CALCITE-6707: - I think I misunderstood this ISSUE. The retu

[jira] [Commented] (CALCITE-6707) Type inference for CHR function is wrong

[ https://issues.apache.org/jira/browse/CALCITE-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901626#comment-17901626 ] xiong duan commented on CALCITE-6707: - [~mbudiu]  If we check the NULL type when t

[jira] [Commented] (CALCITE-6706) Explicit cast to numeric type doesn't check overflow

[ https://issues.apache.org/jira/browse/CALCITE-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901181#comment-17901181 ] xiong duan commented on CALCITE-6706: - The following three SQL statements will all

[jira] [Commented] (CALCITE-4758) When SOME sub-query is SqlNodeList and converted to VALUES, Calcite returns incorrect result

[ https://issues.apache.org/jira/browse/CALCITE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901178#comment-17901178 ] xiong duan commented on CALCITE-4758: - [~mbudiu] I updated the description and comm

[jira] [Commented] (CALCITE-4758) When SOME sub-query is SqlNodeList and converted to VALUES, Calcite returns incorrect result

[ https://issues.apache.org/jira/browse/CALCITE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901177#comment-17901177 ] xiong duan commented on CALCITE-4758: - Because when we use VALUES expression and th

[jira] [Updated] (CALCITE-4758) When SOME sub-query is SqlNodeList and converted to VALUES, Calcite returns incorrect result

[ https://issues.apache.org/jira/browse/CALCITE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-4758: Description: As discussed in the comments: The SQL {code:java} select * from "scott".emp where sa

[jira] [Updated] (CALCITE-4758) When SOME sub-query is SqlNodeList and converted to VALUES, Calcite returns incorrect result

[ https://issues.apache.org/jira/browse/CALCITE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-4758: Summary: When SOME sub-query is SqlNodeList and converted to VALUES, Calcite returns incorrect re

[jira] [Comment Edited] (CALCITE-6566) JDBC adapter should generate PI function with parentheses in most dialects

[ https://issues.apache.org/jira/browse/CALCITE-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901164#comment-17901164 ] xiong duan edited comment on CALCITE-6566 at 11/26/24 10:56 AM: -

[jira] [Commented] (CALCITE-6566) JDBC adapter should generate PI function with parentheses in most dialects

[ https://issues.apache.org/jira/browse/CALCITE-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901164#comment-17901164 ] xiong duan commented on CALCITE-6566: - The PR has been updated. 1) Add allowNiladi

[jira] [Resolved] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

[ https://issues.apache.org/jira/browse/CALCITE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6650. - Fix Version/s: 1.39.0 Resolution: Fixed > Optimize the IN sub-query and SOME sub-query b

[jira] [Commented] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

[ https://issues.apache.org/jira/browse/CALCITE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897058#comment-17897058 ] xiong duan commented on CALCITE-6650: - Fixed in [f347fba|https://github.com/apache

[jira] [Assigned] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

[ https://issues.apache.org/jira/browse/CALCITE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan reassigned CALCITE-6650: --- Assignee: xiong duan > Optimize the IN sub-query and SOME sub-query by Metadata RowCount >

[jira] [Commented] (CALCITE-6649) Enhance RelMdPredicates pull up predicate from PROJECT

[ https://issues.apache.org/jira/browse/CALCITE-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896130#comment-17896130 ] xiong duan commented on CALCITE-6649: - As you said, this may be a very expensive ch

[jira] [Commented] (CALCITE-6651) Use RelBuilder in SqlToRelConverter to construct Union

[ https://issues.apache.org/jira/browse/CALCITE-6651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896127#comment-17896127 ] xiong duan commented on CALCITE-6651: - What's the difference between the result and

[jira] [Commented] (CALCITE-6651) Use RelBuilder in SqlToRelConverter to construct Union

[ https://issues.apache.org/jira/browse/CALCITE-6651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896128#comment-17896128 ] xiong duan commented on CALCITE-6651: - The description is not very clear, maybe nee

[jira] [Commented] (CALCITE-6663) Support SPLIT_PART function for Postgres

[ https://issues.apache.org/jira/browse/CALCITE-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895257#comment-17895257 ] xiong duan commented on CALCITE-6663: - [~mbudiu] We need to keep the Jira summary c

[jira] [Commented] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

[ https://issues.apache.org/jira/browse/CALCITE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895069#comment-17895069 ] xiong duan commented on CALCITE-6650: - The PR has been updated. 1) Replace the `ha

[jira] [Created] (CALCITE-6665) Add isEmpty metadata to check if a relational expression returns no rows

xiong duan created CALCITE-6665: --- Summary: Add isEmpty metadata to check if a relational expression returns no rows Key: CALCITE-6665 URL: https://issues.apache.org/jira/browse/CALCITE-6665 Project: Cal

[jira] [Commented] (CALCITE-6663) Support SPLIT_PART function for postgresql

[ https://issues.apache.org/jira/browse/CALCITE-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17894831#comment-17894831 ] xiong duan commented on CALCITE-6663: - The official function description about spli

[jira] [Comment Edited] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

[ https://issues.apache.org/jira/browse/CALCITE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17894190#comment-17894190 ] xiong duan edited comment on CALCITE-6650 at 10/30/24 12:37 PM: -

[jira] [Commented] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

[ https://issues.apache.org/jira/browse/CALCITE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17894190#comment-17894190 ] xiong duan commented on CALCITE-6650: - Hi [~julianhyde] . The NULL value works as e

[jira] [Commented] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

[ https://issues.apache.org/jira/browse/CALCITE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17894188#comment-17894188 ] xiong duan commented on CALCITE-6650: - Hi [~zabetak] . The PruneEmptyRules can't al

[jira] [Updated] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

[ https://issues.apache.org/jira/browse/CALCITE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-6650: Description: As same as the UNIQUE sub-query, before we convert the sub-query to RelNode. we use

[jira] [Created] (CALCITE-6650) Optimize the IN sub-query and SOME sub-query by Metadata RowCount

xiong duan created CALCITE-6650: --- Summary: Optimize the IN sub-query and SOME sub-query by Metadata RowCount Key: CALCITE-6650 URL: https://issues.apache.org/jira/browse/CALCITE-6650 Project: Calcite

[jira] [Commented] (CALCITE-6645) Support user-defined function without parentheses when db dialect's allowNiladicParentheses property is false

[ https://issues.apache.org/jira/browse/CALCITE-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893666#comment-17893666 ] xiong duan commented on CALCITE-6645: - Ok. I will check this. Thanks for the reply.

[jira] [Commented] (CALCITE-6645) Support user-defined function without parentheses when db dialect's allowNiladicParentheses property is false

[ https://issues.apache.org/jira/browse/CALCITE-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893659#comment-17893659 ] xiong duan commented on CALCITE-6645: - Why do we need to pass CalciteConnectionConf

[jira] [Comment Edited] (CALCITE-6645) Support user-defined function without parentheses when db dialect's allowNiladicParentheses property is false

[ https://issues.apache.org/jira/browse/CALCITE-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893655#comment-17893655 ] xiong duan edited comment on CALCITE-6645 at 10/29/24 12:53 AM: -

[jira] [Commented] (CALCITE-6645) Support user-defined function without parentheses when db dialect's allowNiladicParentheses property is false

[ https://issues.apache.org/jira/browse/CALCITE-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893655#comment-17893655 ] xiong duan commented on CALCITE-6645: - I noticed you use `allowNiladicParentheses`

[jira] [Created] (CALCITE-6649) Enhance RelMdPredicates pull up predicate from PROJECT

xiong duan created CALCITE-6649: --- Summary: Enhance RelMdPredicates pull up predicate from PROJECT Key: CALCITE-6649 URL: https://issues.apache.org/jira/browse/CALCITE-6649 Project: Calcite Issu

[jira] [Commented] (CALCITE-6592) Add test for RelMdPredicates pull up predicate from UNION when it's input predicates include NULL VALUE

[ https://issues.apache.org/jira/browse/CALCITE-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892350#comment-17892350 ] xiong duan commented on CALCITE-6592: - Fixed in [fb7eddea|https://github.com/apach

[jira] [Resolved] (CALCITE-6592) Add test for RelMdPredicates pull up predicate from UNION when it's input predicates include NULL VALUE

[ https://issues.apache.org/jira/browse/CALCITE-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6592. - Fix Version/s: 1.39.0 Assignee: xiong duan Resolution: Fixed > Add test for Rel

[jira] [Commented] (CALCITE-6592) Add test for RelMdPredicates pull up predicate from UNION when it's input predicates include NULL VALUE

[ https://issues.apache.org/jira/browse/CALCITE-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892327#comment-17892327 ] xiong duan commented on CALCITE-6592: - After fixing the CALCITE-6599(RelMdPredicate

[jira] [Updated] (CALCITE-6592) Add test for RelMdPredicates pull up predicate from UNION when it's input predicates include NULL VALUE

[ https://issues.apache.org/jira/browse/CALCITE-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-6592: Summary: Add test for RelMdPredicates pull up predicate from UNION when it's input predicates inc

[jira] [Commented] (CALCITE-5156) Support implicit integer type cast for IN Sub-query

[ https://issues.apache.org/jira/browse/CALCITE-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892113#comment-17892113 ] xiong duan commented on CALCITE-5156: - Hi [~suibianwanwan33], We have already discu

[jira] [Resolved] (CALCITE-5156) Support implicit integer type cast for IN Sub-query

[ https://issues.apache.org/jira/browse/CALCITE-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-5156. - Fix Version/s: 1.39.0 Resolution: Fixed > Support implicit integer type cast for IN Sub-

[jira] [Assigned] (CALCITE-6566) JDBC adapter should generate PI function with parentheses in most dialects

[ https://issues.apache.org/jira/browse/CALCITE-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan reassigned CALCITE-6566: --- Assignee: xiong duan > JDBC adapter should generate PI function with parentheses in most d

[jira] [Commented] (CALCITE-5156) Support implicit integer type cast for IN Sub-query

[ https://issues.apache.org/jira/browse/CALCITE-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891690#comment-17891690 ] xiong duan commented on CALCITE-5156: - Fixed in [6370479|https://github.com/apache

[jira] [Resolved] (CALCITE-6638) Optimization that simplifies expressions such as '1 > a or 1 <= a or a is null' to TRUE is incorrect when it requires casts that are not lossless

[ https://issues.apache.org/jira/browse/CALCITE-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6638. - Resolution: Fixed > Optimization that simplifies expressions such as '1 > a or 1 <= a or a is

[jira] [Commented] (CALCITE-6638) Optimization that simplifies expressions such as '1 > a or 1 <= a or a is null' to TRUE is incorrect when it requires casts that are not lossless

[ https://issues.apache.org/jira/browse/CALCITE-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891375#comment-17891375 ] xiong duan commented on CALCITE-6638: - Fixed in [ef1a83f6|https://github.com/apach

[jira] [Updated] (CALCITE-6638) Optimization that simplifies expressions such as '1 > a or 1 <= a or a is null' to TRUE is incorrect when it requires casts that are not lossless

[ https://issues.apache.org/jira/browse/CALCITE-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-6638: Summary: Optimization that simplifies expressions such as '1 > a or 1 <= a or a is null' to TRUE

[jira] [Created] (CALCITE-6638) Simplify '1 > a or 1 <= a or a is null' to TRUE when a has lossless casts

xiong duan created CALCITE-6638: --- Summary: Simplify '1 > a or 1 <= a or a is null' to TRUE when a has lossless casts Key: CALCITE-6638 URL: https://issues.apache.org/jira/browse/CALCITE-6638 Project: Ca

[jira] [Commented] (CALCITE-6633) MSSQL Dialect does not generate CEILING function

[ https://issues.apache.org/jira/browse/CALCITE-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890767#comment-17890767 ] xiong duan commented on CALCITE-6633: - 1. `The below test will fail because MSSQL s

[jira] [Closed] (CALCITE-6406) Negative scales for DECIMAL types are not tested

[ https://issues.apache.org/jira/browse/CALCITE-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan closed CALCITE-6406. --- Assignee: xiong duan Resolution: Fixed > Negative scales for DECIMAL types are not tested > -

[jira] [Updated] (CALCITE-6406) Negative scales for DECIMAL types are not tested

[ https://issues.apache.org/jira/browse/CALCITE-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-6406: Fix Version/s: 1.38.0 > Negative scales for DECIMAL types are not tested > --

[jira] [Commented] (CALCITE-6406) Negative scales for DECIMAL types are not tested

[ https://issues.apache.org/jira/browse/CALCITE-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890283#comment-17890283 ] xiong duan commented on CALCITE-6406: - This issue has fixed by CACLITE-6560. > Neg

[jira] [Updated] (CALCITE-6631) The common type for a comparison operator returns the wrong type when comparing a Java type long with a SQL type INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-6631: Description: The unit test: {code:java} RelDataType longJavaType = this.typeFactory.createJavaTyp

[jira] [Created] (CALCITE-6631) The common type for a comparison operator returns the wrong type when comparing a Java type long with a SQL type INTEGER

xiong duan created CALCITE-6631: --- Summary: The common type for a comparison operator returns the wrong type when comparing a Java type long with a SQL type INTEGER Key: CALCITE-6631 URL: https://issues.apache.org/ji

[jira] [Commented] (CALCITE-6618) Support Not Equal in Arrow adapter

[ https://issues.apache.org/jira/browse/CALCITE-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887733#comment-17887733 ] xiong duan commented on CALCITE-6618: - {code:java} Support NOT EQUALS operator in A

[jira] [Updated] (CALCITE-5156) Support implicit integer type cast for IN Sub-query

[ https://issues.apache.org/jira/browse/CALCITE-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan updated CALCITE-5156: Summary: Support implicit integer type cast for IN Sub-query (was: Support implicit number type

[jira] [Commented] (CALCITE-6599) RelMdPredicates should pull up more predicates from VALUES when there are several literals

[ https://issues.apache.org/jira/browse/CALCITE-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886703#comment-17886703 ] xiong duan commented on CALCITE-6599: - Fixed in [1af49e4|https://github.com/apache

[jira] [Resolved] (CALCITE-6599) RelMdPredicates should pull up more predicates from VALUES when there are several literals

[ https://issues.apache.org/jira/browse/CALCITE-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiong duan resolved CALCITE-6599. - Fix Version/s: 1.38.0 Assignee: xiong duan Resolution: Fixed > RelMdPredicates

[jira] [Commented] (CALCITE-6606) RelDecorrelator Can't decorrelate JOIN conditions with correlate variables

[ https://issues.apache.org/jira/browse/CALCITE-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886428#comment-17886428 ] xiong duan commented on CALCITE-6606: - Hi [~brandon.chong] .Do we have an SQL that

  1   2   3   4   5   6   >