> > >
> > > > > > Thought as much, thanks very much for taking the time to
> > > > respond.
> > > > > >
> > > > > > Appreciated
> > > > > >
> > > > > > Simon
> > > >
t 11:19 -0400, Josh Elser wrote:
> > > > > > Hi Simon,
> > > > > >
> > > > > > Phoenix does not provide any authorization/security layers on
> > > top
> > > > > of
> > > > > > what HBase does (the thread on
p
> > > > of
> > > > > what HBase does (the thread on user@hbase has a suggestion on
> > > > cell
> > > > > ACLs
> > > > > which is good).
> > > > >
> > > > > I think the question you're ultim
olumn) added to your primary key constraint
> > > > auto-magically. If a user doesn't set a TenantID, then they see
> > > _all_
> > > > data.
> > > >
> > > > Unless you have a layer in-between Phoenix and your end-users
> > > that
gt; data.
> > >
> > > Unless you have a layer in-between Phoenix and your end-users
> > that
> > > add
> > > extra guarantees/restrictions, a user could set their own
> > TenantID
> > > and
> > > see other folks' data. I
this is a good solution for
> > what
> > you're trying to accomplish.
> >
> > On 9/2/19 8:34 PM, Simon Mottram wrote:
> > > Hi
> > >
> > > I'm working on a project where we have a combination of very sparse
> > > data columns with
his is a good solution for
> what
> you're trying to accomplish.
>
> On 9/2/19 8:34 PM, Simon Mottram wrote:
> > Hi
> >
> > I'm working on a project where we have a combination of very sparse
> > data columns with added headaches of multi-tenanc
nantID and
see other folks' data. I don't think this is a good solution for what
you're trying to accomplish.
On 9/2/19 8:34 PM, Simon Mottram wrote:
Hi
I'm working on a project where we have a combination of very sparse
data columns with added headaches of multi-tenancy.
Hi
I'm working on a project where we have a combination of very sparse
data columns with added headaches of multi-tenancy. Hbase looks great
for the back end but I need to check that we can support the customer's
multi-tenancy requirements.
There are 2 that I'm struggling to fi
46 p.m., "Eli Levine" 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’i
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
Hi Mark,
There's not a great reason for this restriction, so it can likely be
relaxed. The tenant ID comes from a connection property, so it'll be a
string, but we could convert it based on the data type of the first
column. Please file a JIRA is this is important for your use case.
Thanks,
James
Hi everyone,
Quote from http://phoenix.apache.org/multi-tenancy.html:
The column that identifies the tenant may be given any name, but must of type
VARCHAR or CHAR. Regular Phoenix connections work with such tables with no
constraints, including working with data across tenant boundaries.
Is th
Jan, thank you for reporting. Working on reproing now.
On Tue, Aug 26, 2014 at 10:50 AM, Eli Levine wrote:
> Dan, TenantId can be embedded directly into a URL used to establish
> connections like this. e.g. jdbc:phoenix:localhost;TenantId=jan Note the
> use of a semicolon after localhost.
>
>
Dan, TenantId can be embedded directly into a URL used to establish
connections like this. e.g. jdbc:phoenix:localhost;TenantId=jan Note the
use of a semicolon after localhost.
On Tue, Aug 26, 2014 at 9:40 AM, Dan Di Spaltro
wrote:
> I've only ever used TenantId in the properties map, I didn't
I've only ever used TenantId in the properties map, I didn't know you could
do that from the connection string (can you?).
Properties pros = new Properties();
props.setProperty("TenantId", "jan");
Connection tenantConn = DriverManager.getConnection(tenantUrl, props);
On Tue, Aug 26, 2014 at 7:
A second problem I noticed is difficult to reproduce in code, so bear with me.
The problem seems to be that it is impossible to create a tenant
specific connection if the same driver instance hasn't previously been
used to create a global connection.
To reproduce:
- connect to a running hbase wit
On Fri, Aug 22, 2014 at 5:18 PM, James Taylor wrote:
> Yes, this works as designed. Would you mind filing a JIRA for us to enhance
> our multi tenant docs, as it sounds like it's unclear?
I created the jira ticket and some progress has already been made,
happy about that ;-)
However, I still hav
can, of
course, create indexes on your base table, though.
Thanks,
James
On Friday, August 22, 2014, Jan Van Besien wrote:
> Hi,
>
> I was experimenting with the Multi tenancy feature in the 4.0 branch.
>
> The documentation mentions how to create/use tenant specific views,
> which
Hi,
I was experimenting with the Multi tenancy feature in the 4.0 branch.
The documentation mentions how to create/use tenant specific views,
which works as documented.
However, I accidentally seemed to be able to get all the features I
want without using views:
// create a driver and connect
20 matches
Mail list logo
