Re: [Architecture] Support Efficient Cross Tenant Analytics in DAS

We need to solve this. IMO this is not an edge case scenario at all. I would say every MT scenario will require cross tenant analytics ... in our platform architecture tenants are meant to be close to each other as in they run the same software on top; thus cross tenant analytics are always

Re: [Architecture] Support Efficient Cross Tenant Analytics in DAS

Use case come from IoT and APIM, and may be others. And it will be a common use case due to our cloud. On Thu, Mar 31, 2016 at 3:55 PM, Anjana Fernando wrote: > Hi Srinath, > > I'm not sure if this is something we would have to "fix". It was a clear > design decision we took in

Re: [Architecture] Support Efficient Cross Tenant Analytics in DAS

Hi, Having to run spark queries for each tenant can be very expensive with large number of tenants, but in terms of data isolation current design is better I believe. If we can come up with a good to design for supporting tenant level data isolation, this is something we can do indeed. However,

Re: [Architecture] Support Efficient Cross Tenant Analytics in DAS

Hi Srinath, I'm not sure if this is something we would have to "fix". It was a clear design decision we took in order to isolate the tenant data, in order for others not to access other tenant's data. So also in Spark virtual tables, it will directly map to their own analytics tables. If we

[Architecture] Support Efficient Cross Tenant Analytics in DAS

Hi Anjana, Currently we keep different Hbase/ RDBMS table per tenant. In multi-tenant, environment, this is very expensive as we will have to run a query per tenant. How can we fix this? e.g. if we keep tenant as field in the table, that let us do a "group by". --Srinath --