benmayersohn opened a new issue, #50186:
URL: https://github.com/apache/doris/issues/50186

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Version
   
   doris-3.0.4-rc02
   
   ### What's Wrong?
   
   In the documentation there is mention of the API endpoint 
[colocate/bucketseq](https://doris.apache.org/docs/3.0/query-acceleration/colocation-join?_highlight=bucketseq#http-restful-api)
 for assigning backend IDs to buckets in a particular colocation group, but it 
appears from the code that this is not implemented: 
https://github.com/apache/doris/blob/a2552b0add3af2bf0453553d72c9fed0960a7296/fe/fe-core/src/main/java/org/apache/doris/httpv2/meta/ColocateMetaService.java#L174
   
   I think the documentation should mention this, as I've been trying to fix 
some colocation tables that are tied to dead backends and therefore unstable 
and went down that rabbit hole to no avail. I ended up just altering the tables 
and giving the corresponding colocation groups a new name, and that seems to do 
the trick.
   
   
   ### What You Expected?
   
   To be informed that this route doesn't work, or for the route to actually 
work as intended.
   
   ### How to Reproduce?
   
   Described above
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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