[
https://issues.apache.org/jira/browse/UNOMI-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255556#comment-16255556
]
Romain Gauthier commented on UNOMI-139:
---------------------------------------
Hi Don,
There are definitely use cases to make unomi multitenant. I'm not sure though
if we should use the existing "scope" identifier or if a super scope should be
added.
With the use cases that we want to address, we would scope profiles, sessions,
events but we also need to find a way to scope properties, tags and any data
structure change that could be done via the API...
Regarding security and permissions, maybe the unomi key could be leveraged.
When using multiple Unomi, are you using the same ElasticSearch cluster with
different indexes ? Is this working well or did it come up with some challenges
?
Best,
Romain
> Isolate Profiles By Client
> --------------------------
>
> Key: UNOMI-139
> URL: https://issues.apache.org/jira/browse/UNOMI-139
> Project: Apache Unomi
> Issue Type: Improvement
> Reporter: Don Hinshaw
>
> Is there a use case for data from multiple clients on the same Unomi instance?
> How can we isolate profiles by a value in the event or session (like scope)
> so that a profile from one client's event is not merged with a profile from
> another.
> At the moment we are using multiple instances of Unomi.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
