Hi,
I am using HDP 2.6 hbase and pheonix. I created a play rest service using
hbase as the backend. However, I have trouble to get a working pheonix
client.
I tried the pheonix-client.jar given by HDP but it has multiple conflicts
with play, for example logback v.s. log4j, guava 13 v.s. guava
Thanks for bringing this to our attention. There's a bug here in that the
SYSTEM.STATS table has a custom split policy that prevents splitting from
occurring (PHOENIX-4700). We'll get a fix out in 4.14, but in the meantime
it's safe to split the table, as long as all stats for a given table are on
Thanks for bringing this to our attention. There's a bug here in that the
SYSTEM.STATS
On Wed, Apr 18, 2018 at 9:59 AM, Batyrshin Alexander <0x62...@gmail.com>
wrote:
> Hello,
> I've discovered that SYSTEM.STATS has only 1 region with size 3.25 GB. Is
> it ok to split it and distribute over
Ron - Salting is only recommended when your primary key is monotonically
increasing. It's mainly used to prevent write hotspotting. Also, I think
Ron forgot to mention, but I was working with him a bit earlier on this,
and I couldn't repro the issue either (in current 4.x or in 4.7 release).
We have a bit more of a stack trace for our bind parameter exception, not sure
if this is very revealing but we have: java.lang.RuntimeException:
java.sql.SQLException: ERROR 2004 (INT05): Parameter value unbound. Parameter
at index 1 is unbound
Hello Sergey,
Per your request, here are the commands that I used to create the table and its
indexes. Hopefully you can find something in here that provides a guide as to
what we are doing wrong.
BTW – as I said, we are novices with Phoenix here. One thing we are doing is
playing around a
Hi Ron,
Best place to ask questions about a JIRA is on the JIRA itself. If you see
no activity on it for a long time, it often means that no one in the
community has had time to fix it. This probably indicates that it's not as
high priority as other JIRAs that have been fixed. This, of course, is
Hello James,
I did a search using PHOENIX-1544 and could not find any updates to your June
2015 post on the Phoenix list, so I wanted to ask: what is the current status
for indexing array fields over immutable (or even mutable) tables? We could
certainly use such.
Ron
On 2015/06/21 23:10:04,
I did some digging, and the reason is because I started PQS using JSON
serialization, rather than PROTOBUF.
When I switch to PROTOBUF serialization, the 'select * from testarray' query
works fine.
There is not type for numbers in Json, so an Json Array[100] is parsed to an
array containing
