[jira] [Comment Edited] (CALCITE-5604) Avg function should infer correct data type

[ https://issues.apache.org/jira/browse/CALCITE-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703639#comment-17703639 ] Shuo Cheng edited comment on CALCITE-5604 at 3/22/23 12:17 PM: --

[jira] [Commented] (CALCITE-5604) Avg function should infer correct data type

[ https://issues.apache.org/jira/browse/CALCITE-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703639#comment-17703639 ] Shuo Cheng commented on CALCITE-5604: - Hi [~loganzheng], As Ansi SQL 2011 declared,

[jira] [Commented] (CALCITE-3760) Rewriting non-deterministic function can break query semantics

[ https://issues.apache.org/jira/browse/CALCITE-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376160#comment-17376160 ] Shuo Cheng commented on CALCITE-3760: - > As we discussed recently, it would be ille

[jira] [Comment Edited] (CALCITE-4118) RexSimplify might remove CAST from RexNode incorrectly

[ https://issues.apache.org/jira/browse/CALCITE-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155086#comment-17155086 ] Shuo Cheng edited comment on CALCITE-4118 at 7/10/20, 4:12 AM: --

[jira] [Commented] (CALCITE-4118) RexSimplify might remove CAST from RexNode incorrectly

[ https://issues.apache.org/jira/browse/CALCITE-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155086#comment-17155086 ] Shuo Cheng commented on CALCITE-4118: - [~kgyrtkirk], please have a look. There is a

[jira] [Created] (CALCITE-4118) RexSimplify might remove CAST from RexNode incorrectly

Shuo Cheng created CALCITE-4118: --- Summary: RexSimplify might remove CAST from RexNode incorrectly Key: CALCITE-4118 URL: https://issues.apache.org/jira/browse/CALCITE-4118 Project: Calcite Issu

[jira] [Commented] (CALCITE-4053) RexSimplify should not pass exprs containing non-const subExprs to RexExecutor

[ https://issues.apache.org/jira/browse/CALCITE-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128916#comment-17128916 ] Shuo Cheng commented on CALCITE-4053: - PR: [https://github.com/apache/calcite/pull/

[jira] [Updated] (CALCITE-4053) RexSimplify should not pass exprs containing non-const subExprs to RexExecutor

[ https://issues.apache.org/jira/browse/CALCITE-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-4053: Summary: RexSimplify should not pass exprs containing non-const subExprs to RexExecutor (was: Re

[jira] [Assigned] (CALCITE-4053) RexSimplify should not pass exprs containing non-const subExprs to RexExecutor

[ https://issues.apache.org/jira/browse/CALCITE-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng reassigned CALCITE-4053: --- Assignee: Shuo Cheng > RexSimplify should not pass exprs containing non-const subExprs to

[jira] [Created] (CALCITE-4053) RexSimplify should not pass exprs containing non-const subExprs to RexExecutor#reduce

Shuo Cheng created CALCITE-4053: --- Summary: RexSimplify should not pass exprs containing non-const subExprs to RexExecutor#reduce Key: CALCITE-4053 URL: https://issues.apache.org/jira/browse/CALCITE-4053

[jira] [Commented] (CALCITE-3979) Unexpected removing of CAST in ReduceExpressionsRule

[ https://issues.apache.org/jira/browse/CALCITE-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102332#comment-17102332 ] Shuo Cheng commented on CALCITE-3979: - cc [~Chunwei Lei] > Unexpected removing of

[jira] [Created] (CALCITE-3979) Unexpected removing of CAST in ReduceExpressionsRule

Shuo Cheng created CALCITE-3979: --- Summary: Unexpected removing of CAST in ReduceExpressionsRule Key: CALCITE-3979 URL: https://issues.apache.org/jira/browse/CALCITE-3979 Project: Calcite Issue

[jira] [Commented] (CALCITE-3893) SQL with GROUP_ID may generate wrong plan

[ https://issues.apache.org/jira/browse/CALCITE-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073628#comment-17073628 ] Shuo Cheng commented on CALCITE-3893: - Hi, [~donnyzone], I'm not quite understandin

[jira] [Commented] (CALCITE-3893) SQL with GROUP_ID may generate wrong plan

[ https://issues.apache.org/jira/browse/CALCITE-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073506#comment-17073506 ] Shuo Cheng commented on CALCITE-3893: - The plan I suggested may not be rigorous eno

[jira] [Issue Comment Deleted] (CALCITE-3893) SQL with GROUP_ID may generate wrong plan

[ https://issues.apache.org/jira/browse/CALCITE-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3893: Comment: was deleted (was: Or like this:) > SQL with GROUP_ID may generate wrong plan >

[jira] [Commented] (CALCITE-3893) SQL with GROUP_ID may generate wrong plan

[ https://issues.apache.org/jira/browse/CALCITE-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073498#comment-17073498 ] Shuo Cheng commented on CALCITE-3893: - Or like this: > SQL with GROUP_ID may gener

[jira] [Updated] (CALCITE-3893) SQL with GROUP_ID may generate wrong plan

[ https://issues.apache.org/jira/browse/CALCITE-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3893: Description: Consider the following SQL: {code:java} select deptno, group_id() as g, count(*)

[jira] [Updated] (CALCITE-3893) SQL with GROUP_ID may generate wrong plan

[ https://issues.apache.org/jira/browse/CALCITE-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3893: Summary: SQL with GROUP_ID may generate wrong plan (was: Sql with GROUP_ID may generate wrong pl

[jira] [Created] (CALCITE-3893) Sql with GROUP_ID may generate wrong plan

Shuo Cheng created CALCITE-3893: --- Summary: Sql with GROUP_ID may generate wrong plan Key: CALCITE-3893 URL: https://issues.apache.org/jira/browse/CALCITE-3893 Project: Calcite Issue Type: Bug

[jira] [Commented] (CALCITE-3830) The ‘approximate’ field should be considered when computing the digest of AggregateCall

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046503#comment-17046503 ] Shuo Cheng commented on CALCITE-3830: - Hi [~julianhyde], I'm considering where the 

[jira] [Commented] (CALCITE-3830) The ‘approximate’ field should be considered when computing the digest of AggregateCall

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046452#comment-17046452 ] Shuo Cheng commented on CALCITE-3830: - [~julianhyde], I've been also hesitated in t

[jira] [Updated] (CALCITE-3830) The ‘approximate’ field should be considered when computing the digest of AggregateCall

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3830: Description: In planner optimization, the digest  of Aggregate node contains digest of its Aggre

[jira] [Commented] (CALCITE-3830) The ‘approximate’ field should be considered when computing the digest of AggregateCall

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046184#comment-17046184 ] Shuo Cheng commented on CALCITE-3830: - [~danny0405], I've created a pr, please have

[jira] [Assigned] (CALCITE-3830) The ‘approximate’ field should be considered when computing the digest of AggregateCall

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng reassigned CALCITE-3830: --- Assignee: Shuo Cheng > The ‘approximate’ field should be considered when computing the dig

[jira] [Updated] (CALCITE-3830) The ‘approximate’ field should be considered when computing the digest of AggregateCall

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3830: Summary: The ‘approximate’ field should be considered when computing the digest of AggregateCall

[jira] [Updated] (CALCITE-3830) Digest of AggregateCall do not consider the ‘approximate’ attribute

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3830: Summary: Digest of AggregateCall do not consider the ‘approximate’ attribute (was: The 'approxim

[jira] [Updated] (CALCITE-3830) Digest of AggregateCall do not consider the ‘approximate’ attribute

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3830: Description: In planner optimization, the digest  of Aggregate node contains digest of its Aggre

[jira] [Updated] (CALCITE-3830) The 'approximate' field should be considered in AggregateCall.toString() which is used as the digest

[ https://issues.apache.org/jira/browse/CALCITE-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3830: Component/s: core Fix Version/s: 1.22.0 Affects Version/s: 1.21.0 Desc

[jira] [Created] (CALCITE-3830) Digest of AggregateCall do not consider the ''

Shuo Cheng created CALCITE-3830: --- Summary: Digest of AggregateCall do not consider the '' Key: CALCITE-3830 URL: https://issues.apache.org/jira/browse/CALCITE-3830 Project: Calcite Issue Type:

[jira] [Commented] (CALCITE-3741) duplicate ‘ordre by‘ key word generate in select

[ https://issues.apache.org/jira/browse/CALCITE-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017651#comment-17017651 ] Shuo Cheng commented on CALCITE-3741: - Hi, James, it would be more clear if you can

[jira] [Commented] (CALCITE-3723) Following the change to add hints to RelNode, deprecate the old constructors

[ https://issues.apache.org/jira/browse/CALCITE-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013972#comment-17013972 ] Shuo Cheng commented on CALCITE-3723: - In current design, when we create a `Hintabl

[jira] [Commented] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013369#comment-17013369 ] Shuo Cheng commented on CALCITE-3721: - Sorry, Danny, I miss understood what you mea

[jira] [Issue Comment Deleted] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3721: Comment: was deleted (was: Hi, Danny, actually, A and B have different groupSet: {code:java} Logi

[jira] [Commented] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013365#comment-17013365 ] Shuo Cheng commented on CALCITE-3721: - Hi, Danny, actually, A and B have different

[jira] [Issue Comment Deleted] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3721: Comment: was deleted (was: Hi, Danny, actually A and B have different groupSet, because filter ar

[jira] [Commented] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013363#comment-17013363 ] Shuo Cheng commented on CALCITE-3721: - Hi, Danny, actually A and B have different g

[jira] [Commented] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012641#comment-17012641 ] Shuo Cheng commented on CALCITE-3721: - Yeah, Danny, this column is actually useless

[jira] [Commented] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012516#comment-17012516 ] Shuo Cheng commented on CALCITE-3721: - Hi, [~danny0405], thanks for you reminder, J

[jira] [Updated] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3721: Description: In `AggregateExpandDistinctAggregatesRule`, when the distinct aggregate call is  rew

[jira] [Updated] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

[ https://issues.apache.org/jira/browse/CALCITE-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3721: Description: In `AggregateExpandDistinctAggregatesRule`, when the distinct aggregate call is  rew

[jira] [Created] (CALCITE-3721) Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule`

Shuo Cheng created CALCITE-3721: --- Summary: Filter of distinct aggregate call is lost after applying `AggregateExpandDistinctAggregatesRule` Key: CALCITE-3721 URL: https://issues.apache.org/jira/browse/CALCITE-3721

[jira] [Commented] (CALCITE-3638) Reduce ambiguous hint strategies

[ https://issues.apache.org/jira/browse/CALCITE-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003925#comment-17003925 ] Shuo Cheng commented on CALCITE-3638: - I also think option 2 is better. The SQL wil

[jira] [Updated] (CALCITE-3631) Support SQL hints for Calc

[ https://issues.apache.org/jira/browse/CALCITE-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3631: Component/s: core > Support SQL hints for Calc > -- > > K

[jira] [Updated] (CALCITE-3631) Support SQL hints for Calc

[ https://issues.apache.org/jira/browse/CALCITE-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3631: Fix Version/s: 1.22.0 > Support SQL hints for Calc > -- > >

[jira] [Updated] (CALCITE-3631) Support SQL hints for Calc

[ https://issues.apache.org/jira/browse/CALCITE-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3631: Affects Version/s: 1.21.0 > Support SQL hints for Calc > -- > >

[jira] [Created] (CALCITE-3631) Support SQL hints for Calc

Shuo Cheng created CALCITE-3631: --- Summary: Support SQL hints for Calc Key: CALCITE-3631 URL: https://issues.apache.org/jira/browse/CALCITE-3631 Project: Calcite Issue Type: Sub-task

[jira] [Assigned] (CALCITE-3631) Support SQL hints for Calc

[ https://issues.apache.org/jira/browse/CALCITE-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng reassigned CALCITE-3631: --- Assignee: Shuo Cheng > Support SQL hints for Calc > -- > >

[jira] [Commented] (CALCITE-2905) Migrate build system to Gradle

[ https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003230#comment-17003230 ] Shuo Cheng commented on CALCITE-2905: - [~vladimirsitnikov], It make sense, but curr

[jira] [Commented] (CALCITE-2905) Migrate build system to Gradle

[ https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003216#comment-17003216 ] Shuo Cheng commented on CALCITE-2905: - [~vladimirsitnikov] , it works now, thanks!

[jira] [Commented] (CALCITE-2905) Migrate build system to Gradle

[ https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003175#comment-17003175 ] Shuo Cheng commented on CALCITE-2905: - [~vladimirsitnikov], I tried and exception a

[jira] [Updated] (CALCITE-2905) Migrate build system to Gradle

[ https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-2905: Attachment: image-2019-12-25-17-50-45-431.png > Migrate build system to Gradle >

[jira] [Commented] (CALCITE-2905) Migrate build system to Gradle

[ https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002741#comment-17002741 ] Shuo Cheng commented on CALCITE-2905: - [~vladimirsitnikov], actually, flink has som

[jira] [Commented] (CALCITE-2905) Migrate build system to Gradle

[ https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002717#comment-17002717 ] Shuo Cheng commented on CALCITE-2905: - Hi, [~vladimirsitnikov], I have problem usi

[jira] [Updated] (CALCITE-2905) Migrate build system to Gradle

[ https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-2905: Attachment: image-2019-12-24-16-18-51-071.png > Migrate build system to Gradle >

[jira] [Updated] (CALCITE-2905) Migrate build system to Gradle

[ https://issues.apache.org/jira/browse/CALCITE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-2905: Attachment: image-2019-12-24-16-16-42-006.png > Migrate build system to Gradle >

[jira] [Assigned] (CALCITE-3590) Support SQL hints for Aggregate

[ https://issues.apache.org/jira/browse/CALCITE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng reassigned CALCITE-3590: --- Assignee: Shuo Cheng > Support SQL hints for Aggregate > --- >

[jira] [Commented] (CALCITE-3590) Support SQL hints for Aggregate

[ https://issues.apache.org/jira/browse/CALCITE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997869#comment-16997869 ] Shuo Cheng commented on CALCITE-3590: - Hi [~amaliujia], I'm sorry for not syncing i

[jira] [Comment Edited] (CALCITE-3594) Support hot Groupby keys hint

[ https://issues.apache.org/jira/browse/CALCITE-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996969#comment-16996969 ] Shuo Cheng edited comment on CALCITE-3594 at 12/16/19 5:05 AM: --

[jira] [Commented] (CALCITE-3594) Support hot Groupby keys hint

[ https://issues.apache.org/jira/browse/CALCITE-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996969#comment-16996969 ] Shuo Cheng commented on CALCITE-3594: - Hi, [~amaliujia] , I'm working on CALCITE-35

[jira] [Updated] (CALCITE-3590) Support SQL hints for Aggregate.

[ https://issues.apache.org/jira/browse/CALCITE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3590: Description: Currently in CALCITE-482, hints are only supported for Project, Join and TableScan.

[jira] [Updated] (CALCITE-3590) Support SQL hints for Aggregate.

[ https://issues.apache.org/jira/browse/CALCITE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3590: Description: Currently in CALCITE-482, hints are only supported for Project, Join and TableScan.

[jira] [Updated] (CALCITE-3590) Support SQL hints for Aggregate.

[ https://issues.apache.org/jira/browse/CALCITE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3590: Description: Currently in CALCITE-482, hints are only supported for Project, Join and TableScan.

[jira] [Updated] (CALCITE-3590) Support SQL hints for Aggregate.

[ https://issues.apache.org/jira/browse/CALCITE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3590: Description: Currently in CALCITE-482, hints are only supported for Project, Join and TableScan.

[jira] [Updated] (CALCITE-3590) Support SQL hints for Aggregate.

[ https://issues.apache.org/jira/browse/CALCITE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3590: Description: Currently in CALCITE-482, hints are only supported for Project, Join and TableScan.

[jira] [Created] (CALCITE-3590) Support SQL hints for Aggregate.

Shuo Cheng created CALCITE-3590: --- Summary: Support SQL hints for Aggregate. Key: CALCITE-3590 URL: https://issues.apache.org/jira/browse/CALCITE-3590 Project: Calcite Issue Type: Sub-task

[jira] [Created] (CALCITE-3527) enrich tests for sql hints.

Shuo Cheng created CALCITE-3527: --- Summary: enrich tests for sql hints. Key: CALCITE-3527 URL: https://issues.apache.org/jira/browse/CALCITE-3527 Project: Calcite Issue Type: Sub-task Affect

[jira] [Updated] (CALCITE-3519) `inheritPath` of `RelHint` represented by `ImmutableBitSet` may be incomplete.

[ https://issues.apache.org/jira/browse/CALCITE-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3519: Description: Taking the following SQL with hint for example: (Copying from `org.apache.calcite.t

[jira] [Updated] (CALCITE-3519) `inheritPath` of `RelHint` represented by `ImmutableBitSet` may be incomplete.

[ https://issues.apache.org/jira/browse/CALCITE-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuo Cheng updated CALCITE-3519: Description: Taking the following SQL with hint for example: (Copying from `org.apache.calcite.t

[jira] [Created] (CALCITE-3519) `inheritPath` of `RelHint` represented by `ImmutableBitSet` may be incomplete.

Shuo Cheng created CALCITE-3519: --- Summary: `inheritPath` of `RelHint` represented by `ImmutableBitSet` may be incomplete. Key: CALCITE-3519 URL: https://issues.apache.org/jira/browse/CALCITE-3519 Projec