[
https://issues.apache.org/jira/browse/PHOENIX-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111030#comment-14111030
]
James Taylor commented on PHOENIX-1204:
---------------------------------------
Yes, I agree too - this was the intention to allow the multi-tenant table to be
used directly by a tenant-specific connection for the simple use case. You
really only need to create views if you want to add tenant-specific columns and
indexes.
Also, something to keep in mind: a tenant-specific connection may access non
multi-tenant tables as well.
> 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)
