Member since
07-17-2019
738
Posts
433
Kudos Received
111
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3478 | 08-06-2019 07:09 PM | |
| 3680 | 07-19-2019 01:57 PM | |
| 5208 | 02-25-2019 04:47 PM | |
| 4675 | 10-11-2018 02:47 PM | |
| 1772 | 09-26-2018 02:49 PM |
02-13-2017
04:18 PM
4 Kudos
"After tracing all the calls, it seems that it is caused by ODBC
driver sending out Avatica Http request with content-type set to
"application/x-www-form-urlencoded”, even though the content is NOT
urlencoded at all. But, when the request passes through Knox, it comes
out as urlencoded. The PQS seems not able to parse urlencoded content.
It seems to take the input as it is." This sounds like a bug in the ODBC driver. I'll have to see what I can find... "Then How can PQS impersonate as the authenticated user to call
HBase so that Ranger can control the access by that user? Since PQS runs
as "hbase" and it calls PQS as "hbase", ranger control cannot be used." This is a factor of impersonation from PQS to HBase (really, Phoenix) only being configured when Kerberos authentication is enabled. My answer to your other question on https://community.hortonworks.com/questions/83203/how-to-access-hbase-through-odbc-then-phoenix-quer.html already covered this. "How can Knox pass the authenticated user to PQS along with the proxy-ed HTTP request?" There is some on-going work which would help enable this in Avatica https://issues.apache.org/jira/browse/CALCITE-1539
... View more
02-13-2017
04:09 PM
2 Kudos
"How to have PQS turn on HTTP Basic authentication to authenticate the calls from ODBC?" This is not supported by PQS, but the code exists in Avatica to support it. http://calcite.apache.org/avatica/docs/security.html#http-basic-authentication Your only route presently is to modify Phoenix to support this. "How to turn on httpS on PQS to secure the connection?" This presently is not supported by PQS. "How to impersonate the calls from PQS to HBase with the authenticated user?" This is only supported via SPNEGO authentication in PQS. http://calcite.apache.org/avatica/docs/security.html#impersonation Again, you can modify Phoenix to support this but there is no out of the box solution. -- You can consider the use of Apache Knox to sit between the ODBC driver and PQS which would provide TLS and configurable authentication. https://issues.apache.org/jira/browse/KNOX-817 https://issues.apache.org/jira/browse/KNOX-844
... View more
02-09-2017
07:11 PM
It's possible. I certainly don't know from the Accumulo side why this would be failing. I can say that Accumulo deploys just fine via Ambari on HDP 2.5. Maybe the mighty @Robert Levas has a tip/suggestion?
... View more
02-08-2017
04:59 PM
1 Kudo
Did you include the proper hbase-site.xml on the classpath of your application?
... View more
02-08-2017
04:59 PM
ZooKeeper clients (your code and HBase) only communicate over 2181. ZooKeeper servers communicate among themselves on those ports.
... View more
02-08-2017
04:56 PM
1 Kudo
The HBase user probably can't read "/root" (unless you're running HBase as root which is a really bad idea if you are..). Just copy the jar in to the lib directory for the HBase installation.
... View more
02-08-2017
04:17 PM
You're probably going to have a rough time trying to build a Thrift server inside of a coprocessor. Why not just create a Thrift server external to HBase which can access your custom coprocessor via the standard protobuf RPCs?
... View more
02-08-2017
04:11 PM
There is no version of Avatica released which has the ability to specify the truststore.
... View more
02-08-2017
04:05 PM
Great. Glad you got to the bottom of it!
... View more
02-07-2017
10:53 PM
The path is just an artifact of when Accumulo was first added to Ambari (HDP-2.2.0). The files that are common to all versions of Accumulo can live in that common-services directory. I think that is a red-herring. https://github.com/apache/ambari/blob/2ad42074f1633c5c6f56cf979bdaa49440457566/ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/files/accumulo-metrics.xml Perhaps it is something trivial like you do not have the ambari-agent installed on the node in question (or maybe the wrong version of the ambari-agent)? I don't recall seeing this one before.
... View more