Geoffrey Jacoby created PHOENIX-6403:
----------------------------------------
Summary: Allow Non-Multi-Tenant Indexes on Multi-Tenant Tables
Key: PHOENIX-6403
URL: https://issues.apache.org/jira/browse/PHOENIX-6403
Project: Phoenix
Issue Type: New Feature
Reporter: Geoffrey Jacoby
When creating an index on a multi-tenant table, I believe we assume the index
is "multi-tenant" as well and thus automatically prepend the tenant id to the
key. It's occasionally really useful to have a table that automatically filters
on tenant_id for most of its access patterns, but which an admin process can
query or modify using a global connection across tenants efficiently.
Normally different access patterns can be handled using an index -- but not if
you can't create an index that doesn't start with a tenant id.
Note that PHOENIX-5248 and PHOENIX-5249 on our backlog attempt to solve
somewhat similar problems in a different way.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
