Hi , all
I use Phoenix4.8.1 to mapping a hbase0.98 table, while I put a 0
(tinyInt) to hbase, the phoenix read as -80,
Has any one had seen this problem yet?
Thx~
From: BiaoMa
Hi Ashish,
Looks like transaction manager may not be running. Is the transaction
manager running? If so, can you look into the transaction manager log to
see if there are any errors?
Thanks,
Poorna.
On Thu, Nov 3, 2016 at 10:20 AM, ashish tapdiya
wrote:
> Hi,
>
> I
It sounds like PHOENIX-3178, but if not, please file a new JIRA with a way
to reproduce it. Patches are most welcome too, of course.
Thanks,
James
On Thu, Nov 3, 2016 at 4:38 PM, Julian Jaffe
wrote:
> When I execute an upsert with filters through the Phoenix JDBC
When I execute an upsert with filters through the Phoenix JDBC connector,
preparedStatement.executeUpdate returns ~2x the number of executed rows. If
the upsert doesn't change the filtered columns, the number it returns is
stable within a codebase (i.e. I am attempting to update 10 rows,
Hi,
I have tried loading data in a transactional table using psql.py and
mapreduce loader and both result in errors
1. psql.py error:
ERROR util.CSVCommonsLoader: Error upserting record
2. map-reduce based loader
16/11/03 22:45:01 INFO mapreduce.Job: Task Id :
Awesome, Lukas! Thanks so much - this is great!
On Thu, Nov 3, 2016 at 2:14 PM, Lukáš Lalinský wrote:
> Hello,
>
> I have released new version of the Python client library for working with
> Phoenix. Thanks to Mark Heppner it now uses the Protocol Buffers interface
> instead
Hello,
I have released new version of the Python client library for working with
Phoenix. Thanks to Mark Heppner it now uses the Protocol Buffers interface
instead of JSON, which fixes some issues with Phoenix 4.8. Additionally,
this version supports both Python 2 and Python 3.
Since these were
I am testing some code using Phoenix Spark plug in to read a Phoenix table with
a namespace prefix in the table name (the table is created as a phoenix table
not a hbase table), but it returns an TableNotFoundException.
The table is obviously there because I can query it using plain phoenix