The Apache Phoenix team is pleased to announce release of it's next major
version 5.0.0
compatible with HBase 2.0+. Apache Phoenix enables SQL-based OLTP and
operational
analytics for Apache Hadoop using Apache HBase as its backing store and
providing
integration with other projects in the Apache
Thanks so much for your response.
Now I am getting better perforamnce i.e 15K per minute, I made two changes.
I disabled pheonix transaction.
phoenix.transactions.enabled
false
And I removed the transaction connection.commit(); Logically this should
not make any difference because by
Sorry, I was brief and didn't get my point across. I meant to say the
same thing you did.
Someone manually submitting two updates to an index is naively faster
that what Phoenix goes through to automatically (and safely) do this.
On 7/13/18 12:07 PM, James Taylor wrote:
Phoenix won’t be
Phoenix won’t be slower to update secondary indexes than a use case would
be. Both have to do the writes to a second table to keep it in sync.
On Fri, Jul 13, 2018 at 8:39 AM Josh Elser wrote:
> Also, they're relying on Phoenix to do secondary index updates for them.
>
> Obviously, you can do
Also, they're relying on Phoenix to do secondary index updates for them.
Obviously, you can do this faster than Phoenix can if you know the exact
use-case.
On 7/12/18 6:31 PM, Pedro Boado wrote:
A tip for performance is reusing the same preparedStatement , just
clearParameters() , set values
