[ANNOUNCE] Apache Phoenix 5.0.0 released
The Apache Phoenix team is pleased to announce release of it's next major version 5.0.0 compatible with HBase 2.0+. Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop using Apache HBase as its backing store and providing integration with other projects in the Apache ecosystem such as Spark, Hive, Pig, Flume, and MapReduce. The 5.0.0 release has feature parity with recently released 4.14.0. Highlights of the release include: * Cleanup deprecated APIs and leveraged new Performant APIs * Refactored coprocessor implementations to make use new Coprocessor or Observer APIs in HBase 2.0 * Hive and Spark Integration works in latest versions of Hive(3.0.0) and Spark(2.3.0) respectively. For more details, visit our blog here [1] and download source and binaries here [2]. Thanks, Rajeshbabu (on behalf of the Apache Phoenix team) [1] https://blogs.apache.org/phoenix/entry/apache-phoenix-releases-next-major [2] http://phoenix.apache.org/download.html
[jira] [Created] (PHOENIX-4814) performance.py fails with "Error: Invalid or corrupt jarfile"
Albert Chu created PHOENIX-4814:
---
Summary: performance.py fails with "Error: Invalid or corrupt
jarfile"
Key: PHOENIX-4814
URL: https://issues.apache.org/jira/browse/PHOENIX-4814
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.14.0
Reporter: Albert Chu
I recently hit
{noformat}
Error: Invalid or corrupt jarfile /var/tmp/achu/data_ylzK6q.csv
{noformat}
with the apache-phoenix-4.14.0-HBase-1.2/1.3/1.4-bin packages released.
But I did NOT hit it with apache-phoenix-4.14.0-HBase-1.1-bin release.
I noticed issue PHOENIX-4510 introduced a fix related to this error message and
noticed that the change in that fix did not propogate into each release of
4.14.0. It did not get into the 4.14.0-HBase-1.1-bin release. Probably not a
coincidence?
{noformat}
>grep PHOENIX_TESTS_JAR_PATTERN apache-phoenix-4.14.*/bin/phoenix_utils.py |
>grep findFile
apache-phoenix-4.14.0-HBase-1.1-bin/bin/phoenix_utils.py: testjar =
findFileInPathWithoutRecursion(PHOENIX_TESTS_JAR_PATTERN,
os.path.join(current_dir, ".."))
apache-phoenix-4.14.0-HBase-1.2-bin/bin/phoenix_utils.py: testjar =
findFileInPathWithoutRecursion(PHOENIX_TESTS_JAR_PATTERN,
os.path.join(current_dir, "..", 'lib'))
apache-phoenix-4.14.0-HBase-1.3-bin/bin/phoenix_utils.py: testjar =
findFileInPathWithoutRecursion(PHOENIX_TESTS_JAR_PATTERN,
os.path.join(current_dir, "..", 'lib'))
apache-phoenix-4.14.0-HBase-1.4-bin/bin/phoenix_utils.py: testjar =
findFileInPathWithoutRecursion(PHOENIX_TESTS_JAR_PATTERN,
os.path.join(current_dir, "..", 'lib'))
{noformat}
PHOENIX-4510 says the patch was released for 4.13.0, but it does not appear to
be applied in those releases either.
I have not looked at this beyond this simple level, but perhaps the patch in
PHOENIX-4510 is not the right fix?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (PHOENIX-4813) Support getActiveGeneralRpcHandlerCount in PhoenixRpcScheduler
Ted Yu created PHOENIX-4813:
---
Summary: Support getActiveGeneralRpcHandlerCount in
PhoenixRpcScheduler
Key: PHOENIX-4813
URL: https://issues.apache.org/jira/browse/PHOENIX-4813
Project: Phoenix
Issue Type: Task
Reporter: Ted Yu
Trying to start Phoenix on top of hbase 2.1, I observed the following:
{code}
2018-07-13 22:30:20,157 WARN [HBase-Metrics2-1] impl.MetricsSystemImpl: Caught
exception in callback postStart
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl$3.invoke(MetricsSystemImpl.java:320)
at com.sun.proxy.$Proxy10.postStart(Unknown Source)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:193)
at
org.apache.hadoop.metrics2.impl.JmxCacheBuster$JmxCacheBusterRunnable.run(JmxCacheBuster.java:109)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.AbstractMethodError:
org.apache.hadoop.hbase.ipc.RpcScheduler.getActiveGeneralRpcHandlerCount()I
at
org.apache.hadoop.hbase.ipc.MetricsHBaseServerWrapperImpl.getActiveGeneralRpcHandlerCount(MetricsHBaseServerWrapperImpl.java:90)
at
org.apache.hadoop.hbase.ipc.MetricsHBaseServerSourceImpl.getMetrics(MetricsHBaseServerSourceImpl.java:160)
at
org.apache.hadoop.metrics2.impl.MetricsSourceAdapter.getMetrics(MetricsSourceAdapter.java:200)
at
org.apache.hadoop.metrics2.impl.MetricsSourceAdapter.updateJmxCache(MetricsSourceAdapter.java:183)
at
org.apache.hadoop.metrics2.impl.MetricsSourceAdapter.getMBeanInfo(MetricsSourceAdapter.java:156)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getNewMBeanClassName(DefaultMBeanServerInterceptor.java:333)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:319)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at org.apache.hadoop.metrics2.util.MBeans.register(MBeans.java:67)
at
org.apache.hadoop.metrics2.impl.MetricsSourceAdapter.startMBeans(MetricsSourceAdapter.java:222)
at
org.apache.hadoop.metrics2.impl.MetricsSourceAdapter.start(MetricsSourceAdapter.java:101)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.registerSource(MetricsSystemImpl.java:268)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl$1.postStart(MetricsSystemImpl.java:239)
{code}
The method, {{getActiveGeneralRpcHandlerCount}}, was added by:
HBASE-20450 Provide metrics for number of total active, priority and
replication rpc handlers
PhoenixRpcScheduler needs to support this method in order to deploy on hbase
2.1 cluster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-2341) Rename in ALTER statement
[ https://issues.apache.org/jira/browse/PHOENIX-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543731#comment-16543731 ] Sergey Soldatov commented on PHOENIX-2341: -- Obviously, that should be easy to do for encoded column names. > Rename in ALTER statement > - > > Key: PHOENIX-2341 > URL: https://issues.apache.org/jira/browse/PHOENIX-2341 > Project: Phoenix > Issue Type: Improvement >Reporter: alex kamil >Priority: Minor > Labels: newbie > > Add RENAME functionality in ALTER statement (e.g. similar to PostgreSQL): > ALTER TABLE name > RENAME column TO new_column > ALTER TABLE name > RENAME TO new_name > ALTER TABLE name > SET SCHEMA new_schema > Reference: http://www.postgresql.org/docs/9.1/static/sql-altertable.html > Related: PHOENIX-152, PHOENIX-1598 , PHOENIX-1940 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PHOENIX-4688) Add kerberos authentication to python-phoenixdb
[ https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543621#comment-16543621 ] ASF GitHub Bot commented on PHOENIX-4688: - Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/307 On the note about docker, trying to think about this, I feel like a docker environment that can spin up all of the necessary stuff to run both of the python tests as well as this new one will be best. Essentially, in the docker container, we have PQS up with all of the necessary environment stuff which will make all of our current tests (and any future test) that much easier to automate. I'm also happy to try to help with that. I know you've spent a bunch of time on this already @pu239ppy > Add kerberos authentication to python-phoenixdb > --- > > Key: PHOENIX-4688 > URL: https://issues.apache.org/jira/browse/PHOENIX-4688 > Project: Phoenix > Issue Type: Improvement >Reporter: Lev Bronshtein >Priority: Minor > > In its current state python-phoenixdv does not support support kerberos > authentication. Using a modern python http library such as requests or > urllib it would be simple (if not trivial) to add this support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] phoenix issue #307: PHOENIX-4688 Kerberize python phoenixdb
Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/307 On the note about docker, trying to think about this, I feel like a docker environment that can spin up all of the necessary stuff to run both of the python tests as well as this new one will be best. Essentially, in the docker container, we have PQS up with all of the necessary environment stuff which will make all of our current tests (and any future test) that much easier to automate. I'm also happy to try to help with that. I know you've spent a bunch of time on this already @pu239ppy ---
[jira] [Commented] (PHOENIX-4688) Add kerberos authentication to python-phoenixdb
[ https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543496#comment-16543496 ] ASF GitHub Bot commented on PHOENIX-4688: - Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/307 If there's a bright-side, it's something in my environment. Spinning up the JDBC thin client against this setup works: ``` $ PHOENIX_OPTS="$PHOENIX_OPTS -Dsun.security.krb5.debug=true -Djava.security.krb5.conf=/Users/jelser/projects/phoenix.git/phoenix-queryserver/target/test-data/8bc1abb8-79fa-4beb-aa56-fe3ae4edff64/kdc/1531499757782/krb5.conf " /usr/local/lib/phoenix-4.14.0-HBase-1.4/bin/sqlline-thin.py http://localhost:60358 -a SPNEGO ``` > Add kerberos authentication to python-phoenixdb > --- > > Key: PHOENIX-4688 > URL: https://issues.apache.org/jira/browse/PHOENIX-4688 > Project: Phoenix > Issue Type: Improvement >Reporter: Lev Bronshtein >Priority: Minor > > In its current state python-phoenixdv does not support support kerberos > authentication. Using a modern python http library such as requests or > urllib it would be simple (if not trivial) to add this support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] phoenix issue #307: PHOENIX-4688 Kerberize python phoenixdb
Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/307 If there's a bright-side, it's something in my environment. Spinning up the JDBC thin client against this setup works: ``` $ PHOENIX_OPTS="$PHOENIX_OPTS -Dsun.security.krb5.debug=true -Djava.security.krb5.conf=/Users/jelser/projects/phoenix.git/phoenix-queryserver/target/test-data/8bc1abb8-79fa-4beb-aa56-fe3ae4edff64/kdc/1531499757782/krb5.conf " /usr/local/lib/phoenix-4.14.0-HBase-1.4/bin/sqlline-thin.py http://localhost:60358 -a SPNEGO ``` ---
[jira] [Commented] (PHOENIX-4688) Add kerberos authentication to python-phoenixdb
[
https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543479#comment-16543479
]
ASF GitHub Bot commented on PHOENIX-4688:
-
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/307
Turning back on `KRB5_TRACE`...
```
DEBUG:phoenixdb.avatica.client:POST http://localhost:60358/
'\n?org.apache.calcite.avatica.proto.Requests$OpenConnectionRequest\x12&\n$386e3317-e23e-4a0e-9fc6-2efaa546ffc4'
{'content-type': 'application/x-google-protobuf'}
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1):
localhost:60358
send: 'POST / HTTP/1.1\r\nHost: localhost:60358\r\nConnection:
keep-alive\r\nAccept-Encoding: gzip, deflate\r\nAccept: */*\r\nUser-Agent:
python-requests/2.19.1\r\ncontent-type:
application/x-google-protobuf\r\nContent-Length:
105\r\n\r\n\n?org.apache.calcite.avatica.proto.Requests$OpenConnectionRequest\x12&\n$386e3317-e23e-4a0e-9fc6-2efaa546ffc4'
reply: 'HTTP/1.1 401 Unauthorized\r\n'
header: Date: Fri, 13 Jul 2018 17:23:46 GMT
header: WWW-Authenticate: Negotiate
header: Cache-Control: must-revalidate,no-cache,no-store
header: Content-Type: text/html; charset=ISO-8859-1
header: Content-Length: 281
header: Server: Jetty(9.2.19.v20160908)
DEBUG:urllib3.connectionpool:http://localhost:60358 "POST / HTTP/1.1" 401
281
DEBUG:requests_kerberos.kerberos_:handle_401(): Handling: 401
[28575] 1531502626.856661: ccselect module realm chose cache
FILE:/tmp/krb5cc_502 with client principal us...@example.com for server
principal HTTP/localh...@example.com
[28575] 1531502626.856662: Getting credentials us...@example.com ->
HTTP/localhost@ using ccache FILE:/tmp/krb5cc_502
[28575] 1531502626.856663: Retrieving us...@example.com -> HTTP/localhost@
from FILE:/tmp/krb5cc_502 with result: -1765328243/Matching credential not
found (filename: /tmp/krb5cc_502)
[28575] 1531502626.856664: Retrying us...@example.com ->
HTTP/localh...@example.com with result: -1765328243/Matching credential not
found (filename: /tmp/krb5cc_502)
[28575] 1531502626.856665: Server has referral realm; starting with
HTTP/localh...@example.com
[28575] 1531502626.85: Retrieving us...@example.com ->
krbtgt/example@example.com from FILE:/tmp/krb5cc_502 with result: 0/Success
[28575] 1531502626.856667: Starting with TGT for client realm:
us...@example.com -> krbtgt/example@example.com
[28575] 1531502626.856668: Requesting tickets for
HTTP/localh...@example.com, referrals on
[28575] 1531502626.856669: Generated subkey for TGS request: aes128-cts/86C4
[28575] 1531502626.856670: etypes requested in TGS request: aes256-cts,
aes128-cts, aes256-sha2, aes128-sha2, des3-cbc-sha1, rc4-hmac, camellia128-cts,
camellia256-cts
[28575] 1531502626.856672: Encoding request body and padata into FAST
request
[28575] 1531502626.856673: Sending request (807 bytes) to EXAMPLE.COM
[28575] 1531502626.856674: Resolving hostname localhost
[28575] 1531502626.856675: Initiating TCP connection to stream ::1:60299
[28575] 1531502626.856676: Terminating TCP connection to stream ::1:60299
[28575] 1531502626.856677: Initiating TCP connection to stream
127.0.0.1:60299
[28575] 1531502626.856678: Sending TCP request to stream 127.0.0.1:60299
[28575] 1531502626.856679: Received answer (119 bytes) from stream
127.0.0.1:60299
[28575] 1531502626.856680: Terminating TCP connection to stream
127.0.0.1:60299
[28575] 1531502626.856681: Sending DNS URI query for _kerberos.EXAMPLE.COM.
[28575] 1531502626.856682: No URI records found
[28575] 1531502626.856683: Sending DNS SRV query for
_kerberos-master._udp.EXAMPLE.COM.
[28575] 1531502626.856684: Sending DNS SRV query for
_kerberos-master._tcp.EXAMPLE.COM.
[28575] 1531502626.856685: No SRV records found
[28575] 1531502626.856686: Response was not from master KDC
[28575] 1531502626.856687: TGS request result: -1765328343/Message stream
modified
[28575] 1531502626.856688: Requesting tickets for
HTTP/localh...@example.com, referrals off
[28575] 1531502626.856689: Generated subkey for TGS request: aes128-cts/F96F
[28575] 1531502626.856690: etypes requested in TGS request: aes256-cts,
aes128-cts, aes256-sha2, aes128-sha2, des3-cbc-sha1, rc4-hmac, camellia128-cts,
camellia256-cts
[28575] 1531502626.856692: Encoding request body and padata into FAST
request
[28575] 1531502626.856693: Sending request (807 bytes) to EXAMPLE.COM
[28575] 1531502626.856694: Resolving hostname localhost
[28575] 1531502626.856695: Initiating TCP connection to stream ::1:60299
[28575] 1531502626.856696: Terminating TCP connection to stream ::1:60299
[28575] 1531502626.856697: Initiating TCP connection to stream
127.0.0.1:60299
[28575] 1531502626.856698: Sending TCP request to
[GitHub] phoenix issue #307: PHOENIX-4688 Kerberize python phoenixdb
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/307
Turning back on `KRB5_TRACE`...
```
DEBUG:phoenixdb.avatica.client:POST http://localhost:60358/
'\n?org.apache.calcite.avatica.proto.Requests$OpenConnectionRequest\x12&\n$386e3317-e23e-4a0e-9fc6-2efaa546ffc4'
{'content-type': 'application/x-google-protobuf'}
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1):
localhost:60358
send: 'POST / HTTP/1.1\r\nHost: localhost:60358\r\nConnection:
keep-alive\r\nAccept-Encoding: gzip, deflate\r\nAccept: */*\r\nUser-Agent:
python-requests/2.19.1\r\ncontent-type:
application/x-google-protobuf\r\nContent-Length:
105\r\n\r\n\n?org.apache.calcite.avatica.proto.Requests$OpenConnectionRequest\x12&\n$386e3317-e23e-4a0e-9fc6-2efaa546ffc4'
reply: 'HTTP/1.1 401 Unauthorized\r\n'
header: Date: Fri, 13 Jul 2018 17:23:46 GMT
header: WWW-Authenticate: Negotiate
header: Cache-Control: must-revalidate,no-cache,no-store
header: Content-Type: text/html; charset=ISO-8859-1
header: Content-Length: 281
header: Server: Jetty(9.2.19.v20160908)
DEBUG:urllib3.connectionpool:http://localhost:60358 "POST / HTTP/1.1" 401
281
DEBUG:requests_kerberos.kerberos_:handle_401(): Handling: 401
[28575] 1531502626.856661: ccselect module realm chose cache
FILE:/tmp/krb5cc_502 with client principal us...@example.com for server
principal HTTP/localh...@example.com
[28575] 1531502626.856662: Getting credentials us...@example.com ->
HTTP/localhost@ using ccache FILE:/tmp/krb5cc_502
[28575] 1531502626.856663: Retrieving us...@example.com -> HTTP/localhost@
from FILE:/tmp/krb5cc_502 with result: -1765328243/Matching credential not
found (filename: /tmp/krb5cc_502)
[28575] 1531502626.856664: Retrying us...@example.com ->
HTTP/localh...@example.com with result: -1765328243/Matching credential not
found (filename: /tmp/krb5cc_502)
[28575] 1531502626.856665: Server has referral realm; starting with
HTTP/localh...@example.com
[28575] 1531502626.85: Retrieving us...@example.com ->
krbtgt/example@example.com from FILE:/tmp/krb5cc_502 with result: 0/Success
[28575] 1531502626.856667: Starting with TGT for client realm:
us...@example.com -> krbtgt/example@example.com
[28575] 1531502626.856668: Requesting tickets for
HTTP/localh...@example.com, referrals on
[28575] 1531502626.856669: Generated subkey for TGS request: aes128-cts/86C4
[28575] 1531502626.856670: etypes requested in TGS request: aes256-cts,
aes128-cts, aes256-sha2, aes128-sha2, des3-cbc-sha1, rc4-hmac, camellia128-cts,
camellia256-cts
[28575] 1531502626.856672: Encoding request body and padata into FAST
request
[28575] 1531502626.856673: Sending request (807 bytes) to EXAMPLE.COM
[28575] 1531502626.856674: Resolving hostname localhost
[28575] 1531502626.856675: Initiating TCP connection to stream ::1:60299
[28575] 1531502626.856676: Terminating TCP connection to stream ::1:60299
[28575] 1531502626.856677: Initiating TCP connection to stream
127.0.0.1:60299
[28575] 1531502626.856678: Sending TCP request to stream 127.0.0.1:60299
[28575] 1531502626.856679: Received answer (119 bytes) from stream
127.0.0.1:60299
[28575] 1531502626.856680: Terminating TCP connection to stream
127.0.0.1:60299
[28575] 1531502626.856681: Sending DNS URI query for _kerberos.EXAMPLE.COM.
[28575] 1531502626.856682: No URI records found
[28575] 1531502626.856683: Sending DNS SRV query for
_kerberos-master._udp.EXAMPLE.COM.
[28575] 1531502626.856684: Sending DNS SRV query for
_kerberos-master._tcp.EXAMPLE.COM.
[28575] 1531502626.856685: No SRV records found
[28575] 1531502626.856686: Response was not from master KDC
[28575] 1531502626.856687: TGS request result: -1765328343/Message stream
modified
[28575] 1531502626.856688: Requesting tickets for
HTTP/localh...@example.com, referrals off
[28575] 1531502626.856689: Generated subkey for TGS request: aes128-cts/F96F
[28575] 1531502626.856690: etypes requested in TGS request: aes256-cts,
aes128-cts, aes256-sha2, aes128-sha2, des3-cbc-sha1, rc4-hmac, camellia128-cts,
camellia256-cts
[28575] 1531502626.856692: Encoding request body and padata into FAST
request
[28575] 1531502626.856693: Sending request (807 bytes) to EXAMPLE.COM
[28575] 1531502626.856694: Resolving hostname localhost
[28575] 1531502626.856695: Initiating TCP connection to stream ::1:60299
[28575] 1531502626.856696: Terminating TCP connection to stream ::1:60299
[28575] 1531502626.856697: Initiating TCP connection to stream
127.0.0.1:60299
[28575] 1531502626.856698: Sending TCP request to stream 127.0.0.1:60299
[28575] 1531502626.856699: Received answer (119 bytes) from stream
127.0.0.1:60299
[28575] 1531502626.856700: Terminating TCP connection to stream
127.0.0.1:60299
[28575] 1531502626.856701: Sending DNS URI
[jira] [Commented] (PHOENIX-4688) Add kerberos authentication to python-phoenixdb
[
https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543464#comment-16543464
]
ASF GitHub Bot commented on PHOENIX-4688:
-
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/307
Ok, where I'm at now:
* Python 2.7.15 (installed via pyenv)
* Using virtualenv to circumvent the .sh script
* Modified the junit test to just leave it running
* Modified the junit test to just use the minikdc's kdc.conf
* Pulled back the pykerberos dependency to 1.1.14 to get past an "illegal
instruction error" that I get with pykerberos-1.2.1 (or whatever pip found)
This gets the phoenixdb client to actually submit the initial POST and get
the `WWW-Authenticate: Negotiate` header back. However, my client seems to be
unable to generate its challenge data from our mini kdc:
```
DEBUG:phoenixdb.avatica.client:POST http://localhost:60358/
'\n@org.apache.calcite.avatica.proto.Requests$CloseConnectionRequest\x12&\n$f71fb5c5-a814-4766-9691-8aeddfc0eea4'
{'content-type': 'application/x-google-protobuf'}
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1):
localhost:60358
send: 'POST / HTTP/1.1\r\nHost: localhost:60358\r\nConnection:
keep-alive\r\nAccept-Encoding: gzip, deflate\r\nAccept: */*\r\nUser-Agent:
python-requests/2.19.1\r\ncontent-type:
application/x-google-protobuf\r\nContent-Length:
106\r\n\r\n\n@org.apache.calcite.avatica.proto.Requests$CloseConnectionRequest\x12&\n$f71fb5c5-a814-4766-9691-8aeddfc0eea4'
reply: 'HTTP/1.1 401 Unauthorized\r\n'
header: Date: Fri, 13 Jul 2018 17:06:02 GMT
header: WWW-Authenticate: Negotiate
header: Cache-Control: must-revalidate,no-cache,no-store
header: Content-Type: text/html; charset=ISO-8859-1
header: Content-Length: 281
header: Server: Jetty(9.2.19.v20160908)
DEBUG:urllib3.connectionpool:http://localhost:60358 "POST / HTTP/1.1" 401
281
DEBUG:requests_kerberos.kerberos_:handle_401(): Handling: 401
ERROR:requests_kerberos.kerberos_:generate_request_header():
authGSSClientStep() failed:
Traceback (most recent call last):
File
"/Users/jelser/projects/phoenix.git/python/requests-kerberos/requests_kerberos/kerberos_.py",
line 235, in generate_request_header
negotiate_resp_value)
GSSError: (('Unspecified GSS failure. Minor code may provide more
information', 851968), ('Message stream modified', 11))
ERROR:requests_kerberos.kerberos_:(('Unspecified GSS failure. Minor code
may provide more information', 851968), ('Message stream modified', 11))
Traceback (most recent call last):
File
"/Users/jelser/projects/phoenix.git/python/requests-kerberos/requests_kerberos/kerberos_.py",
line 235, in generate_request_header
negotiate_resp_value)
GSSError: (('Unspecified GSS failure. Minor code may provide more
information', 851968), ('Message stream modified', 11))
```
I can't seem to unwrap what's wrong with the request to the KDC which is
preventing that from happening. Need to find more debug...
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/jira/browse/PHOENIX-4688
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Lev Bronshtein
>Priority: Minor
>
> In its current state python-phoenixdv does not support support kerberos
> authentication. Using a modern python http library such as requests or
> urllib it would be simple (if not trivial) to add this support.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] phoenix issue #307: PHOENIX-4688 Kerberize python phoenixdb
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/307
Ok, where I'm at now:
* Python 2.7.15 (installed via pyenv)
* Using virtualenv to circumvent the .sh script
* Modified the junit test to just leave it running
* Modified the junit test to just use the minikdc's kdc.conf
* Pulled back the pykerberos dependency to 1.1.14 to get past an "illegal
instruction error" that I get with pykerberos-1.2.1 (or whatever pip found)
This gets the phoenixdb client to actually submit the initial POST and get
the `WWW-Authenticate: Negotiate` header back. However, my client seems to be
unable to generate its challenge data from our mini kdc:
```
DEBUG:phoenixdb.avatica.client:POST http://localhost:60358/
'\n@org.apache.calcite.avatica.proto.Requests$CloseConnectionRequest\x12&\n$f71fb5c5-a814-4766-9691-8aeddfc0eea4'
{'content-type': 'application/x-google-protobuf'}
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1):
localhost:60358
send: 'POST / HTTP/1.1\r\nHost: localhost:60358\r\nConnection:
keep-alive\r\nAccept-Encoding: gzip, deflate\r\nAccept: */*\r\nUser-Agent:
python-requests/2.19.1\r\ncontent-type:
application/x-google-protobuf\r\nContent-Length:
106\r\n\r\n\n@org.apache.calcite.avatica.proto.Requests$CloseConnectionRequest\x12&\n$f71fb5c5-a814-4766-9691-8aeddfc0eea4'
reply: 'HTTP/1.1 401 Unauthorized\r\n'
header: Date: Fri, 13 Jul 2018 17:06:02 GMT
header: WWW-Authenticate: Negotiate
header: Cache-Control: must-revalidate,no-cache,no-store
header: Content-Type: text/html; charset=ISO-8859-1
header: Content-Length: 281
header: Server: Jetty(9.2.19.v20160908)
DEBUG:urllib3.connectionpool:http://localhost:60358 "POST / HTTP/1.1" 401
281
DEBUG:requests_kerberos.kerberos_:handle_401(): Handling: 401
ERROR:requests_kerberos.kerberos_:generate_request_header():
authGSSClientStep() failed:
Traceback (most recent call last):
File
"/Users/jelser/projects/phoenix.git/python/requests-kerberos/requests_kerberos/kerberos_.py",
line 235, in generate_request_header
negotiate_resp_value)
GSSError: (('Unspecified GSS failure. Minor code may provide more
information', 851968), ('Message stream modified', 11))
ERROR:requests_kerberos.kerberos_:(('Unspecified GSS failure. Minor code
may provide more information', 851968), ('Message stream modified', 11))
Traceback (most recent call last):
File
"/Users/jelser/projects/phoenix.git/python/requests-kerberos/requests_kerberos/kerberos_.py",
line 235, in generate_request_header
negotiate_resp_value)
GSSError: (('Unspecified GSS failure. Minor code may provide more
information', 851968), ('Message stream modified', 11))
```
I can't seem to unwrap what's wrong with the request to the KDC which is
preventing that from happening. Need to find more debug...
---
[jira] [Commented] (PHOENIX-4688) Add kerberos authentication to python-phoenixdb
[ https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543400#comment-16543400 ] ASF GitHub Bot commented on PHOENIX-4688: - Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/307 Ah, I think my issue might have been cruft sitting in `python/requests-kerberos/`, the `build` dir and the `.egg-info` dir. Getting a straightforward HTTP/401 error now. That I know how to deal with :) > Add kerberos authentication to python-phoenixdb > --- > > Key: PHOENIX-4688 > URL: https://issues.apache.org/jira/browse/PHOENIX-4688 > Project: Phoenix > Issue Type: Improvement >Reporter: Lev Bronshtein >Priority: Minor > > In its current state python-phoenixdv does not support support kerberos > authentication. Using a modern python http library such as requests or > urllib it would be simple (if not trivial) to add this support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] phoenix issue #307: PHOENIX-4688 Kerberize python phoenixdb
Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/307 Ah, I think my issue might have been cruft sitting in `python/requests-kerberos/`, the `build` dir and the `.egg-info` dir. Getting a straightforward HTTP/401 error now. That I know how to deal with :) ---
[jira] [Commented] (PHOENIX-4688) Add kerberos authentication to python-phoenixdb
[ https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543391#comment-16543391 ] ASF GitHub Bot commented on PHOENIX-4688: - Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/307 > Not sure how you got MIT on Mac OS X, is it in some ports package Yeah, homebrew has a `krb5` package which I use for running stuff locally (e.g. I put it on the `PATH` before the Heimdal, osx-provided variant) > I suppose integrating docker into the mix would make things interesting. I'll try it over the weekend if I get the time. I'm playing with different versions of python now, but am just worried about the feasibility of this actually working on the general person's machine given how much I'm struggling :\ > Add kerberos authentication to python-phoenixdb > --- > > Key: PHOENIX-4688 > URL: https://issues.apache.org/jira/browse/PHOENIX-4688 > Project: Phoenix > Issue Type: Improvement >Reporter: Lev Bronshtein >Priority: Minor > > In its current state python-phoenixdv does not support support kerberos > authentication. Using a modern python http library such as requests or > urllib it would be simple (if not trivial) to add this support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] phoenix issue #307: PHOENIX-4688 Kerberize python phoenixdb
Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/307 > Not sure how you got MIT on Mac OS X, is it in some ports package Yeah, homebrew has a `krb5` package which I use for running stuff locally (e.g. I put it on the `PATH` before the Heimdal, osx-provided variant) > I suppose integrating docker into the mix would make things interesting. I'll try it over the weekend if I get the time. I'm playing with different versions of python now, but am just worried about the feasibility of this actually working on the general person's machine given how much I'm struggling :\ ---
[jira] [Commented] (PHOENIX-4688) Add kerberos authentication to python-phoenixdb
[ https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543021#comment-16543021 ] ASF GitHub Bot commented on PHOENIX-4688: - Github user pu239ppy commented on the issue: https://github.com/apache/phoenix/pull/307 @joshelser Not sure how you got MIT on Mac OS X, is it in some ports package? I can try this later on ubuntu perhaps, if you want a test with MIT. I suppose integrating docker into the mix would make things interesting. I'll try it over the weekend if I get the time > Add kerberos authentication to python-phoenixdb > --- > > Key: PHOENIX-4688 > URL: https://issues.apache.org/jira/browse/PHOENIX-4688 > Project: Phoenix > Issue Type: Improvement >Reporter: Lev Bronshtein >Priority: Minor > > In its current state python-phoenixdv does not support support kerberos > authentication. Using a modern python http library such as requests or > urllib it would be simple (if not trivial) to add this support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] phoenix issue #307: PHOENIX-4688 Kerberize python phoenixdb
Github user pu239ppy commented on the issue: https://github.com/apache/phoenix/pull/307 @joshelser Not sure how you got MIT on Mac OS X, is it in some ports package? I can try this later on ubuntu perhaps, if you want a test with MIT. I suppose integrating docker into the mix would make things interesting. I'll try it over the weekend if I get the time ---
[jira] [Commented] (PHOENIX-2341) Rename in ALTER statement
[ https://issues.apache.org/jira/browse/PHOENIX-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542967#comment-16542967 ] buptljy commented on PHOENIX-2341: -- Any progress on this ? > Rename in ALTER statement > - > > Key: PHOENIX-2341 > URL: https://issues.apache.org/jira/browse/PHOENIX-2341 > Project: Phoenix > Issue Type: Improvement >Reporter: alex kamil >Priority: Minor > Labels: newbie > > Add RENAME functionality in ALTER statement (e.g. similar to PostgreSQL): > ALTER TABLE name > RENAME column TO new_column > ALTER TABLE name > RENAME TO new_name > ALTER TABLE name > SET SCHEMA new_schema > Reference: http://www.postgresql.org/docs/9.1/static/sql-altertable.html > Related: PHOENIX-152, PHOENIX-1598 , PHOENIX-1940 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
