You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: