ASF policy states that we have to talk about unreleased code on the dev
list, not the user list. Moving this over to the dev list as such :)
On 11/4/19 8:41 AM, Alexander Batyrshin wrote:
As I see there are many bug fixes and updates (consistent indexes) for 4.x
Phoenix branch.
So im curios
As I see there are many bug fixes and updates (consistent indexes) for 4.x
Phoenix branch.
So im curios when this will be available for 5.x branch?
It's working fine with Kerberos, but we use streaming Spark jobs on Google
Dataproc cluster and seems it has some problems to make Spark -> Phoenix
JDBC -> HBase working, so I'm trying to find some workaround to keep HBase
unsecure and have "protection from mistake" for PQS that users use.
On
To the best of my knowledge Phoenix/HBase only supports Kerberos.
In past, i have used secure HBase/Phoenix cluster in web services and it
worked fine. Kerberos can be integrated with AD. But, you might need to
check whether Queryserver supports security or not. In worst case, a
potential
Hello community.
Does Phoenix have some kind of security for authentication and
authorization other then Kerberos ?
We're allowing our users connect to our cluster with QueryServer, but at
the same time we want to authenticate them and control what kind of access
they can have (read only, write
