A multi-tenant table's first PK column is treated as the tenant id column. Since it's the fist PK column, tenant data is naturally co-located. A tenant-specific connection automatically applies a where clause that tenant to only see its data in multi-tenant tables and tenant-specific views over those tables.
Thanks, Eli On Mon, Oct 9, 2017 at 11:05 PM, sudipta das <[email protected]> wrote: > Thanks Eli for your reply. > > I am looking forward for the internal processing of multi-tenant feature > of Phoenix. > > Does it applies a where clause filter in sql once multi-tenant jdbc > connection is established? > > Also, does it partition the data in back-end once we load a multi- tenant > table? > > How about the performance of a multi-tenant table? > > Kindly provide your valuable response. > > Thanks, > Sudipta > > On 6 Oct 2017 11:46 p.m., "Eli Levine" <[email protected]> wrote: > >> Hi Sudipta, >> >> This is a good high-level overview of Phoenix’s multi-tenancy: >> https://phoenix.apache.org/multi-tenancy.html >> >> Are you looking for more info than what’s on that page? >> >> CC’ing user@phoenix, since this might be useful to others. >> >> Thanks, >> >> Eli >> >> >> On Wed, Oct 4, 2017 at 10:28 PM, sudipta das <[email protected]> >> wrote: >> >>> Hello Eli, >>> >>> I have got your mail id while searching more details on Phoenix >>> Multi-Tenancy. >>> I am looking for how multi-tenancy works ? >>> >>> Can you please share some details ? >>> >>> Thanks, >>> Sudipta >>> >> >>
