Skip to content
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

Data Index EXPLAIN plan #487

Open
tripott opened this issue Mar 30, 2022 · 0 comments
Open

Data Index EXPLAIN plan #487

tripott opened this issue Mar 30, 2022 · 0 comments

Comments

@tripott
Copy link
Contributor

tripott commented Mar 30, 2022

Use Case

As a developer building on top of the hyper cloud and trying to debug performance issues with our indexes
I want to utilize an EXPLAIN endpoint within the data API
so that I can make sure that the indexes we expect are being used are actually being used.

Notes

Requested by Travis Nesland.

Tom: I think a explain feature is a valid request and I believe many databases support an explain feature, I think we would need to be able to support a not implemented response as well for adapter implementers

Tyler: I agree with that. There are cases where an adapter might not implement an explain ie. sqlite adapter or something to that effect. Seems like the sort of thing that would be documented as a convention, then maybe a pre-canned util for adapter devs to use ie. NotImplementedHyperErr() or something.

@TillaTheHun0 TillaTheHun0 moved this to 🆕 New in Public Board Mar 2, 2023
@TillaTheHun0 TillaTheHun0 moved this from 🆕 New to 📋 Backlog in Public Board Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant