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

Usability improvements for secondary indices. #7081

Open
alexey-milovidov opened this issue Sep 24, 2019 · 3 comments
Open

Usability improvements for secondary indices. #7081

alexey-milovidov opened this issue Sep 24, 2019 · 3 comments
Labels
comp-skipidx Data skipping indices usability

Comments

@alexey-milovidov
Copy link
Member

Use case
People usually create indices of type set with unlimited size. It will lead to troubles.
Other common mistake is to specify high GRANULARITY of secondary index.

Describe the solution you'd like

  1. set(0) should be default value from merge-tree setting (for example, 100).
  2. If GRANULARITY of secondary index is greater than some merge-tree setting (for example, 1000), throw an exception.

Always allow to ATTACH table.

@filimonov filimonov added the comp-skipidx Data skipping indices label Sep 25, 2019
@zhang2014
Copy link
Contributor

For different indexes: set different default values for granularity may also be helpful?

@alexey-milovidov
Copy link
Member Author

For different indexes: set different default values for granularity may also be helpful?

Usually granularity 1 is enough and bigger value is considered as fine-tuning.

@tobia
Copy link

tobia commented Jun 29, 2020

Why does set(0) lead to trouble?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-skipidx Data skipping indices usability
Projects
None yet
Development

No branches or pull requests

4 participants