xinghuayu007 opened a new pull request #6022:
URL: https://github.com/apache/incubator-doris/pull/6022


   ## Proposed changes
   
   Currently, after alter task finished, it only validate meta data of new 
tablet. It is also better to validate data file of new tablet. Because we found 
some tablet with beta format meta data, but alpha storage data after some bugs 
of alter operation. Look at the pic.
   
   ![10 136 22 47 8040 api meta header 511088487 
1278488007](https://user-images.githubusercontent.com/12771191/121687976-87dae500-caf5-11eb-92f6-4b6219da5ffb.png)
   ![小米办公  6 
](https://user-images.githubusercontent.com/12771191/121687986-8a3d3f00-caf5-11eb-9ab0-040e623c29d8.png)
    
   
   ## Types of changes
   
   What types of changes does your code introduce to Doris?
   _Put an `x` in the boxes that apply_
   
   - [ ] Bugfix (non-breaking change which fixes an issue)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to not work as expected)
   - [ ] Documentation Update (if none of the other choices apply)
   - [ ] Code refactor (Modify the code structure, format the code, etc...)
   
   ## Checklist
   
   _Put an `x` in the boxes that apply. You can also fill these out after 
creating the PR. If you're unsure about any of them, don't hesitate to ask. 
We're here to help! This is simply a reminder of what we are going to look for 
before merging your code._
   
   - [ ] I have created an issue on (Fix #ISSUE) and described the bug/feature 
there in detail
   - [ ] Compiling and unit tests pass locally with my changes
   - [ ] I have added tests that prove my fix is effective or that my feature 
works
   - [ ] If these changes need document changes, I have updated the document
   - [ ] Any dependent changes have been merged
   
   ## Further comments
   
   If this is a relatively large or complex change, kick off the discussion at 
d...@doris.apache.org 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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to