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

Redundant elastic indexing for multiple users using the same datasource? #66

Closed
kixxalot opened this issue Mar 27, 2019 · 2 comments
Closed
Assignees
Labels
question Further information is requested

Comments

@kixxalot
Copy link

This is not a bug, more of a question.

Currently it seems that in case of multiple users using the same datasource, every user is required to start elastic indexing, and a duplicate elastic index is made for each user.

Just wondering if my understanding of this is correct. And if so: is this really necessary? Will this not potentially cause huge storage space requirements when dealing with a large group of users?

@robfrank robfrank added the question Further information is requested label Mar 27, 2019
@robfrank robfrank self-assigned this Mar 27, 2019
@robfrank
Copy link
Contributor

Yes, you understand correctly. Each user has its own indexes over the same data source.
Our first deployment was our SAAS service, so each customer usually had its own data sources.
We didn't put our effort on deduplication of indexes as we focused more on connectors and operativity.

What are you working on?
If you don't want to share (and I guess you don't want, due to your anonymous profile) with the public feel free to drop me an email.

@kixxalot
Copy link
Author

Just sent you an email.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants