[ https://issues.apache.org/jira/browse/PHOENIX-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110395#comment-14110395 ]
Jan Van Besien commented on PHOENIX-1204: ----------------------------------------- yes, this is certainly an improvement because the document doesn't start talking about views straight away. However in my head (let me know if I got this wrong) there are two equal ways to use this: - the "no views" option: create tenant specific connections and work with the underlying table through these tenant specific connections - the "views" option: create views and work through the views The documentation still talks about the views as being *the* way to do it. Maybe it should be changed such that it says "if next to data isolation you also want feature x and y, you can create tenant specific views" whereby feature x and y are extra capabilities you get once you use tenant specific views over the "no views" approach. I am not 100% sure myself what these features would be, probably "schema isolation" next to "data isolation" or something like that? Also in the section about Tenant-specific tables it says: "A tenant specific connection may only query: - their own schema, which is to say it only sees tenant-specific views that were created by that tenant. non multi-tenant global tables, that is tables created with a regular connection without the MULTI_TENANT=TRUE declaration. " Is that actually correct? With a tenant specific connection is is perfectly possible to query multi-tenant tables without having to create tenant-specific views. > Unclear multi tenancy docs > -------------------------- > > Key: PHOENIX-1204 > URL: https://issues.apache.org/jira/browse/PHOENIX-1204 > 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 (http://phoenix.apache.org/multi-tenancy.html) 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 (v6.2#6252)