-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Tracking issue for Cardinality Estimation Enhancement #26085
Comments
/sig planner |
May I have a try? |
Thank you for that. |
@time-and-fate is there a design document or pre-RFC? We may avoid discuss privately if unnecessary. |
Here are two simple discussion documents about these in this issue: https://docs.google.com/document/d/1IyxlOJAQY-lFpcId0nRJy4aVgm4Be1K5CUESsqSZNWk/edit?usp=sharing, https://docs.google.com/document/d/16sn1aoTfzQXBWR3QAztTpu-JnIzg8r23lMkRT8ua4Ck/edit?usp=sharing. |
@time-and-fate @qw4990 is there any ongoing issues? If all subtasks closed, it should be a conclusion about the status of the tracking issue. I'd like to ask for a design document or brief description about this "enhancement". Otherwise we implement feature secretly and hard to trace back even by ourselves. |
The tasks for this staged have been completed and the design docs are contained in the links above. |
@time-and-fate the document above is private to PingCAP company. I'd prefer to see a brief description public in this PR or as a design document. |
Close since all tasks have been finished. |
Enhancement
We're investigating flaws in our cardinality estimation logic and trying to fix them. And we're also trying to improve our cardinality estimation mechanism. This issue is for tracking the developments.
NDV
andcardinality
in the optimizer #26283The text was updated successfully, but these errors were encountered: