You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2019/04/18 15:25:00 UTC
[jira] [Assigned] (PHOENIX-5249) Implicit multi-tenancy by naming
convention
[ https://issues.apache.org/jira/browse/PHOENIX-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoffrey Jacoby reassigned PHOENIX-5249:
----------------------------------------
Assignee: Geoffrey Jacoby
> Implicit multi-tenancy by naming convention
> -------------------------------------------
>
> Key: PHOENIX-5249
> URL: https://issues.apache.org/jira/browse/PHOENIX-5249
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
>
> Many data models have a naming convention for the tenantId. It would be useful to define that convention with an optional Phoenix property in config, so if a tenant-specific connection is opened and a table is queried that has that tenantId column name in its PK, multi-tenant behavior automatically occurs even if MULTI_TENANT is not set in the table's metadata. (If MULTI_TENANT is explicitly false, multi-tenant behavior would not occur.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)