You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/10/03 03:49:56 UTC
[GitHub] [shardingsphere] wgy8283335 opened a new issue #12894: Rel node tree is different between join
wgy8283335 opened a new issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894
## Feature Request
**For English only**, other languages will not accept.
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will **close it**.
Please answer these questions before submitting your issue. Thanks!
### Is your feature request related to a problem?
### Describe the feature you would like.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] wgy8283335 edited a comment on issue #12894: Rel node tree should not be different between cross join and cross where
Posted by GitBox <gi...@apache.org>.
wgy8283335 edited a comment on issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894#issuecomment-932857834
Solution:
1. Compare with the test result of the same SQL in the calcite project. Find out the test in the calcite project, and write unit test in ss according to the result of the test in calcite.
2. find the difference in the optimization process between 'join' and 'where', in the trace log. Trace log is really worth read to understand the process of optimization.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] wgy8283335 edited a comment on issue #12894: Rel node tree should not be different between cross join and cross where
Posted by GitBox <gi...@apache.org>.
wgy8283335 edited a comment on issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894#issuecomment-932857834
Solution method:
1. Compare with the test result of the same SQL in the calcite project. Find out the test in the calcite project, and write unit test in ss according to the result of the test in calcite.
2. find the difference in the optimization process between 'join' and 'where', in the trace log. Trace log is really worth read to understand the process of optimization.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] wgy8283335 edited a comment on issue #12894: Rel node tree should not be different between cross join and cross where
Posted by GitBox <gi...@apache.org>.
wgy8283335 edited a comment on issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894#issuecomment-932857834
Solution:
1. Find the difference in the optimization process between 'join' and 'where', in the trace log. Trace log is really worth read to understand the process of optimization. '[CAST($0): VARCHAR]' this may cause the difference, try different rules to pull this expression from 'where' to 'join'.
2. Make the SQL node to be the same before optimize.
3. Compare with the test result of the same SQL in the calcite project. Find out the test in the calcite project, and write unit test in ss according to the result of the test in calcite.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] wgy8283335 commented on issue #12894: Rel node tree is different between join
Posted by GitBox <gi...@apache.org>.
wgy8283335 commented on issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894#issuecomment-932857834
Solution method:
1. find the difference in the optimization process.
2. Compare with the test result in calcite project.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] wgy8283335 edited a comment on issue #12894: Rel node tree should not be different between cross join and cross where
Posted by GitBox <gi...@apache.org>.
wgy8283335 edited a comment on issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894#issuecomment-932857834
Solution method:
1. Compare with the test result in calcite project for the same sql.
2. find the difference in the optimization process between join and where, in trace log.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] wgy8283335 edited a comment on issue #12894: Rel node tree should not be different between cross join and cross where
Posted by GitBox <gi...@apache.org>.
wgy8283335 edited a comment on issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894#issuecomment-932857834
Solution method:
1. Compare with the test result of the same sql in calcite project.
2. find the difference in the optimization process between join and where, in trace log.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] wgy8283335 edited a comment on issue #12894: Rel node tree should not be different between cross join and cross where
Posted by GitBox <gi...@apache.org>.
wgy8283335 edited a comment on issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894#issuecomment-932857834
Solution:
1. Find the difference in the optimization process between 'join' and 'where', in the trace log. Trace log is really worth read to understand the process of optimization. '[CAST($0): VARCHAR]' this may cause the difference, try different rules to pull this expression from 'where' to 'join'.
2. Compare with the test result of the same SQL in the calcite project. Find out the test in the calcite project, and write unit test in ss according to the result of the test in calcite.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] wgy8283335 edited a comment on issue #12894: Rel node tree should not be different between cross join and cross where
Posted by GitBox <gi...@apache.org>.
wgy8283335 edited a comment on issue #12894:
URL: https://github.com/apache/shardingsphere/issues/12894#issuecomment-932857834
Solution:
1. Find the difference in the optimization process between 'join' and 'where', in the trace log. Trace log is really worth read to understand the process of optimization. '[CAST($0):VARCHAR]' this may cause the difference, try different rules to pull this expression up to join.
2. Compare with the test result of the same SQL in the calcite project. Find out the test in the calcite project, and write unit test in ss according to the result of the test in calcite.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org