-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](mtmv)Fix the old version of the materialized view error 'Current database is not set'` #42152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
run buildall |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
seawinde
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…t database is not set'` (apache#42152) cause by: apache#36543 after apache#36543,not need set db&catalog in `ConnectContext`, because query sql Because the query statement was rewritten to the full path (ctl.db. table. col) during creation, but query sql of old materialized view not was rewritten, so need set db&catalog in `ConnectContext`
…t database is not set'` (apache#42152) cause by: apache#36543 after apache#36543,not need set db&catalog in `ConnectContext`, because query sql Because the query statement was rewritten to the full path (ctl.db. table. col) during creation, but query sql of old materialized view not was rewritten, so need set db&catalog in `ConnectContext`
cause by: #36543
after 36543,not need set db&catalog in
ConnectContext, because query sql Because the query statement was rewritten to the full path (ctl.db. table. col) during creation,but query sql of old materialized view not was rewritten, so need set db&catalog in
ConnectContext