phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Levine (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1204) Unclear multi tenancy docs
Date Tue, 26 Aug 2014 17:46:00 GMT


Eli Levine commented on PHOENIX-1204:

Ah, I see what you mean. Yes, this is somewhat of an undocumented (and frankly unintended
IMHO) feature that allows tenant-specific connections to use multi-tenant tables directly.
My first impulse was to change the behavior to disallow multi-tenant tables to be visible
to tenant-specific connections. Thinking about this some more, however, it seems it might
be useful to allow users to interact with multi-tenant tables directly. The only thing they
would not be taking advantage of is tenant-specific metadata, like columns. If users don't
need tenant-specific columns they don't need to create tenant-specific tables and can work
with multi-tenant tables directly.

Unless there is disagreement, I am going to leave current behavior as is and doc it.

[~jamestaylor], do you have any thoughts on this?

> Unclear multi tenancy docs
> --------------------------
>                 Key: PHOENIX-1204
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.0.0
>            Reporter: Jan Van Besien
>            Assignee: Eli Levine
>         Attachments: mt.diff
> From the multi tenancy docs ( I had the
impression that it is mandatory to create tenant specific views.
> The basic use case where you simply create a tenant specific connection on a table where
multi tenancy is enabled, and you transparently only see the data specific to your tenant
(leaving out the tenantid column), is missing in the documentation.
> I think it would be useful to start the documentation with such an example before talking
about tenant specific views.

This message was sent by Atlassian JIRA

View raw message