[jira] [Commented] (CALCITE-5627) The rule of 'CoreRules.FILTER_INTO_JOIN' executed error, if some condition is sub-query

[ https://issues.apache.org/jira/browse/CALCITE-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707274#comment-17707274 ] Xurenhe commented on CALCITE-5627: -- [~libenchao]  Thanks for your quick reply. In some cases, keeping

[jira] [Created] (CALCITE-5627) The rule of 'CoreRules.FILTER_INTO_JOIN' executed error, if some condition is sub-query

Xurenhe created CALCITE-5627: Summary: The rule of 'CoreRules.FILTER_INTO_JOIN' executed error, if some condition is sub-query Key: CALCITE-5627 URL: https://issues.apache.org/jira/browse/CALCITE-5627

[jira] [Updated] (CALCITE-5465) Rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES transforms wrong plan, when sql has distinct agg-call with rollup

[ https://issues.apache.org/jira/browse/CALCITE-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5465: - Description: The rule _*AGGREGATE_EXPAND_DISTINCT_AGGREGATES*_ transform wrong plan, when the sql is

[jira] [Updated] (CALCITE-5465) Rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES transforms wrong plan, when sql has distinct agg-call with rollup

[ https://issues.apache.org/jira/browse/CALCITE-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5465: - Description: The rule _*AGGREGATE_EXPAND_DISTINCT_AGGREGATES*_ transform wrong plan, when the sql is

[jira] [Created] (CALCITE-5465) Rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES transforms wrong plan, when sql has distinct agg-call with rollup

Xurenhe created CALCITE-5465: Summary: Rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES transforms wrong plan, when sql has distinct agg-call with rollup Key: CALCITE-5465 URL:

[jira] [Updated] (CALCITE-5465) Rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES transforms wrong plan, when sql has distinct agg-call with rollup

[ https://issues.apache.org/jira/browse/CALCITE-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5465: - Description: The rule AGGREGATE_EXPAND_DISTINCT_AGGREGATES transform wrong plan, when the sql is

[jira] [Comment Edited] (CALCITE-5328) The rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES_TO_JOIN throws error when meeting the rollup's query

[ https://issues.apache.org/jira/browse/CALCITE-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17624382#comment-17624382 ] Xurenhe edited comment on CALCITE-5328 at 10/26/22 11:25 AM: - The rule of

[jira] [Commented] (CALCITE-5328) The rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES_TO_JOIN throws error when meeting the rollup's query

[ https://issues.apache.org/jira/browse/CALCITE-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17624382#comment-17624382 ] Xurenhe commented on CALCITE-5328: -- The rule of

[jira] [Commented] (CALCITE-4982) NonNull field shouldn't be pushed down into leaf of outer-join in 'ProjectJoinTransposeRule'

[ https://issues.apache.org/jira/browse/CALCITE-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17620115#comment-17620115 ] Xurenhe commented on CALCITE-4982: -- [~libenchao] Yes I agree it. Code has been updated: Should not

[jira] [Updated] (CALCITE-5328) The rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES_TO_JOIN throws error when meeting the rollup's query

[ https://issues.apache.org/jira/browse/CALCITE-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5328: - Description: The rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES_TO_JOIN aims to transform aggregate

[jira] [Created] (CALCITE-5328) The rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES_TO_JOIN throws error when meeting the rollup's query

Xurenhe created CALCITE-5328: Summary: The rule of AGGREGATE_EXPAND_DISTINCT_AGGREGATES_TO_JOIN throws error when meeting the rollup's query Key: CALCITE-5328 URL: https://issues.apache.org/jira/browse/CALCITE-5328

[jira] [Commented] (CALCITE-4982) NonNull field shouldn't be pushed down into leaf of outer-join in 'ProjectJoinTransposeRule'

[ https://issues.apache.org/jira/browse/CALCITE-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615037#comment-17615037 ] Xurenhe commented on CALCITE-4982: -- Hi [~libenchao]  As PR said, there are two solutions: # Avoid

[jira] [Commented] (CALCITE-5296) In a query with ROLLUP, validator wrongly infers that a column is NOT NULL

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614336#comment-17614336 ] Xurenhe commented on CALCITE-5296: -- [~julianhyde]  It doesn't matter.  Your suggestion is very

[jira] [Commented] (CALCITE-5296) In a query with ROLLUP, validator wrongly infers that a column is NOT NULL

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17610888#comment-17610888 ] Xurenhe commented on CALCITE-5296: -- [~libenchao]  I think second method need more changed code. By the

[jira] [Updated] (CALCITE-5296) In a query with ROLLUP, validator wrongly infers that a column is NOT NULL

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Attachment: image-2022-09-29-16-31-04-642.png > In a query with ROLLUP, validator wrongly infers that

[jira] [Commented] (CALCITE-5296) In a query with ROLLUP, validator wrongly infers that a column is NOT NULL

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17610881#comment-17610881 ] Xurenhe commented on CALCITE-5296: -- [~julianhyde] [~asolimando]  Maybe my description is not clear

[jira] [Commented] (CALCITE-5296) SqlValidator infer node's null-attribute error, which is from rollup's function and wrapped by operator

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17610446#comment-17610446 ] Xurenhe commented on CALCITE-5296: -- [~julianhyde]  Yes, it's shorter and more clear. I have changed

[jira] [Updated] (CALCITE-5296) In a query with ROLLUP, validator wrongly infers that a column is NOT NULL

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Summary: In a query with ROLLUP, validator wrongly infers that a column is NOT NULL (was:

[jira] [Updated] (CALCITE-5296) SqlValidator infer node's null-attribute error, which is from rollup's function and wrapped by operator

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Summary: SqlValidator infer node's null-attribute error, which is from rollup's function and wrapped

[jira] [Commented] (CALCITE-5296) Infer rowtype error, when meeting function with group-set's item in the SELECT statement

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609992#comment-17609992 ] Xurenhe commented on CALCITE-5296: -- [~julianhyde] Thank you for reminding me. I change this tittle to

[jira] [Updated] (CALCITE-5296) Infer rowtype error, when meeting function with group-set's item in the SELECT statement

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Summary: Infer rowtype error, when meeting function with group-set's item in the SELECT statement

[jira] [Updated] (CALCITE-5296) Infer rowtype error, when meeting function with group-set's item

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Summary: Infer rowtype error, when meeting function with group-set's item (was: SELECT function

[jira] [Commented] (CALCITE-5296) Infer rowtype error, when meeting function with group-set's item

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609436#comment-17609436 ] Xurenhe commented on CALCITE-5296: -- [~libenchao]  Yes, rowtype are different between validating stage

[jira] [Commented] (CALCITE-5296) SELECT function within grouping-set's item throws exception, during converting sql to relnode

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608491#comment-17608491 ] Xurenhe commented on CALCITE-5296: -- Not only for CASE statement, the following example has the same

[jira] [Updated] (CALCITE-5296) SELECT function within grouping-set's item throws exception, during converting sql to relnode

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Description: CALCITE throws exception during the stage of sql_to_rel,  when executing *SELECT*

[jira] [Updated] (CALCITE-5296) SELECT function within grouping-set's item throws exception, during converting sql to relnode

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Summary: SELECT function within grouping-set's item throws exception, during converting sql to relnode

[jira] [Updated] (CALCITE-5296) CASE statement within grouping-sets's item throws exception during sql_to_rel

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Description: CALCITE throws exception during the stage of sql_to_rel, when executing *CASE* statement 

[jira] [Updated] (CALCITE-5296) CASE statement within grouping-sets's item throws exception during sql_to_rel

[ https://issues.apache.org/jira/browse/CALCITE-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5296: - Description: CALCITE throws exception during the stage of sql_to_rel, when executing *CASE* statement 

[jira] [Created] (CALCITE-5296) CASE statement within grouping-sets's item throws exception during sql_to_rel

Xurenhe created CALCITE-5296: Summary: CASE statement within grouping-sets's item throws exception during sql_to_rel Key: CALCITE-5296 URL: https://issues.apache.org/jira/browse/CALCITE-5296 Project:

[jira] (CALCITE-5163) MysqlSqlDialect unparse LISTAGG aggregate function error

[ https://issues.apache.org/jira/browse/CALCITE-5163 ] Xurenhe deleted comment on CALCITE-5163: -- was (Author: wojustme): Hi guys, PR has been ready, welcome to review it. https://github.com/apache/calcite/pull/2812 > MysqlSqlDialect unparse

[jira] [Commented] (CALCITE-5163) MysqlSqlDialect unparse LISTAGG aggregate function error

[ https://issues.apache.org/jira/browse/CALCITE-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539994#comment-17539994 ] Xurenhe commented on CALCITE-5163: -- Hi guys, PR has been ready, welcome to review it.

[jira] [Created] (CALCITE-5163) MysqlSqlDialect unparse LISTAGG aggregate function error

Xurenhe created CALCITE-5163: Summary: MysqlSqlDialect unparse LISTAGG aggregate function error Key: CALCITE-5163 URL: https://issues.apache.org/jira/browse/CALCITE-5163 Project: Calcite Issue

[jira] [Commented] (CALCITE-3890) Derive IS NOT NULL filter for the inputs of inner join

[ https://issues.apache.org/jira/browse/CALCITE-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534644#comment-17534644 ] Xurenhe commented on CALCITE-3890: -- I left some doubts in the pr. I am curious about how to analyze

[jira] [Commented] (CALCITE-5109) RelMdAllPredicates support to analyze left-out-join

[ https://issues.apache.org/jira/browse/CALCITE-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529450#comment-17529450 ] Xurenhe commented on CALCITE-5109: -- Hi [~Ziwei Liu] Thanks for your comment. I define some sub-classes

[jira] [Commented] (CALCITE-5109) RelMdAllPredicates support to analyze left-out-join

[ https://issues.apache.org/jira/browse/CALCITE-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529439#comment-17529439 ] Xurenhe commented on CALCITE-5109: -- Hi [~Chunwei Lei]  I made a

[jira] [Commented] (CALCITE-5109) RelMdAllPredicates support to analyze left-out-join

[ https://issues.apache.org/jira/browse/CALCITE-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529164#comment-17529164 ] Xurenhe commented on CALCITE-5109: -- [~Chunwei Lei]  Thanks for your review and advice. I'm not sure

[jira] [Commented] (CALCITE-5109) RelMdAllPredicates support to analyze left-out-join

[ https://issues.apache.org/jira/browse/CALCITE-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528800#comment-17528800 ] Xurenhe commented on CALCITE-5109: -- Hi all Please review the commit:

[jira] [Commented] (CALCITE-5109) RelMdAllPredicates support to analyze left-out-join

[ https://issues.apache.org/jira/browse/CALCITE-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527509#comment-17527509 ] Xurenhe commented on CALCITE-5109: -- [~Chunwei Lei] Thanks for your encourage. Yes, this feature is

[jira] [Updated] (CALCITE-5109) RelMdAllPredicates support to analyze left-out-join

[ https://issues.apache.org/jira/browse/CALCITE-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5109: - Description:   {code:java} select * from left_sub_query {left_where_condition} join {join_type}

[jira] [Created] (CALCITE-5109) RelMdAllPredicates support to analyze left-out-join

Xurenhe created CALCITE-5109: Summary: RelMdAllPredicates support to analyze left-out-join Key: CALCITE-5109 URL: https://issues.apache.org/jira/browse/CALCITE-5109 Project: Calcite Issue Type:

[jira] [Commented] (CALCITE-5000) Expand rule of `AGGREGATE_REDUCE_FUNCTIONS`, when arg of agg-call is in the aggregate's group

[ https://issues.apache.org/jira/browse/CALCITE-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17526305#comment-17526305 ] Xurenhe commented on CALCITE-5000: -- [~julianhyde]  English is not my mother tongue, and I am very

[jira] [Commented] (CALCITE-5000) Expand rule of `AGGREGATE_REDUCE_FUNCTIONS`, when arg of agg-call is in the aggregate's group

[ https://issues.apache.org/jira/browse/CALCITE-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522676#comment-17522676 ] Xurenhe commented on CALCITE-5000: -- [~hyuan] Thanks for your review and merge. > Expand rule of

[jira] [Comment Edited] (CALCITE-5000) Expand rule of `AGGREGATE_REDUCE_FUNCTIONS`, when arg of agg-call is in the aggregate's group

[ https://issues.apache.org/jira/browse/CALCITE-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491863#comment-17491863 ] Xurenhe edited comment on CALCITE-5000 at 4/14/22 11:37 AM: Hi community

[jira] [Updated] (CALCITE-5087) Support bitwise operators

[ https://issues.apache.org/jira/browse/CALCITE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5087: - Description: As [email|https://lists.apache.org/thread/01vxw7rlzwzh82kk1p1srxhfhg5not30] discussed,

[jira] [Updated] (CALCITE-5087) Support bitwise operators

[ https://issues.apache.org/jira/browse/CALCITE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5087: - Description: As [email|https://lists.apache.org/thread/01vxw7rlzwzh82kk1p1srxhfhg5not30] discussed,

[jira] [Created] (CALCITE-5087) Support bitwise operators

Xurenhe created CALCITE-5087: Summary: Support bitwise operators Key: CALCITE-5087 URL: https://issues.apache.org/jira/browse/CALCITE-5087 Project: Calcite Issue Type: New Feature

[jira] [Commented] (CALCITE-5039) View:Timestamp cannot query Data:Long in GMT+8 TimeZone Env

[ https://issues.apache.org/jira/browse/CALCITE-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17518800#comment-17518800 ] Xurenhe commented on CALCITE-5039: -- I think it's special case and not a behavior of standard sql. >

[jira] [Commented] (CALCITE-5039) View:Timestamp cannot query Data:Long in GMT+8 TimeZone Env

[ https://issues.apache.org/jira/browse/CALCITE-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516270#comment-17516270 ] Xurenhe commented on CALCITE-5039: -- Hi [~itxiangkui]    ||id(int)||c1(varchar)||ts(bigint)||

[jira] [Resolved] (CALCITE-5038) Making AGGREGATE_ANY_PULL_UP_CONSTANTS's test case more rigorous

[ https://issues.apache.org/jira/browse/CALCITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe resolved CALCITE-5038. -- Resolution: Fixed Fixed in 

[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=17516229#comment-17516229 ] Xurenhe commented on CALCITE-5036: -- Hi [~yuanhsh] [~nobigo]  I see you gave the pass tickets for this

[jira] [Updated] (CALCITE-5069) RelMdRowCount has not consider 'EXCEPT ALL'

[ https://issues.apache.org/jira/browse/CALCITE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5069: - Summary: RelMdRowCount has not consider 'EXCEPT ALL' (was: Method of minus's getRowCount has not

[jira] [Comment Edited] (CALCITE-5069) Method of minus's getRowCount has not consider 'except all'

[ https://issues.apache.org/jira/browse/CALCITE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515929#comment-17515929 ] Xurenhe edited comment on CALCITE-5069 at 4/1/22 4:22 PM: --   I have pondered

[jira] [Commented] (CALCITE-5069) Method of minus's getRowCount has not consider 'except all'

[ https://issues.apache.org/jira/browse/CALCITE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515929#comment-17515929 ] Xurenhe commented on CALCITE-5069: --   I have pondered over the problem again and again.    

[jira] [Reopened] (CALCITE-5069) Method of minus's getRowCount has not consider 'except all'

[ https://issues.apache.org/jira/browse/CALCITE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe reopened CALCITE-5069: -- > Method of minus's getRowCount has not consider 'except all' >

[jira] [Comment Edited] (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=17515219#comment-17515219 ] Xurenhe edited comment on CALCITE-5036 at 3/31/22, 10:11 AM: - Hi all It's a

[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=17515219#comment-17515219 ] Xurenhe commented on CALCITE-5036: -- Hi all It's a small change to support predicate's analyzation of

[jira] [Comment Edited] (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=17515219#comment-17515219 ] Xurenhe edited comment on CALCITE-5036 at 3/31/22, 10:11 AM: - Hi all It's a

[jira] [Commented] (CALCITE-5054) Avatica Jdbc layer: Json vs ProtoBuf performance

[ https://issues.apache.org/jira/browse/CALCITE-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515210#comment-17515210 ] Xurenhe commented on CALCITE-5054: -- Hi [~itxiangkui]  It's unintelligible, could you show the test

[jira] [Commented] (CALCITE-5069) Method of minus's getRowCount has not consider 'except all'

[ https://issues.apache.org/jira/browse/CALCITE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514608#comment-17514608 ] Xurenhe commented on CALCITE-5069: -- My formula: * all = false, return original rowCount * all =

[jira] [Closed] (CALCITE-5069) Method of minus's getRowCount has not consider 'except all'

[ https://issues.apache.org/jira/browse/CALCITE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe closed CALCITE-5069. Resolution: Invalid > Method of minus's getRowCount has not consider 'except all' >

[jira] [Created] (CALCITE-5069) Method of minus's getRowCount has not consider 'except all'

Xurenhe created CALCITE-5069: Summary: Method of minus's getRowCount has not consider 'except all' Key: CALCITE-5069 URL: https://issues.apache.org/jira/browse/CALCITE-5069 Project: Calcite

[jira] [Commented] (CALCITE-5066) Support variables with “@" and “@@" prefixes (like MySQL)

[ https://issues.apache.org/jira/browse/CALCITE-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514057#comment-17514057 ] Xurenhe commented on CALCITE-5066: -- [~aochagavia]  This sql just like mysql, which querying system

[jira] [Commented] (CALCITE-5043) GROUP BY alias or SELECT field should be determined by using sql dialect when alias and field are same

[ https://issues.apache.org/jira/browse/CALCITE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514051#comment-17514051 ] Xurenhe commented on CALCITE-5043: -- [~yanjing.wang]  Thanks for your careful explain. I know these

[jira] [Commented] (CALCITE-5043) GROUP BY alias or SELECT field should be determined by using sql dialect when alias and field are same

[ https://issues.apache.org/jira/browse/CALCITE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17513332#comment-17513332 ] Xurenhe commented on CALCITE-5043: -- It may be related to

[jira] [Commented] (CALCITE-5039) View:Timestamp cannot query Data:Long in GMT+8 TimeZone Env

[ https://issues.apache.org/jira/browse/CALCITE-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17513324#comment-17513324 ] Xurenhe commented on CALCITE-5039: -- I guess you're using the type of bigint to store time data. These

[jira] [Comment Edited] (CALCITE-5044) JDBC adapter generates integer literal in ORDER BY, which some dialects wrongly interpret as a reference to a field

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511586#comment-17511586 ] Xurenhe edited comment on CALCITE-5044 at 3/24/22, 11:59 AM: - Hi

[jira] [Commented] (CALCITE-5044) JDBC adapter generates integer literal in ORDER BY, which some dialects wrongly interpret as a reference to a field

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511586#comment-17511586 ] Xurenhe commented on CALCITE-5044: -- Hi [~julianhyde]  I have finished the review. I think we need

[jira] [Commented] (CALCITE-5044) JDBC adapter generates integer literal in ORDER BY, which some dialects wrongly interpret as a reference to a field

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511529#comment-17511529 ] Xurenhe commented on CALCITE-5044: -- [~julianhyde]  I'm sorry I didn't see your latest reply.:) And,

[jira] [Commented] (CALCITE-5044) JDBC adapter generates integer literal in ORDER BY, which some dialects wrongly interpret as a reference to a field

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511528#comment-17511528 ] Xurenhe commented on CALCITE-5044: -- [~julianhyde]  Thanks for your reply. My first plan is removing

[jira] [Comment Edited] (CALCITE-5053) Implement “show catalogs/databases/schemas" semantics

[ https://issues.apache.org/jira/browse/CALCITE-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511333#comment-17511333 ] Xurenhe edited comment on CALCITE-5053 at 3/23/22, 3:59 PM: *SHOW

[jira] [Commented] (CALCITE-5053) Implement “show catalogs/databases/schemas" semantics

[ https://issues.apache.org/jira/browse/CALCITE-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511333#comment-17511333 ] Xurenhe commented on CALCITE-5053: -- *SHOW DATABASES* may be MySQL's behavior, which is executed for

[jira] [Commented] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511322#comment-17511322 ] Xurenhe commented on CALCITE-5044: -- Ok, Got it. It's really closely related to *isOrderByOrdinal()*

[jira] [Comment Edited] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511322#comment-17511322 ] Xurenhe edited comment on CALCITE-5044 at 3/23/22, 3:40 PM: [~julianhyde] 

[jira] [Comment Edited] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510502#comment-17510502 ] Xurenhe edited comment on CALCITE-5044 at 3/22/22, 2:01 PM: [~julianhyde]

[jira] [Comment Edited] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510502#comment-17510502 ] Xurenhe edited comment on CALCITE-5044 at 3/22/22, 2:00 PM: [~julianhyde]

[jira] [Comment Edited] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510502#comment-17510502 ] Xurenhe edited comment on CALCITE-5044 at 3/22/22, 1:57 PM: Yes, I agree

[jira] [Comment Edited] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510502#comment-17510502 ] Xurenhe edited comment on CALCITE-5044 at 3/22/22, 1:56 PM: Yes, I agree

[jira] [Commented] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510502#comment-17510502 ] Xurenhe commented on CALCITE-5044: -- Yes, I agree with you. We could define a

[jira] [Commented] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508201#comment-17508201 ] Xurenhe commented on CALCITE-5044: -- *Context#orderField* should return null if the current dialect

[jira] [Updated] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5044: - Attachment: image-2022-03-17-21-45-22-988.png > OrderBy constant executing RelToSql ambiguously >

[jira] [Commented] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507678#comment-17507678 ] Xurenhe commented on CALCITE-5044: -- [~julianhyde]  I'm very glad to receive your reply. I choose first

[jira] [Updated] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5044: - Description:   There is ambiguous in the rel-to-sql's converter when meeting `order by constant `.

[jira] [Updated] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

[ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5044: - Description:   There is ambiguous in the rel-to-sql's converter when meeting `order by constant `.

[jira] [Created] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

Xurenhe created CALCITE-5044: Summary: OrderBy constant executing RelToSql ambiguously Key: CALCITE-5044 URL: https://issues.apache.org/jira/browse/CALCITE-5044 Project: Calcite Issue Type:

[jira] [Commented] (CALCITE-4512) group by expression has argument name same with select list item alias, causes validation error

[ https://issues.apache.org/jira/browse/CALCITE-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504736#comment-17504736 ] Xurenhe commented on CALCITE-4512: -- Hi all, I met the similar problem, and do some investigations

[jira] [Comment Edited] (CALCITE-5029) Babel parser support identifier starting with number

[ https://issues.apache.org/jira/browse/CALCITE-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502683#comment-17502683 ] Xurenhe edited comment on CALCITE-5029 at 3/11/22, 3:17 AM: Define a custom

[jira] [Commented] (CALCITE-4998) Subquery Regression

[ https://issues.apache.org/jira/browse/CALCITE-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504362#comment-17504362 ] Xurenhe commented on CALCITE-4998: -- Hi [~wnoble]  I try to build a similar test case by your rel's

[jira] [Comment Edited] (CALCITE-5035) Define a rule of SortProjectPullUpConstantsRule to pull up constant's project under Sort

[ https://issues.apache.org/jira/browse/CALCITE-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504240#comment-17504240 ] Xurenhe edited comment on CALCITE-5035 at 3/10/22, 1:25 PM: I've been

[jira] [Updated] (CALCITE-5038) Making AGGREGATE_ANY_PULL_UP_CONSTANTS's test case more rigorous

[ https://issues.apache.org/jira/browse/CALCITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5038: - Description: Some test cases for AGGREGATE_ANY_PULL_UP_CONSTANTS aren't rigorous.   {code:java} //sql

[jira] [Commented] (CALCITE-5035) Define a rule of SortProjectPullUpConstantsRule to pull up constant's project under Sort

[ https://issues.apache.org/jira/browse/CALCITE-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504240#comment-17504240 ] Xurenhe commented on CALCITE-5035: -- I've been thinking this over and over recently Some sort elements

[jira] [Comment Edited] (CALCITE-5035) Define a rule of SortProjectPullUpConstantsRule to pull up constant's project under Sort

[ https://issues.apache.org/jira/browse/CALCITE-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504240#comment-17504240 ] Xurenhe edited comment on CALCITE-5035 at 3/10/22, 12:54 PM: - I've been

[jira] [Created] (CALCITE-5038) Making AGGREGATE_ANY_PULL_UP_CONSTANTS's test case more rigorous

Xurenhe created CALCITE-5038: Summary: Making AGGREGATE_ANY_PULL_UP_CONSTANTS's test case more rigorous Key: CALCITE-5038 URL: https://issues.apache.org/jira/browse/CALCITE-5038 Project: Calcite

[jira] [Commented] (CALCITE-5035) Define a rule of SortProjectPullUpConstantsRule to pull up constant's project under Sort

[ https://issues.apache.org/jira/browse/CALCITE-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503424#comment-17503424 ] Xurenhe commented on CALCITE-5035: -- [~asolimando]  Thanks your reply. The related

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

Xurenhe created CALCITE-5036: Summary: `RelMetadataQuery#getPulledUpPredicates` support to analyze constant key for the operator of IS_NOT_DISTINCT_FROM Key: CALCITE-5036 URL:

[jira] [Commented] (CALCITE-5035) Define a rule of SortProjectPullUpConstantsRule to pull up constant's project under Sort

[ https://issues.apache.org/jira/browse/CALCITE-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503285#comment-17503285 ] Xurenhe commented on CALCITE-5035: -- [~julianhyde]  Thanks for your reply. I try to rename this rule,

[jira] [Updated] (CALCITE-5035) Define a rule of SortProjectPullUpConstantsRule to pull up constant's project under Sort

[ https://issues.apache.org/jira/browse/CALCITE-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xurenhe updated CALCITE-5035: - Summary: Define a rule of SortProjectPullUpConstantsRule to pull up constant's project under Sort

[jira] [Created] (CALCITE-5035) Define a rule of SortProjectPullUpConstantsRule to pull up constants project under Sort

Xurenhe created CALCITE-5035: Summary: Define a rule of SortProjectPullUpConstantsRule to pull up constants project under Sort Key: CALCITE-5035 URL: https://issues.apache.org/jira/browse/CALCITE-5035

[jira] [Commented] (CALCITE-5029) Babel parser support identifier starting with number

[ https://issues.apache.org/jira/browse/CALCITE-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502683#comment-17502683 ] Xurenhe commented on CALCITE-5029: -- Hi all PR is ready, please review it. Thanks PR:

[jira] [Commented] (CALCITE-5029) Babel parser support identifier starting with number

[ https://issues.apache.org/jira/browse/CALCITE-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502065#comment-17502065 ] Xurenhe commented on CALCITE-5029: -- [~nobigo] Thanks for your reply. It need be a numeric SQL

[jira] [Created] (CALCITE-5029) Babel parser support identifier starting with number

Xurenhe created CALCITE-5029: Summary: Babel parser support identifier starting with number Key: CALCITE-5029 URL: https://issues.apache.org/jira/browse/CALCITE-5029 Project: Calcite Issue Type:

  1   2   3   4   >