[jira] [Created] (CALCITE-4363) Need a utility to check if a SQL operator is standard

Liya Fan created CALCITE-4363: - Summary: Need a utility to check if a SQL operator is standard Key: CALCITE-4363 URL: https://issues.apache.org/jira/browse/CALCITE-4363 Project: Calcite Issue

[jira] [Created] (CALCITE-4364) "a in (1, 2) and a = 1" should be simplified to "a=1"

Danny Chen created CALCITE-4364: --- Summary: "a in (1, 2) and a = 1" should be simplified to "a=1" Key: CALCITE-4364 URL: https://issues.apache.org/jira/browse/CALCITE-4364 Project: Calcite

[jira] [Updated] (CALCITE-4354) add support for ROW/STRUCT data types to ITEM operator

[ https://issues.apache.org/jira/browse/CALCITE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stamatis Zampetakis updated CALCITE-4354: - Fix Version/s: 1.27.0 > add support for ROW/STRUCT data types to ITEM operator

[jira] [Updated] (CALCITE-4354) Allow ITEM operator on ROW/STRUCT data types

[ https://issues.apache.org/jira/browse/CALCITE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stamatis Zampetakis updated CALCITE-4354: - Summary: Allow ITEM operator on ROW/STRUCT data types (was: add support for

[jira] [Commented] (CALCITE-4360) Apply SubstitutionRule first in top-down driven rule apply

[ https://issues.apache.org/jira/browse/CALCITE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222730#comment-17222730 ] Chunwei Lei commented on CALCITE-4360: -- I am sorry that I misunderstood the codes. Currently, the

[jira] [Updated] (CALCITE-4277) When rel has been removed from its subset, skip the origin rule match (Jiatao Tao)

[ https://issues.apache.org/jira/browse/CALCITE-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiatao Tao updated CALCITE-4277: Summary: When rel has been removed from its subset, skip the origin rule match (Jiatao Tao)

[jira] [Commented] (CALCITE-4360) Apply SubstitutionRule first in top-down driven rule apply

[ https://issues.apache.org/jira/browse/CALCITE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222742#comment-17222742 ] Liya Fan commented on CALCITE-4360: --- [~Chunwei Lei] Thanks for the investigation.  The process is a

[jira] [Commented] (CALCITE-4360) Apply SubstitutionRule first in top-down driven rule apply

[ https://issues.apache.org/jira/browse/CALCITE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222749#comment-17222749 ] Chunwei Lei commented on CALCITE-4360: -- [~fan_li_ya] Makes sense.  > Apply SubstitutionRule first

[jira] [Updated] (CALCITE-4364) "a in (1, 2) and a = 1" should be simplified to "a=1"

[ https://issues.apache.org/jira/browse/CALCITE-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Chen updated CALCITE-4364: Description: Check this test in {{RexProgramTest}}: {code:java} @Test void testSimplifyInAnd()

[jira] [Commented] (CALCITE-4358) Potential memory leak in VolcanoPlanner#materializations due to circular reference

[ https://issues.apache.org/jira/browse/CALCITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222810#comment-17222810 ] Stamatis Zampetakis commented on CALCITE-4358: -- I don't doubt there is a circular

[jira] [Resolved] (CALCITE-4360) Apply SubstitutionRule first in top-down driven rule apply

[ https://issues.apache.org/jira/browse/CALCITE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chunwei Lei resolved CALCITE-4360. -- Resolution: Invalid > Apply SubstitutionRule first in top-down driven rule apply >

[jira] [Commented] (CALCITE-4360) Apply SubstitutionRule first in top-down driven rule apply

[ https://issues.apache.org/jira/browse/CALCITE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222756#comment-17222756 ] Chunwei Lei commented on CALCITE-4360: -- BTW, I found all the test cases in TopDownOptTest failed

[jira] [Comment Edited] (CALCITE-4360) Apply SubstitutionRule first in top-down driven rule apply

[ https://issues.apache.org/jira/browse/CALCITE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222756#comment-17222756 ] Chunwei Lei edited comment on CALCITE-4360 at 10/29/20, 7:51 AM: - BTW,

[jira] [Created] (CALCITE-4365) SEARCHes in ANDs and ORs cannot be simplified if the complexity of its SARG can actually be reduced to 1

Caizhi Weng created CALCITE-4365: Summary: SEARCHes in ANDs and ORs cannot be simplified if the complexity of its SARG can actually be reduced to 1 Key: CALCITE-4365 URL:

[jira] [Commented] (CALCITE-4364) "a in (1, 2) and a = 1" should be simplified to "a=1"

[ https://issues.apache.org/jira/browse/CALCITE-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223109#comment-17223109 ] Julian Hyde commented on CALCITE-4364: -- Might be fixed by CALCITE-4352. Can you test against the

[jira] [Commented] (CALCITE-4348) Materialization recognition fails when query has calculation expression

[ https://issues.apache.org/jira/browse/CALCITE-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223175#comment-17223175 ] Julian Hyde commented on CALCITE-4348: -- bq. By the way ... Yes, let's get CALCITE-3409 reviewed.

[jira] [Updated] (CALCITE-4358) Potential memory leak in VolcanoPlanner#materializations due to circular reference

[ https://issues.apache.org/jira/browse/CALCITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiatao Tao updated CALCITE-4358: Attachment: screenshot-1.png > Potential memory leak in VolcanoPlanner#materializations due to

[jira] [Commented] (CALCITE-4358) Potential memory leak in VolcanoPlanner#materializations due to circular reference

[ https://issues.apache.org/jira/browse/CALCITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222746#comment-17222746 ] Jiatao Tao commented on CALCITE-4358: - Can this be the evidence? I show the incoming objects, the

[jira] [Updated] (CALCITE-4358) Potential memory leak in VolcanoPlanner#materializations due to circular reference

[ https://issues.apache.org/jira/browse/CALCITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiatao Tao updated CALCITE-4358: Description: Hi fellows We use Calcite's materialization view in our product env, and it OOM

[jira] [Commented] (CALCITE-4362) Unable to parse queries that use BigQuery pseudo columns _PARTITIONDATE/_PARTITIONTIME

[ https://issues.apache.org/jira/browse/CALCITE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223154#comment-17223154 ] Julian Hyde commented on CALCITE-4362: -- The solution is probably to make {{_PARTITIONDATE}} and

[jira] [Assigned] (CALCITE-4362) Unable to parse queries that use BigQuery pseudo columns _PARTITIONDATE/_PARTITIONTIME

[ https://issues.apache.org/jira/browse/CALCITE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde reassigned CALCITE-4362: Assignee: Julian Hyde > Unable to parse queries that use BigQuery pseudo columns >

[jira] [Commented] (CALCITE-4361) BigQuery comments starting with # cause SqlParseException

[ https://issues.apache.org/jira/browse/CALCITE-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223166#comment-17223166 ] Julian Hyde commented on CALCITE-4361: -- Can you please check whether '#' starts a comment if it is

[jira] [Commented] (CALCITE-3409) Add an interface in MaterializedViewSubstitutionVisitor to allow registering UnifyRule

[ https://issues.apache.org/jira/browse/CALCITE-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223174#comment-17223174 ] Julian Hyde commented on CALCITE-3409: -- [~jcamachorodriguez] Can you please review this PR? > Add

[jira] [Commented] (CALCITE-4365) SEARCHes in ANDs and ORs cannot be simplified if the complexity of its SARG can actually be reduced to 1

[ https://issues.apache.org/jira/browse/CALCITE-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223108#comment-17223108 ] Julian Hyde commented on CALCITE-4365: -- Can you check my PR for CALCITE-4352 and see whether it

[jira] [Commented] (CALCITE-4363) Need a utility to check if a SQL operator is standard

[ https://issues.apache.org/jira/browse/CALCITE-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223122#comment-17223122 ] Julian Hyde commented on CALCITE-4363: -- Can you clarify what you mean by 'standard'? We have the

[jira] [Commented] (CALCITE-4348) Materialization recognition fails when query has calculation expression

[ https://issues.apache.org/jira/browse/CALCITE-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223171#comment-17223171 ] Julian Hyde commented on CALCITE-4348: -- {quote}It seems like that can not preserves line breaks

[jira] [Created] (CALCITE-4366) LatticeSuggester should treat UNION / VALUES sub-expressions as tables

Julian Hyde created CALCITE-4366: Summary: LatticeSuggester should treat UNION / VALUES sub-expressions as tables Key: CALCITE-4366 URL: https://issues.apache.org/jira/browse/CALCITE-4366 Project:

[jira] [Assigned] (CALCITE-4366) LatticeSuggester should treat UNION / VALUES sub-expressions as tables

[ https://issues.apache.org/jira/browse/CALCITE-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde reassigned CALCITE-4366: Assignee: Julian Hyde > LatticeSuggester should treat UNION / VALUES sub-expressions as

[jira] [Closed] (CALCITE-4365) SEARCHes in ANDs and ORs cannot be simplified if the complexity of its SARG can actually be reduced to 1

[ https://issues.apache.org/jira/browse/CALCITE-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Chen closed CALCITE-4365. --- Fix Version/s: 1.27.0 Assignee: Danny Chen Resolution: Duplicate Close because it

[jira] [Commented] (CALCITE-4364) "a in (1, 2) and a = 1" should be simplified to "a=1"

[ https://issues.apache.org/jira/browse/CALCITE-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223329#comment-17223329 ] Danny Chen commented on CALCITE-4364: - Tested, not fixed by CALCITE-4352 yet. > "a in (1, 2) and a

[jira] [Created] (CALCITE-4367) Incorrect documentation for Avatica JSON request/response signatures

John Bodley created CALCITE-4367: Summary: Incorrect documentation for Avatica JSON request/response signatures Key: CALCITE-4367 URL: https://issues.apache.org/jira/browse/CALCITE-4367 Project:

[jira] [Commented] (CALCITE-3913) Test correctness using formal verification techniques

[ https://issues.apache.org/jira/browse/CALCITE-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223278#comment-17223278 ] Qi Zhou commented on CALCITE-3913: -- The commit tree in the previous pull request becomes too