ase python-phoenixdb 1.2.1
> --
>
> Key: PHOENIX-6799
> URL: https://issues.apache.org/jira/browse/PHOENIX-6799
> Project: Phoenix
> Issue Type: Task
> Components: python
> Affects Versi
[
https://issues.apache.org/jira/browse/PHOENIX-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned PHOENIX-6892:
Assignee: Istvan Toth
> Python Phoenixdb SqlAlchemy tests fail with SqlAlchemy
Istvan Toth created PHOENIX-6892:
Summary: Python Phoenixdb SqlAlchemy tests fail with SqlAlchemy 2.0
Key: PHOENIX-6892
URL: https://issues.apache.org/jira/browse/PHOENIX-6892
Project: Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richárd Antal updated PHOENIX-6820:
---
Fix Version/s: python-phoenixdb-1.2.2
> Update python-phoenixdb/RELEASING.
ticket
> Update python-phoenixdb/RELEASING.rst
> -
>
> Key: PHOENIX-6820
> URL: https://issues.apache.org/jira/browse/PHOENIX-6820
> Project: Phoenix
> Issue Type: Task
>
Richárd Antal created PHOENIX-6820:
--
Summary: Update python-phoenixdb/RELEASING.rst
Key: PHOENIX-6820
URL: https://issues.apache.org/jira/browse/PHOENIX-6820
Project: Phoenix
Issue Type
Hi
I agree we should do a new Python PhoenixDB release.
It has been almost a month since the first email, there wasn't any other
ticket mentioned that we should include in the release, so I would like
to proceed with the process.
I volunteer to be the RM for the release.
I created PHOENIX
Richárd Antal created PHOENIX-6799:
--
Summary: Release python-phoenixdb 1.2.1
Key: PHOENIX-6799
URL: https://issues.apache.org/jira/browse/PHOENIX-6799
Project: Phoenix
Issue Type: Task
Hi!
Richard has found that the gssapi OID fix fix in PHOENIX-6414 wasn't
applied to a
backwards compatibility case, which causes failures with the new kerberos
implementation in Avatica 1.21.0. (PHOENIX-6781)
I propose releasing Python PhoenixDB 1.2.1 with PHOENIX-6781 as the only
signif
[
https://issues.apache.org/jira/browse/PHOENIX-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6739.
--
Fix Version/s: python-phoenixdb-1.2.0
Resolution: Done
> Release python-phoeni
Istvan Toth created PHOENIX-6739:
Summary: Release python-phoenixdb 1.2.0
Key: PHOENIX-6739
URL: https://issues.apache.org/jira/browse/PHOENIX-6739
Project: Phoenix
Issue Type: Task
[
https://issues.apache.org/jira/browse/PHOENIX-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6529.
--
Resolution: Fixed
> Release python-phoenixdb 1.
[
https://issues.apache.org/jira/browse/PHOENIX-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6529:
-
Fix Version/s: (was: python-phoenixdb-1.1.1)
python-phoenixdb-1.1.0
[
https://issues.apache.org/jira/browse/PHOENIX-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6529:
-
Fix Version/s: (was: python-phoenixdb-1.1.0)
python-phoenixdb-1.1.1
[
https://issues.apache.org/jira/browse/PHOENIX-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6529:
-
Fix Version/s: python-phoenixdb-1.1.0
> Release python-phoenixdb 1.
Istvan Toth created PHOENIX-6529:
Summary: Release python-phoenixdb 1.1.0
Key: PHOENIX-6529
URL: https://issues.apache.org/jira/browse/PHOENIX-6529
Project: Phoenix
Issue Type: Task
[
https://issues.apache.org/jira/browse/PHOENIX-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6465:
-
Fix Version/s: (was: 1.0.1)
python-phoenixdb-1.0.1
> Close sessi
[
https://issues.apache.org/jira/browse/PHOENIX-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6484:
-
Fix Version/s: (was: 1.1.0)
python-phoenixdb-1.1.0
> Python phoeni
Hi!
We have some metadata index and primary key handling improvements in
PHOENIX-6410, which would be a real help for Hue.
I propose that we release 1.1.0 with those.
I volunteer to to be the RM.
Please let me know if you have any objections, want to volunteer as RM
(though only Josh, Ankit, and
an array type column.
Resolution: Fixed
Committed.
Thanks for the review and the help in repro, Romain.
> Python phoenixdb throws error on empty resultsets with array types
> ---
>
> Key:
Istvan Toth created PHOENIX-6484:
Summary: Python phoenixdb throws error on empty resultsets with
array types
Key: PHOENIX-6484
URL: https://issues.apache.org/jira/browse/PHOENIX-6484
Project
[
https://issues.apache.org/jira/browse/PHOENIX-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6464.
--
Resolution: Fixed
> Release python-phoenixdb 1.
[
https://issues.apache.org/jira/browse/PHOENIX-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6465.
--
Resolution: Fixed
> Close sessions explicitly in python-phoeni
Istvan Toth created PHOENIX-6465:
Summary: Close sessions explicitly in python-phoenixdb
Key: PHOENIX-6465
URL: https://issues.apache.org/jira/browse/PHOENIX-6465
Project: Phoenix
Issue Type
Istvan Toth created PHOENIX-6464:
Summary: Release python-phoenixdb 1.0.1
Key: PHOENIX-6464
URL: https://issues.apache.org/jira/browse/PHOENIX-6464
Project: Phoenix
Issue Type: Task
Yes, that'd be great.
The tl;dr for others: Knox employs a cookie for redirecting clients back
to the same backend PQS server. However, the Python library didn't pass
this cookie back to Knox. This results in the second Avatica API call
going to a different PQS instance which doesn't have the
Hi!
PHOENIX-6459 is a show-stopper for using phoenixdb when Knox HA is used.
I propose releasing phoenixdb 1.0.1 after Josh's fix lands.
regards
Istvan
Hi!
I think that we are ready to do a formal release of python-phoenixdb from
the Phoenix project, and publish it to PyPI.
I volunteer to be the release manager for python-phoenixdb-1.0.0.
We have discussed with Josh and Ankit the PyPI release requirements and
process https://issues.apache.org
improvements [~rajeshbabu] and [~elserj]
> Create release script for python-phoenixdb ASF releases
> ---
>
> Key: PHOENIX-6060
> URL: https://issues.apache.org/jira/browse/PHOENIX-6060
>
-6.0.0
Description: A simplified version of the release script in
apache/phoenix.
> Create release script for python-phoenixdb ASF releases
> ---
>
> Key: PHOENIX-6060
> URL: https://is
Istvan Toth created PHOENIX-6060:
Summary: Create release script for python-phoenixdb ASF releases
Key: PHOENIX-6060
URL: https://issues.apache.org/jira/browse/PHOENIX-6060
Project: Phoenix
I agree with everything that you said.
However by 'source release', I was merely referring to a Python/PyPI
packaging technicality, where we distribute the package in the form that is
generated by *python setup.py sdist*,
as opposed to the pre-built binary egg or wheel formats.
But since you brou
Yup, let's just draw a number (whatever we'd like, as long as it follows
the standard PEP for versioning). When we release it, we can advertise
whatever level of stability we expect it to have (i.e. "This is an
alpha, you can try it if you want").
ASF is very strict when it comes to releases i
The Beam guide looks interesting, we could certainly borrow from it.
I'm fine with your suggested process. Here's my interpretation of it:
- No dev releases on PyPI
- Decoupling PhoenixDB versioning from PQS versioning
- Making a proper minor/patch release when important features/fixes l
ASF releases do not have to be on the order of years. As long as we have
three people to vote, we can do releases as often as we'd like. The
lower-bound on release cadence is probably on the order of "weeks" (as
opposed to days) but that's primarily limited by bandwidth of our
volunteers :)
A
One more thing :)
Apache Beam appears to have an excellent release guide which includes
their process which involves PyPi --
https://beam.apache.org/contribute/release-guide/
Maybe we can copy them?
On 6/15/20 1:08 PM, Josh Elser wrote:
Did a little searching..
* Found a 2011 blog post fro
TestPyPi certainly seems useful to practice the release process, and avoid
mistakes with it.
However, I don't think that it is a substitute for a .devN release, which
(in my mind) is meant to give the users something to use until we get all
our ducks in a row to do a proper 1.0 release. The primar
Did a little searching..
* Found a 2011 blog post from sqlalchemy which said (as a project) they
would not post devN releases to pypi
* There's a TestPyPi [1] instead which seems to be for staging work.
Could we play with staging there? And then push to pypi (real) after we
do a normal vote?
Hey Istvan,
Great of you to drive this work!
I do have one concern about pushing the dev releases to PyPi (I'm
assuming that's what you mean). I understand that in the Python world a
"dev" release indicates that this isn't an "official" release [1].
At the ASF, you're correct that we, develo
Hi!
Even though we have adopted the PhoenixDB driver in 2018, there hasn't been
much activity on it, and the version available on PyPI is still the old 0.7
release by Lukas.
Recently I have worked on it quite a bit, adding fixes and new features,
and adopting the partial SQLAlchemy driver from py
[
https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni closed PHOENIX-4688.
-
Bulk closing Jiras for the 4.15.0 release.
> Add kerberos authentication to pyt
[
https://issues.apache.org/jira/browse/PHOENIX-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Tarassov updated PHOENIX-5598:
---
Attachment: Screen Shot 2019-12-05 at 21.48.28.png
> Python phoenixdb unable to conn
[
https://issues.apache.org/jira/browse/PHOENIX-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Tarassov updated PHOENIX-5598:
---
Attachment: Screen Shot 2019-12-05 at 21.42.12.png
> Python phoenixdb unable to conn
n url.
:bpl-cookie-hdp-infra-00.devops.guavus.mtl:2181,bpl-cookie-hdp-infra-01.devops.guavus.mtl:2181,bpl-cookie-hdp-infra-02.devops.guavus.mtl:2181:2181:/hbase-unsecure;'
{noformat}
Please take the time to read your error messages closely before filing an issue.
> Python phoenixdb unab
Oleg Tarassov created PHOENIX-5598:
--
Summary: Python phoenixdb unable to connect with Phoenix 5.x on
HDP 3.1
Key: PHOENIX-5598
URL: https://issues.apache.org/jira/browse/PHOENIX-5598
Project
4.15.0
Calling it! Pushed this to 4.15 and 5.1.
It is more than good enough for a first stab at this. We can continue to
iterate now that we have a starting point.
Thanks for your Herculean efforts, Lev! Truly impressive.
> Add kerberos authentication to python-phoeni
what happened to the change you proposed?)
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/jira/browse/PHOENIX-4688
>
as "java -jar" which is nice. Then, we
could have a Maven module which consumes this jar, provides that Dockerfile,
and runs any/all tests we have. The perk of this approach is that we could also
run the rest of the Python tests this way which would be nice.
> Add kerberos au
en a little busy this week, but will try to get to
this soon. If you have any suggestions on how to instrument this, let me know.
I am assuming all we need is a well written docker file
> Add kerberos authentication to python-ph
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/jira/browse/PHOENIX-4688
> Project: Phoenix
> Issue Type: Improvement
&g
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 b
.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 authent
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
-Dja
s/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))
```
So, definitely the KDC throwing a f
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
rberos/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
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 te
erberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/jira/browse/PHOENIX-4688
> Project: Phoenix
> Issue Type: Improvement
>
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
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
> Pro
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 Heimda
7;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
> Projec
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
I ran into another GH issue saying that pykerberos==1.1.14 fixed it for
them, but I'm not seeing a difference locally.
How do you feel about requiring Docker, @pu239ppy? ;)
> Add kerberos authentication to python-phoenixdb
> -
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/307
Ugh, I'm getting frustrated:
I have MIT kerberos on my Mac, so I unblocked myself first by just forcing
the minikdc config file to be made instead of the if-branch you added, Lev.
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/307
> If you are still unable to get .deactivate to work, remove it from the
shell script for now and we can revisit it. Again I am being overly pedantic
here, but a the shell exits, we really do not
ronment.
Ok. I'm looking at this again today. Thanks for the feedback so far.
The test/code looks good to me. I think we just need to update
documentation to explain what we're doing (maybe a README.md in `python/`?)
> Add kerberos authentication
executing python or just continue running in the same
shell, which is why I stopped attempts to make ny further reductions to the
shell script
Oh right, I forgot they would bash the environment. Let's just let this be
for now. Will be easier to come back
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r202108057
--- Diff: phoenix-queryserver/src/it/bin/test_phoenixdb.sh ---
@@ -0,0 +1,59 @@
+#/usr/bin/env bash
+
+set -u
+set -x
+set -e
+
t +e
+set +u
+kdestroy
--- End diff --
Ok, cool. I didn't think kdestroy was doing more than just cleaning up
those token :)
> Add kerberos authentication to python-phoenixdb
> ---
>
>
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r202106445
--- Diff: phoenix-queryserver/src/it/bin/test_phoenixdb.sh ---
@@ -0,0 +1,59 @@
+#/usr/bin/env bash
+
+set -u
+set -x
+set -e
+
any
environment.
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/jira/browse/PHOENIX-4688
> Project: Phoenix
>
Github user pu239ppy commented on the issue:
https://github.com/apache/phoenix/pull/307
@joshelser If you are still unable to get .deactivate to work, remove it
from the shell script for now and we can revisit it. Again I am being overly
pedantic here, but a the shell exits, we reall
1.getKey() + "@" + KDC.getRealm());
+cmdList.add(user1.getValue().getAbsolutePath());
+String osName = System.getProperty("os.name").toLowerCase();
+LOG.info("OS is " + osName);
+File krb5ConfFile = null;
+
Github user pu239ppy commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201717820
--- Diff:
phoenix-queryserver/src/it/java/org/apache/phoenix/end2end/SecureQueryServerPhoenixDBIT.java
---
@@ -0,0 +1,423 @@
+/*
+ * Licensed to t
on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201716375
--- Diff: python/phoenixdb-module/phoenixdb/__init__.py ---
@@ -1,11 +1,10 @@
-# Licensed to the Apache Software Foundation (ASF) under one or more
-# contributor license agreem
Github user pu239ppy commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201716375
--- Diff: python/phoenixdb-module/phoenixdb/__init__.py ---
@@ -1,11 +1,10 @@
-# Licensed to the Apache Software Foundation (ASF) under one or more
ugin
+
+
+**/SecureQueryServerPhoenixDBIT.java
--- End diff --
There are a few prerequisites
- Either anaconda or virtual env *must* to be installed
- System *must* provide either MIT or Heimdal kerberos utilities and
libraries
> Add kerberos authentication to python-ph
Github user pu239ppy commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201482973
--- Diff: phoenix-queryserver/pom.xml ---
@@ -47,6 +47,11 @@
org.apache.maven.plugins
maven-failsafe-plugin
+
t +e
+set +u
+kdestroy
--- End diff --
Not to be overly pedantic, but you would want to still pass krb5ccname and
just call kdestroy to make sure proper cleanup is done
> Add kerberos authentication to python-ph
Github user pu239ppy commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201482297
--- Diff:
phoenix-queryserver/src/it/java/org/apache/phoenix/end2end/SecureQueryServerPhoenixDBIT.java
---
@@ -0,0 +1,423 @@
+/*
+ * Licensed to t
Github user pu239ppy commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201482215
--- Diff: phoenix-queryserver/src/it/bin/test_phoenixdb.sh ---
@@ -0,0 +1,59 @@
+#/usr/bin/env bash
+
+set -u
+set -x
+set -e
+
conf", null);
+FileOutputStream fos = new FileOutputStream(krb5ConfFile);
+fos.write(krb5conf.toString().getBytes());
+fos.close();
+LOG.info("krb5.conf written to " +
krb5ConfFile.getAbsolutePath());
+
Github user pu239ppy commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201481976
--- Diff: phoenix-queryserver/src/it/bin/test_phoenixdb.sh ---
@@ -0,0 +1,59 @@
+#/usr/bin/env bash
+
+set -u
+set -x
+set -e
+
This stalled, although looking at the code now it probably should have been
a directory, which is why kinit stalled
I can try this again
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key:
from conda to virtualenv. I am
going to attempt to support both, but for now there is probably enough to look
at.
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: h
verPhoenixDBIT(359):
/Users/jelser/projects/phoenix.git/phoenix-queryserver/./src/it/bin/test_phoenixdb.sh:
line 12: deactivate: No such file or directory
```
Might have been me hacking on things... digging more.
> Add kerberos authentication to
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/307
Tried to run the test, but it failed with:
```
2018-07-10 13:43:55,599 ERROR [main]
end2end.SecureQueryServerPhoenixDBIT(359): + . deactivate ''
2018-07-10 13:43:55,599 ERROR [main]
en
update
python/phoenixdb/requirements.txt to make sure we pull that
0.13.0.dev0-phoenixdb, right?
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/ji
ros/requests_kerberos/__init__.py. We should update
python/phoenixdb/requirements.txt to make sure we pull that
0.13.0.dev0-phoenixdb, right?
---
t +e
+set +u
+kdestroy
--- End diff --
If we use a custom directory for the `kinit`, then this just becomes
removing that custom directory.
> Add kerberos authentication to python-phoenixdb
> ---
>
>
if they already
have one).
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/jira/browse/PHOENIX-4688
> Project: Pho
1.getKey() + "@" + KDC.getRealm());
+cmdList.add(user1.getValue().getAbsolutePath());
+String osName = System.getProperty("os.name").toLowerCase();
+LOG.info("OS is " + osName);
+File krb5ConfFile = null;
+if (osName.i
d on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201077800
--- Diff: python/phoenixdb-module/phoenixdb/__init__.py ---
@@ -1,11 +1,10 @@
-# Licensed to the Apache Software Foundation (ASF) under one or more
-# contributor license agreem
ugin
+
+
+**/SecureQueryServerPhoenixDBIT.java
--- End diff --
You not intending for this test to be executed during the normal build
process?
> Add kerberos authentication to python-phoenixdb
> ---
>
> K
ttps://www.apache.org/legal/resolved.html
> Add kerberos authentication to python-phoenixdb
> ---
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/jira/browse/PHOENIX-4688
> Project: Phoenix
.getInputStream()));
+BufferedReader processError = new BufferedReader(new
InputStreamReader(runPythonProcess.getErrorStream()));
+int exitCode = runPythonProcess.waitFor();
+
+// dump stdout and stderr
+ while (process
conf", null);
+FileOutputStream fos = new FileOutputStream(krb5ConfFile);
+ fos.write(krb5conf.toString().getBytes());
+fos.close();
+LOG.info("krb5.conf written to " +
krb5ConfFile.getAbsolutePath());
+
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201418146
--- Diff: phoenix-queryserver/pom.xml ---
@@ -47,6 +47,11 @@
org.apache.maven.plugins
maven-failsafe-plugin
+
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/307#discussion_r201078376
--- Diff: python/requests-kerberos/LICENSE ---
@@ -0,0 +1,15 @@
+ISC License
--- End diff --
Just calling out that this is allowed: ISC is
1 - 100 of 195 matches
Mail list logo
