-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Add documentation for history based optimizer #21830
Comments
A list of optimizations:
CC: @mlyublena |
@feilong-liu is working on adding documentation. |
Just drafted a doc on HBO, since it's mainly for Presto user, hence I skip the technical details, but focus on the brief description of the supported optimizers and associated session properties to turn them on. https://docs.google.com/document/d/1Y6ylfV4yfbJ5X5lQwG5gTiC5nSVyV0QoyP0VLyJfLME/edit?usp=sharing @steveburnett Hi Steve, I know that you are working on Presto documentation, wonder if you could help to polish the draft before adding it to the documentation (and share a email account so that I can assign edit access to you or copy it into another doc whichever works better for you). Thanks! |
@feilong-liu I would be happy to help! I see that you've already received some good feedback on the draft in your link. You can use the email address attached to my GitHub profile if you like. |
Hi @steveburnett, thanks for helping with it. I've addressed the comments and added you as editor of the doc. |
Hi @feilong-liu! I'm sorry I took longer than I expected to get to this, but I just completed a light edit of the draft - light mostly because it's an excellent draft, especially after you've already addressed the other reviewers' technical recommendations. |
Many prominent improvements are being added to the history based optimizer. We already have documentation for the Redis HBO provider, yet lack documentation for how HBO works and how to enable it. We should add this documentation to encourage its use.
It seems like this should be added to the query optimizer section.
CC: @pranjalssh @mlyublena @feilong-liu @jaystarshot
The text was updated successfully, but these errors were encountered: