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 w
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
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
Phoenix queries seem to return incorrect results when defining tables
with more salt buckets than regions. Is this a known problem or am I
misunderstanding something?
I tested with phoenix 5.1.2 and hbase 2.1.4.
Create a table with 4 salt buckets and 2 initial regions and add some values:
create
cket in it, and it is not hard
> to get into the state that you describe.
> We have at least one JIRA open for it.
> Phoenix will automatically pre-split according to the salt buckets if you
> don't explicitly specify the splits in the create table statement.
>
> On Tue, No
