BiteTheDDDDt opened a new pull request, #18629:
URL: https://github.com/apache/doris/pull/18629

   # Proposed changes
   In the past doris, we have **rollup** and **materialized view**, which are 
fully synchronized with the base table and can be used to speed up the query.
   In the new version, we have introduced **multiple table materialized view**, 
which can be directly queried and cannot accelerate the query of the base 
table. Its positioning is more like a **view**, while the rollup/mv in the old 
version is more like an **index**.
   In order to clarify their design positioning, I renamed materialized view to 
materialized index in this pr. Since then, doris supports syntax like create 
materialized index, but the old syntax is still supported.
   This pr mainly made the following changes:
   1. Added materialized-index related syntax support
   2. Change materialized-view in related documents to materialized-index
   3. Change the case in the related test (feut/regression-test) to 
materialized-index
   
   ## Problem summary
   
   Describe your changes.
   
   ## Checklist(Required)
   
   * [ ] Does it affect the original behavior
   * [ ] Has unit tests been added
   * [ ] Has document been added or modified
   * [ ] Does it need to update dependencies
   * [ ] Is this PR support rollback (If NO, please explain WHY)
   
   ## Further comments
   
   If this is a relatively large or complex change, kick off the discussion at 
[[email protected]](mailto:[email protected]) by explaining why you 
chose the solution you did and what alternatives you considered, etc...
   
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to