Yeah, I don't think the inclusion of Python code should be viewed as a
barrier to inclusion (maybe just a hurdle). I've seen other projects
(Ambari, iirc) which have tons of Python code and lots of integration.
The serialization for PQS can be changed via a single configuration
property in
Sorry for the delayed response, Lukáš. I still think it would be a good
addition and the JSON/Protobuf issue you brought up is all the more reason
to keep the JSON binding too.
We have precedence for non Java code with our Spark integration. Sure, it
makes it a bit more work to add this new
Glad you got it working, Steve. If you have a chance to file JIRAs where
you ran into issues, that'd be much appreciated.
Lukás - your Python Query Server support would be a welcome addition to
Phoenix or Avatica. Send us a pull request for a new module if you're
interested.
James
On
On Sat, Feb 6, 2016 at 12:53 AM, Steve Terrell
wrote:
> These two incidents leads me to guess that root cause of my issue with
> pythondb is that it was not correctly recognizing the Avatica version.
>
Unfortunately, there is no good way to automatically recognize the
This depends on the exact version of Avatica you are using, because it's
different in all released versions.
In this comment you can see an example of running UPSERT with 1.4 with the
JSON serializer (I think Phoenix 4.7 includes that version):
On Sat, Feb 6, 2016 at 7:28 AM, James Taylor wrote:
> Lukás - your Python Query Server support would be a welcome addition to
> Phoenix or Avatica. Send us a pull request for a new module if you're
> interested.
>
I was considering that when I got the first working
Phoenix 4.7.0 is not released yet. A couple of issues can up in the last
RC, so we'll roll a new one very soon.
Thanks,
James
On Fri, Feb 5, 2016 at 9:23 AM, Steve Terrell wrote:
> Oh, I didn't know there was a 4.7. Following the links on
>
But please feel free to play around with the last RC:
http://mail-archives.apache.org/mod_mbox/phoenix-dev/201601.mbox/%3CCAAF1JdgFzrwWBBcs586hkJnoZaZFBYDGxtaqUZjAuQM1XwBgOQ%40mail.gmail.com%3E
On Fri, Feb 5, 2016 at 9:26 AM, James Taylor wrote:
> Phoenix 4.7.0 is not
On Fri, Feb 5, 2016 at 8:46 PM, Steve Terrell
wrote:
>
> When I tried to send a "createStatement" via curl and via Lukas's
> phoenixdb, I got these error's respectively:
>
> HTTP ERROR: 500
> Problem accessing /. Reason:
> Cannot find parser for
>
>
> File
I'm using HBase 0.98.15, so I installed
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.7.0-HBase-0.98-rc1/
Had a problem starting the query server that I resolved by
deleting $PHOENIX_OPTS from queryserver.py . (It was giving me "Error:
Could not find or load main class $PHOENIX_OPTS")
Thanks, Lukas. Half the battle is won, now. With your help I was able to
see the JSON used to perform the upsert. Looks like my problem was that I
was not doing any "connectionSync" calls. I had played around with the
"createStatement" before my upsert SQL, but I may not have stumbled across
Success!
I had to fix another trivial bug in queryserver.py to allow the
*-Dphoenix.queryserver.**serialization=JSON* to get passed to the Java
command.
Then I ran into a pythondb error very much like the one described at
12 matches
Mail list logo