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.

Sign up for GitHub

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

Jump to bottom

Secondary indexes #3

Open
alexberriman opened this issue Jul 12, 2022 · 0 comments
Open

Secondary indexes #3

alexberriman opened this issue Jul 12, 2022 · 0 comments
Assignees
@alexberriman
Labels
backlog Issues that are marked to be worked on enhancement New feature or request
Milestone
v1.0

Comments

@alexberriman
Copy link
Owner

alexberriman commented Jul 12, 2022 •
edited
Loading

Currently, an index is only created for the primary key of a collection. That means for every other query where the primary key is not included, the entire collection has to be scanned. If you were able to configure multiple secondary indexes, read operations could reference the hash table as opposed to scanning the linked list.
@alexberriman alexberriman added enhancement New feature or request backlog Issues that are marked to be worked on labels Jul 12, 2022
@alexberriman alexberriman self-assigned this Jul 12, 2022
@alexberriman alexberriman added this to the v1.0 milestone Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexberriman alexberriman

Labels
backlog Issues that are marked to be worked on enhancement New feature or request
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
1 participant
@alexberriman