As I mentioned about a week ago, I am working on a golang client using
protobuf serialization with the phoenix query server. I have
successfully dealt with the serialization of requests and responses.
However, I am trying to commit a transaction and just doesn't seem to
commit.
Here's what
Hey Mujtaba,
I was able to get it working. I think the addition of HBASE_HOME and
changing the way my entrypoint scripts in my docker container were being
called helped solved the issue.
Thanks again!
On 31/03/2016 11:38 PM, Mujtaba Chohan wrote:
Shouldn't be a bug there as it has been
Hi Josh,
Thanks a lot for the info. I began attempting to update Phoenix manually, but
after digging around a bit, I suspect Azure does some non-standard automagic
configuration that I shouldn't tamper with. I reached out to Azure for help
with the upgrade.
Thanks again,
Jared
-Original
For Phoenix phoenix.query.maxGlobalMemoryPercentage is 15% of heap
https://phoenix.apache.org/tuning.html. Block cache and memstore memory
setting are via usual HBase settings and their usage is exposed via jmx at
http://:60030/jmx. Was there any useful info in GC logs? Also 2GB
heap is on the low
Excellent, Vijay. Nice work - the APIs look very clean. We'll put up a page
on the Phoenix site that points folks toward this (and other Phoenix
add-ons).
James
On Thursday, March 31, 2016, Josh Mahonin wrote:
> This looks awesome, good work!
>
> On Thu, Mar 24, 2016 at
Shouldn't be a bug there as it has been working in our environment. To
verify can you please try this? Copy only tephra and tephra-env.sh files
supplied with Phoenix in a new directory with HBASE_HOME env variable set
and then run tephra.
Thanks,
Mujtaba
On Wed, Mar 30, 2016 at 9:59 PM, F21
Hi,
I have been trying to execute a upsert query that select data from a 10 mil
records table. The query fails on the sqlline client at times with Caused
by: java.lang.RuntimeException: Could not get page at index: 16.
The detailed exception is pasted here - http://pastebin.com/1wTCHyJM.
I tried
Hi All,
We have noticed an issue with performance of secondary index in Phoenix
4.7. Consider main table ACT with primary key (K1, K2, K3, K4) and Non PK
columns (M1, M2) and secondary index of form -
CREATE INDEX IF NOT EXISTS act_idx ON ACT(K1, K4, K3, K2);
Query in our use case is -
select