[jira] [Commented] (CALCITE-4737) Add Volcano visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459849#comment-17459849 ] Thomas Rebele commented on CALCITE-4737: [~zabetak] had proposed to make the vi

[jira] [Comment Edited] (CALCITE-4737) Add Volcano visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459849#comment-17459849 ] Thomas Rebele edited comment on CALCITE-4737 at 12/15/21, 10:50 AM: -

[jira] [Assigned] (CALCITE-4737) Add Volcano visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele reassigned CALCITE-4737: -- Assignee: Thomas Rebele > Add Volcano visualizer for debugging > ---

[jira] [Updated] (CALCITE-4737) Add Volcano visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4737: --- Fix Version/s: 1.29.0 > Add Volcano visualizer for debugging >

[jira] [Updated] (CALCITE-4737) Add Volcano visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4737: --- Issue Type: New Feature (was: Bug) > Add Volcano visualizer for debugging > --

[jira] [Created] (CALCITE-4944) Add a property to activate the RuleMatchVisualizer

Thomas Rebele created CALCITE-4944: -- Summary: Add a property to activate the RuleMatchVisualizer Key: CALCITE-4944 URL: https://issues.apache.org/jira/browse/CALCITE-4944 Project: Calcite Is

[jira] [Updated] (CALCITE-4737) Add RelOptPlanner visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4737: --- Summary: Add RelOptPlanner visualizer for debugging (was: Add Volcano visualizer for debug

[jira] [Created] (CALCITE-4947) Checkstyle fails on classes generated by Intellij when using option "build and run [tests] using Intellij IDEA"

Thomas Rebele created CALCITE-4947: -- Summary: Checkstyle fails on classes generated by Intellij when using option "build and run [tests] using Intellij IDEA" Key: CALCITE-4947 URL: https://issues.apache.org/jira/

[jira] [Commented] (CALCITE-4737) Add RelOptPlanner visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461368#comment-17461368 ] Thomas Rebele commented on CALCITE-4737: I've updated the PR to make it ready f

[jira] [Updated] (CALCITE-4947) Checkstyle fails on classes generated by Intellij when using option "build and run [tests] using Intellij IDEA"

[ https://issues.apache.org/jira/browse/CALCITE-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4947: --- Labels: pull-request-available (was: ) > Checkstyle fails on classes generated by Intellij

[jira] [Assigned] (CALCITE-4947) Checkstyle fails on classes generated by Intellij when using option "build and run [tests] using Intellij IDEA"

[ https://issues.apache.org/jira/browse/CALCITE-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele reassigned CALCITE-4947: -- Assignee: Thomas Rebele > Checkstyle fails on classes generated by Intellij when usi

[jira] [Commented] (CALCITE-4947) Checkstyle fails on classes generated by Intellij when using option "build and run [tests] using Intellij IDEA"

[ https://issues.apache.org/jira/browse/CALCITE-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463181#comment-17463181 ] Thomas Rebele commented on CALCITE-4947: [~vladimirsitnikov], when you have som

[jira] [Commented] (CALCITE-5001) Error for sql query with non-ascii characters with Oracle db

[ https://issues.apache.org/jira/browse/CALCITE-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488810#comment-17488810 ] Thomas Rebele commented on CALCITE-5001: Just a general comment: if you add a u

[jira] [Created] (CALCITE-5061) Improve recursive application of the field trimming

Thomas Rebele created CALCITE-5061: -- Summary: Improve recursive application of the field trimming Key: CALCITE-5061 URL: https://issues.apache.org/jira/browse/CALCITE-5061 Project: Calcite I

[jira] [Commented] (CALCITE-5061) Improve recursive application of the field trimming

[ https://issues.apache.org/jira/browse/CALCITE-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511305#comment-17511305 ] Thomas Rebele commented on CALCITE-5061: I've started on an alternative field t

[jira] [Commented] (CALCITE-5051) UNION query plan prevents projection push down

[ https://issues.apache.org/jira/browse/CALCITE-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511306#comment-17511306 ] Thomas Rebele commented on CALCITE-5051: I think the problem here is that RelFi

[jira] [Commented] (CALCITE-5061) Improve recursive application of the field trimming

[ https://issues.apache.org/jira/browse/CALCITE-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534476#comment-17534476 ] Thomas Rebele commented on CALCITE-5061: The problem with the RelFieldTrimmer i

[jira] [Comment Edited] (CALCITE-5061) Improve recursive application of the field trimming

[ https://issues.apache.org/jira/browse/CALCITE-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534476#comment-17534476 ] Thomas Rebele edited comment on CALCITE-5061 at 5/11/22 8:55 AM:

[jira] [Commented] (CALCITE-5061) Improve recursive application of the field trimming

[ https://issues.apache.org/jira/browse/CALCITE-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534778#comment-17534778 ] Thomas Rebele commented on CALCITE-5061: The proposed changes have been develop

[jira] [Updated] (CALCITE-5061) Improve recursive application of the field trimming

[ https://issues.apache.org/jira/browse/CALCITE-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-5061: --- Fix Version/s: (was: 1.31.0) > Improve recursive application of the field trimming > --

[jira] [Assigned] (CALCITE-5061) Improve recursive application of the field trimming

[ https://issues.apache.org/jira/browse/CALCITE-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele reassigned CALCITE-5061: -- Assignee: Ruben Q L (was: Thomas Rebele) > Improve recursive application of the fie

[jira] [Commented] (CALCITE-5277) Make EnumerableRelImplementor stashedParameters order deterministic to increase BINDABLE_CACHE hit rate

[ https://issues.apache.org/jira/browse/CALCITE-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602193#comment-17602193 ] Thomas Rebele commented on CALCITE-5277: The map itself is not part of the cach

[jira] [Comment Edited] (CALCITE-5277) Make EnumerableRelImplementor stashedParameters order deterministic to increase BINDABLE_CACHE hit rate

[ https://issues.apache.org/jira/browse/CALCITE-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602193#comment-17602193 ] Thomas Rebele edited comment on CALCITE-5277 at 9/9/22 10:07 AM:

[jira] [Created] (CALCITE-4264) The query planner should take CPU cost into account

Thomas Rebele created CALCITE-4264: -- Summary: The query planner should take CPU cost into account Key: CALCITE-4264 URL: https://issues.apache.org/jira/browse/CALCITE-4264 Project: Calcite I

[jira] [Commented] (CALCITE-4264) The query planner should take CPU cost into account

[ https://issues.apache.org/jira/browse/CALCITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203325#comment-17203325 ] Thomas Rebele commented on CALCITE-4264: I implemented the proposal and run the

[jira] [Comment Edited] (CALCITE-4264) The query planner should take CPU cost into account

[ https://issues.apache.org/jira/browse/CALCITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203325#comment-17203325 ] Thomas Rebele edited comment on CALCITE-4264 at 9/28/20, 4:04 PM: ---

[jira] [Created] (CALCITE-4404) Missing LogicalCorrelate when using FILTER_SUB_QUERY_TO_CORRELATE for nested subqueries

Thomas Rebele created CALCITE-4404: -- Summary: Missing LogicalCorrelate when using FILTER_SUB_QUERY_TO_CORRELATE for nested subqueries Key: CALCITE-4404 URL: https://issues.apache.org/jira/browse/CALCITE-4404

[jira] [Updated] (CALCITE-4404) Missing LogicalCorrelate when using FILTER_SUB_QUERY_TO_CORRELATE for nested subqueries

[ https://issues.apache.org/jira/browse/CALCITE-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4404: --- Attachment: Cte4404.java > Missing LogicalCorrelate when using FILTER_SUB_QUERY_TO_CORRELAT

[jira] [Commented] (CALCITE-4437) The Sort rel should be decorrelated even though it has fetch or limit when it is not inside a Correlate

[ https://issues.apache.org/jira/browse/CALCITE-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248935#comment-17248935 ] Thomas Rebele commented on CALCITE-4437: A workaround for the issue: add a para

[jira] [Comment Edited] (CALCITE-4437) The Sort rel should be decorrelated even though it has fetch or limit when it is not inside a Correlate

[ https://issues.apache.org/jira/browse/CALCITE-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248935#comment-17248935 ] Thomas Rebele edited comment on CALCITE-4437 at 12/14/20, 12:02 PM: -

[jira] [Comment Edited] (CALCITE-4437) The Sort rel should be decorrelated even though it has fetch or limit when it is not inside a Correlate

[ https://issues.apache.org/jira/browse/CALCITE-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248935#comment-17248935 ] Thomas Rebele edited comment on CALCITE-4437 at 12/14/20, 12:09 PM: -

[jira] [Commented] (CALCITE-4264) The query planner should take CPU cost into account

[ https://issues.apache.org/jira/browse/CALCITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250355#comment-17250355 ] Thomas Rebele commented on CALCITE-4264: The purpose of this ticket is just to

[jira] [Commented] (CALCITE-4432) When the RelNode's input is the same subset as the node belonged to, not choose this node as best.

[ https://issues.apache.org/jira/browse/CALCITE-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258108#comment-17258108 ] Thomas Rebele commented on CALCITE-4432: Would it be possible to add a check "i

[jira] [Created] (CALCITE-4530) EnumerableWindow.copy(...) should adapt the rowType

Thomas Rebele created CALCITE-4530: -- Summary: EnumerableWindow.copy(...) should adapt the rowType Key: CALCITE-4530 URL: https://issues.apache.org/jira/browse/CALCITE-4530 Project: Calcite I

[jira] [Updated] (CALCITE-4530) EnumerableWindow.copy(...) should adapt the rowType

[ https://issues.apache.org/jira/browse/CALCITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4530: --- Description: The method EnumerableWindow.copy(RelTraitSet, List) copies the row type. Howe

[jira] [Commented] (CALCITE-4530) EnumerableWindow.copy(...) should adapt the rowType

[ https://issues.apache.org/jira/browse/CALCITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299433#comment-17299433 ] Thomas Rebele commented on CALCITE-4530: Sorry for the imprecise wording. The o

[jira] [Updated] (CALCITE-4530) EnumerableWindow.copy(...) should adapt the rowType

[ https://issues.apache.org/jira/browse/CALCITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4530: --- Attachment: copy-methods-084d608.zip > EnumerableWindow.copy(...) should adapt the rowType

[jira] [Commented] (CALCITE-4530) EnumerableWindow.copy(...) should adapt the rowType

[ https://issues.apache.org/jira/browse/CALCITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302519#comment-17302519 ] Thomas Rebele commented on CALCITE-4530: I've had a look at the copy methods ([

[jira] [Created] (CALCITE-4540) The constructor of EnumerableWindow should be public

Thomas Rebele created CALCITE-4540: -- Summary: The constructor of EnumerableWindow should be public Key: CALCITE-4540 URL: https://issues.apache.org/jira/browse/CALCITE-4540 Project: Calcite

[jira] [Closed] (CALCITE-4530) EnumerableWindow.copy(...) should adapt the rowType

[ https://issues.apache.org/jira/browse/CALCITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele closed CALCITE-4530. -- Resolution: Won't Fix If the solution is to write custom code to fix the row type of the wind

[jira] [Created] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query with UNNEST to logical plan

Thomas Rebele created CALCITE-4680: -- Summary: AssertionError: contains $cor1, while converting SQL query with UNNEST to logical plan Key: CALCITE-4680 URL: https://issues.apache.org/jira/browse/CALCITE-4680

[jira] [Updated] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query with UNNEST to logical plan

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4680: --- Attachment: Calcite4680.java > AssertionError: contains $cor1, while converting SQL query w

[jira] [Updated] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query containing UNNEST to logical plan using subquery expansion

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4680: --- Summary: AssertionError: contains $cor1, while converting SQL query containing UNNEST to lo

[jira] [Commented] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query containing UNNEST to logical plan using subquery expansion

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376573#comment-17376573 ] Thomas Rebele commented on CALCITE-4680: Thank you, the problem goes away after

[jira] [Updated] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query containing UNNEST to logical plan using subquery expansion

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4680: --- Priority: Minor (was: Major) > AssertionError: contains $cor1, while converting SQL query

[jira] [Created] (CALCITE-4689) EnumerableUncollectRule causes an IllegalArgumentException: Type mismatch: the field sizes are not equal

Thomas Rebele created CALCITE-4689: -- Summary: EnumerableUncollectRule causes an IllegalArgumentException: Type mismatch: the field sizes are not equal Key: CALCITE-4689 URL: https://issues.apache.org/jira/browse/

[jira] [Updated] (CALCITE-4689) EnumerableUncollectRule causes an IllegalArgumentException: Type mismatch: the field sizes are not equal

[ https://issues.apache.org/jira/browse/CALCITE-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4689: --- Attachment: Calcite4689.java > EnumerableUncollectRule causes an IllegalArgumentException:

[jira] [Updated] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query containing UNNEST to logical plan using subquery expansion

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4680: --- Attachment: Calcite4680.java > AssertionError: contains $cor1, while converting SQL query c

[jira] [Updated] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query containing UNNEST to logical plan using subquery expansion

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4680: --- Attachment: (was: Calcite4680.java) > AssertionError: contains $cor1, while converting

[jira] [Commented] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query containing UNNEST to logical plan using subquery expansion

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378106#comment-17378106 ] Thomas Rebele commented on CALCITE-4680: The problem does not exist for the Qui

[jira] [Created] (CALCITE-4691) Incorrect handling of NOT IN and NULL values

Thomas Rebele created CALCITE-4691: -- Summary: Incorrect handling of NOT IN and NULL values Key: CALCITE-4691 URL: https://issues.apache.org/jira/browse/CALCITE-4691 Project: Calcite Issue Ty

[jira] [Updated] (CALCITE-4691) Incorrect handling of NOT IN and NULL values

[ https://issues.apache.org/jira/browse/CALCITE-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4691: --- Description: It seems that Calcite does not handle WHERE foo NOT IN (values) correctly, if

[jira] [Commented] (CALCITE-4737) Add Volcano visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398750#comment-17398750 ] Thomas Rebele commented on CALCITE-4737: Thanks for creating the ticket. There

[jira] [Assigned] (CALCITE-4689) EnumerableUncollectRule causes an IllegalArgumentException: Type mismatch: the field sizes are not equal

[ https://issues.apache.org/jira/browse/CALCITE-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele reassigned CALCITE-4689: -- Assignee: (was: Thomas Rebele) > EnumerableUncollectRule causes an IllegalArgume

[jira] [Assigned] (CALCITE-4689) EnumerableUncollectRule causes an IllegalArgumentException: Type mismatch: the field sizes are not equal

[ https://issues.apache.org/jira/browse/CALCITE-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele reassigned CALCITE-4689: -- Assignee: Thomas Rebele > EnumerableUncollectRule causes an IllegalArgumentException

[jira] [Commented] (CALCITE-4737) Add Volcano visualizer for debugging

[ https://issues.apache.org/jira/browse/CALCITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421567#comment-17421567 ] Thomas Rebele commented on CALCITE-4737: I made some fixes and improvements to

[jira] [Created] (CALCITE-4848) Adding a HAVING condition to a query with a dynamic parameter makes the result empty

Thomas Rebele created CALCITE-4848: -- Summary: Adding a HAVING condition to a query with a dynamic parameter makes the result empty Key: CALCITE-4848 URL: https://issues.apache.org/jira/browse/CALCITE-4848

[jira] [Updated] (CALCITE-4848) Adding a HAVING condition to a query with a dynamic parameter makes the result empty

[ https://issues.apache.org/jira/browse/CALCITE-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4848: --- Attachment: CALCITE-4848.patch > Adding a HAVING condition to a query with a dynamic parame

[jira] [Commented] (CALCITE-4848) Adding a HAVING condition to a query with a dynamic parameter makes the result empty

[ https://issues.apache.org/jira/browse/CALCITE-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427770#comment-17427770 ] Thomas Rebele commented on CALCITE-4848: I've debugged this a bit: In the HEP p

[jira] [Assigned] (CALCITE-4848) Adding a HAVING condition to a query with a dynamic parameter makes the result empty

[ https://issues.apache.org/jira/browse/CALCITE-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele reassigned CALCITE-4848: -- Assignee: Thomas Rebele > Adding a HAVING condition to a query with a dynamic parame

[jira] [Updated] (CALCITE-4848) Adding a HAVING condition to a query with a dynamic parameter makes the result always empty

[ https://issues.apache.org/jira/browse/CALCITE-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4848: --- Summary: Adding a HAVING condition to a query with a dynamic parameter makes the result alw

[jira] [Created] (CALCITE-3977) RelDecorrelator produces incorrect plans if the input plan contains field accesses

Thomas Rebele created CALCITE-3977: -- Summary: RelDecorrelator produces incorrect plans if the input plan contains field accesses Key: CALCITE-3977 URL: https://issues.apache.org/jira/browse/CALCITE-3977

[jira] [Updated] (CALCITE-3977) RelDecorrelator produces incorrect plans if the input plan contains field accesses

[ https://issues.apache.org/jira/browse/CALCITE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3977: --- Attachment: (was: Calcite3977.java) > RelDecorrelator produces incorrect plans if the i

[jira] [Updated] (CALCITE-3977) RelDecorrelator produces incorrect plans if the input plan contains field accesses

[ https://issues.apache.org/jira/browse/CALCITE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3977: --- Attachment: Calcite3977.java > RelDecorrelator produces incorrect plans if the input plan c

[jira] [Updated] (CALCITE-3977) RelDecorrelator produces incorrect plans if the input plan contains field accesses

[ https://issues.apache.org/jira/browse/CALCITE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3977: --- Attachment: Calcite3977.java > RelDecorrelator produces incorrect plans if the input plan c

[jira] [Updated] (CALCITE-3977) RelDecorrelator does not resolve correlation variable with field accesses

[ https://issues.apache.org/jira/browse/CALCITE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3977: --- Summary: RelDecorrelator does not resolve correlation variable with field accesses (was: R

[jira] [Created] (CALCITE-3978) RelDecorrelator on a plan with field accesses does not update field indices when adding a projection

Thomas Rebele created CALCITE-3978: -- Summary: RelDecorrelator on a plan with field accesses does not update field indices when adding a projection Key: CALCITE-3978 URL: https://issues.apache.org/jira/browse/CALC

[jira] [Updated] (CALCITE-3978) RelDecorrelator on a plan with field accesses does not update field indices when adding a projection

[ https://issues.apache.org/jira/browse/CALCITE-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3978: --- Attachment: Calcite3978.java > RelDecorrelator on a plan with field accesses does not updat

[jira] [Updated] (CALCITE-3978) RelDecorrelator on a plan with field accesses does not update field indices when adding a projection

[ https://issues.apache.org/jira/browse/CALCITE-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3978: --- Affects Version/s: 1.22.0 > RelDecorrelator on a plan with field accesses does not update f

[jira] [Commented] (CALCITE-3978) RelDecorrelator on a plan with field accesses does not update field indices when adding a projection

[ https://issues.apache.org/jira/browse/CALCITE-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101779#comment-17101779 ] Thomas Rebele commented on CALCITE-3978: A workaround for this issue would be t

[jira] [Commented] (CALCITE-3977) RelDecorrelator does not resolve correlation variable with field accesses

[ https://issues.apache.org/jira/browse/CALCITE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102477#comment-17102477 ] Thomas Rebele commented on CALCITE-3977: The original plan is a simplified vers

[jira] [Commented] (CALCITE-3977) RelDecorrelator does not resolve correlation variable with field accesses

[ https://issues.apache.org/jira/browse/CALCITE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104194#comment-17104194 ] Thomas Rebele commented on CALCITE-3977: Indeed, good point. I've added b.field

[jira] [Commented] (CALCITE-3094) Code of method grows beyond 64 KB

[ https://issues.apache.org/jira/browse/CALCITE-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118612#comment-17118612 ] Thomas Rebele commented on CALCITE-3094: In this particular case the problem se

[jira] [Updated] (CALCITE-3094) Code of method grows beyond 64 KB

[ https://issues.apache.org/jira/browse/CALCITE-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3094: --- Attachment: CTE-3094.zip > Code of method grows beyond 64 KB >

[jira] [Commented] (CALCITE-3094) Code of method grows beyond 64 KB

[ https://issues.apache.org/jira/browse/CALCITE-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140508#comment-17140508 ] Thomas Rebele commented on CALCITE-3094: I would not apply a transformation to

[jira] [Commented] (CALCITE-3920) Improve ORDER BY computation in Enumerable convention by exploiting LIMIT

[ https://issues.apache.org/jira/browse/CALCITE-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144822#comment-17144822 ] Thomas Rebele commented on CALCITE-3920: If no one has started to work on it ye

[jira] [Assigned] (CALCITE-3094) Code of method grows beyond 64 KB

[ https://issues.apache.org/jira/browse/CALCITE-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele reassigned CALCITE-3094: -- Assignee: Thomas Rebele > Code of method grows beyond 64 KB > --

[jira] [Updated] (CALCITE-3094) Code of method grows beyond 64 KB when joining two tables with many fields

[ https://issues.apache.org/jira/browse/CALCITE-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3094: --- Summary: Code of method grows beyond 64 KB when joining two tables with many fields (was:

[jira] [Commented] (CALCITE-3094) Code of method grows beyond 64 KB when joining two tables with many fields

[ https://issues.apache.org/jira/browse/CALCITE-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150302#comment-17150302 ] Thomas Rebele commented on CALCITE-3094: I've implemented a WIP draft of my pro

[jira] [Updated] (CALCITE-3920) Improve ORDER BY computation in Enumerable convention by exploiting LIMIT

[ https://issues.apache.org/jira/browse/CALCITE-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-3920: --- Labels: pull-requests-available (was: pull-request-available) > Improve ORDER BY computati

[jira] [Commented] (CALCITE-3920) Improve ORDER BY computation in Enumerable convention by exploiting LIMIT

[ https://issues.apache.org/jira/browse/CALCITE-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168140#comment-17168140 ] Thomas Rebele commented on CALCITE-3920: [~zabetak] had mentioned the benchmark

[jira] [Commented] (CALCITE-3920) Improve ORDER BY computation in Enumerable convention by exploiting LIMIT

[ https://issues.apache.org/jira/browse/CALCITE-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170101#comment-17170101 ] Thomas Rebele commented on CALCITE-3920: Unfortunately priorityQueue:stableSort

[jira] [Created] (CALCITE-4157) Use a different sort algorithm for EnumerableDefaults.orderBy(...)

Thomas Rebele created CALCITE-4157: -- Summary: Use a different sort algorithm for EnumerableDefaults.orderBy(...) Key: CALCITE-4157 URL: https://issues.apache.org/jira/browse/CALCITE-4157 Project: Cal

[jira] [Updated] (CALCITE-4157) Use a different sort algorithm for EnumerableDefaults.orderBy(...)

[ https://issues.apache.org/jira/browse/CALCITE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4157: --- Description: As shown by [the benchmarks|https://github.com/thomasrebele/jmh-micro-benchma

[jira] [Commented] (CALCITE-4157) Use a different sort algorithm for EnumerableDefaults.orderBy(...)

[ https://issues.apache.org/jira/browse/CALCITE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172122#comment-17172122 ] Thomas Rebele commented on CALCITE-4157: Thanks for your comments. Indeed, that

[jira] [Commented] (CALCITE-4157) Use a different sort algorithm for EnumerableDefaults.orderBy(...)

[ https://issues.apache.org/jira/browse/CALCITE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175349#comment-17175349 ] Thomas Rebele commented on CALCITE-4157: I haven't thought about an important p

[jira] [Commented] (CALCITE-3920) Improve ORDER BY computation in Enumerable convention by exploiting LIMIT

[ https://issues.apache.org/jira/browse/CALCITE-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175363#comment-17175363 ] Thomas Rebele commented on CALCITE-3920: Thank you for all your feedback. I fou

[jira] [Created] (CALCITE-4189) Simplify 'X OR IS NOT TRUE X' to 'TRUE'

Thomas Rebele created CALCITE-4189: -- Summary: Simplify 'X OR IS NOT TRUE X' to 'TRUE' Key: CALCITE-4189 URL: https://issues.apache.org/jira/browse/CALCITE-4189 Project: Calcite Issue Type: I

[jira] [Updated] (CALCITE-4189) Simplify 'P OR P IS NOT TRUE' to 'TRUE'

[ https://issues.apache.org/jira/browse/CALCITE-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4189: --- Summary: Simplify 'P OR P IS NOT TRUE' to 'TRUE' (was: Simplify 'X OR IS NOT TRUE X' to 'T

[jira] [Updated] (CALCITE-4189) Simplify 'P OR P IS NOT TRUE' to 'TRUE'

[ https://issues.apache.org/jira/browse/CALCITE-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4189: --- Description: Statements of the form 'P OR P IS NOT TRUE' to 'TRUE' should always be true (

[jira] [Commented] (CALCITE-4189) Simplify 'P OR P IS NOT TRUE' to 'TRUE'

[ https://issues.apache.org/jira/browse/CALCITE-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181948#comment-17181948 ] Thomas Rebele commented on CALCITE-4189: Thanks for spotting, fixed. > Simplif

[jira] [Created] (CALCITE-4256) RexSimplify should not simplify P AND P to P, if it contains a call to RAND or RAND_INTEGER

Thomas Rebele created CALCITE-4256: -- Summary: RexSimplify should not simplify P AND P to P, if it contains a call to RAND or RAND_INTEGER Key: CALCITE-4256 URL: https://issues.apache.org/jira/browse/CALCITE-4256

[jira] [Commented] (CALCITE-4256) RexSimplify should not simplify P AND P to P, if it contains a call to RAND or RAND_INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195960#comment-17195960 ] Thomas Rebele commented on CALCITE-4256: The function RexUtil#flattenAnd remove

[jira] [Commented] (CALCITE-4256) RexSimplify should not simplify P AND P to P, if it contains a call to RAND or RAND_INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196863#comment-17196863 ] Thomas Rebele commented on CALCITE-4256: Personally, if I write a query with RA

[jira] [Commented] (CALCITE-4189) Simplify 'P OR P IS NOT TRUE' to 'TRUE'

[ https://issues.apache.org/jira/browse/CALCITE-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197045#comment-17197045 ] Thomas Rebele commented on CALCITE-4189: A similar optimization is done for AND

[jira] [Commented] (CALCITE-2959) Support collation on struct fields

[ https://issues.apache.org/jira/browse/CALCITE-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676025#comment-17676025 ] Thomas Rebele commented on CALCITE-2959: Maybe the {{EnhancedScan}} could outpu

[jira] [Commented] (CALCITE-4021) EnumerableUnion should preserve ordering when all inputs have the same collation

[ https://issues.apache.org/jira/browse/CALCITE-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676026#comment-17676026 ] Thomas Rebele commented on CALCITE-4021: I agree with [~julianhyde], and propos

[jira] [Created] (CALCITE-5470) VolcanoPlanner removes a necessary sort

Thomas Rebele created CALCITE-5470: -- Summary: VolcanoPlanner removes a necessary sort Key: CALCITE-5470 URL: https://issues.apache.org/jira/browse/CALCITE-5470 Project: Calcite Issue Type: B

[jira] [Updated] (CALCITE-5470) VolcanoPlanner removes a necessary sort

[ https://issues.apache.org/jira/browse/CALCITE-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-5470: --- Attachment: sqlline.log > VolcanoPlanner removes a necessary sort > ---

[jira] [Updated] (CALCITE-5470) VolcanoPlanner removes a necessary sort

[ https://issues.apache.org/jira/browse/CALCITE-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-5470: --- Description: A logical plan that roughly corresponds to SELECT a*a FROM (VALUES(-10),(2),(

  1   2   >