Skip to content
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

branch-2.1: [Fix](nereids) fix create view and alter view using old parser checking #43263 #44456

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

github-actions[bot]
Copy link
Contributor

Cherry-picked from #43263

…ng (#43263)

Problem:
Creating a view on a table with materialized views (MV) results in an
error: failed to init view stmt. For example, executing the following
SQL:
create view v1 as select * from t1 index t_mv_mv.

Root Cause:
The syntax index t_mv_mv is supported only by the new planner and not by
the old planner. During the view creation process, regardless of whether
the new or old optimizer is used, the process eventually calls the
createView method in Env. In the createView method, the persisted SQL of
the view is parsed using the old optimizer's parser. If the parsing
fails, an error is thrown.
As a result, if the SQL for creating a view includes syntax supported
only by the new optimizer, an error occurs.

Solution:
This PR addresses the issue by removing the parsing check from the
createView method in Env. Instead, the check is moved to the respective
classes responsible for creating views in the new and old optimizers.
@doris-robot
Copy link

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Nov 22, 2024
@doris-robot
Copy link

run buildall

@feiniaofeiafei
Copy link
Contributor

run feut

@feiniaofeiafei
Copy link
Contributor

run external

1 similar comment
@feiniaofeiafei
Copy link
Contributor

run external

@morrySnow morrySnow merged commit b07ea89 into branch-2.1 Nov 27, 2024
21 of 22 checks passed
@morrySnow morrySnow deleted the auto-pick-43263-branch-2.1 branch November 27, 2024 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants