Skip to content
This repository has been archived by the owner on Aug 13, 2019. It is now read-only.

Label Values composite index #26

Closed
gouthamve opened this issue Mar 29, 2017 · 7 comments
Closed

Label Values composite index #26

gouthamve opened this issue Mar 29, 2017 · 7 comments

Comments

@gouthamve
Copy link
Collaborator

I see from this doc that we are going to have composite indexes. But it is still un-implemented.

@fabxc I am assuming this is a TODO item and you have not dropped the idea of a composite index.

@fabxc
Copy link
Contributor

fabxc commented Mar 29, 2017 via email

@krasi-georgiev
Copy link
Contributor

@fabxc , @gouthamve
having red the issue description briefly this is still in need to be implemented right?
just so I know how to label the issue.

@codesome
Copy link
Contributor

@krasi-georgiev I was about to implement this in my GSoC. But as there were not many use cases with this, it was decided that we don't implement it for now.

@krasi-georgiev
Copy link
Contributor

yeah that is what I wanted to know.
Autocompletion sounds very useful so really surprising why it didn't get more interest.

@gouthamve
Copy link
Collaborator Author

Well, there was no use-case for this. Current APIs also allow for autocompletion but this was supposed to make it more efficient.

This means hardcoding what to autocomplete against and the current implementations were fast enough to not require this optimisation.

@krasi-georgiev
Copy link
Contributor

krasi-georgiev commented Aug 31, 2018

so in summary

  1. what we have works well enough
  2. there isn't any immediate demand for this

Seems we close this for now and revisit if needed?

@gouthamve
Copy link
Collaborator Author

Yes. Also @codesome has a branch somewhere that does this, I think (:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants