[ 
https://issues.apache.org/jira/browse/PHOENIX-6878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710427#comment-17710427
 ] 

Richárd Antal commented on PHOENIX-6878:
----------------------------------------

Hi [~srikanth1184] 

I wrote a unittest to test tables with ROW_TIMESTAMP with and without 
phoenix.acls.enabled enabled, and I could not Identify slowness, however with 
and without PHOENIX-6395 there is a huge difference.

What version of phoenix are you using?

When phoenix.acls.enabled=true and without the fix for PHOENIX-6395 reduces the 
performance drastically. Can you check if you have PHOENIX-6395 in your product?

> Upserts into tables with ROW_TIMESTAMP are extremely slow
> ---------------------------------------------------------
>
>                 Key: PHOENIX-6878
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6878
>             Project: Phoenix
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 5.2.0, 5.1.3
>            Reporter: Istvan Toth
>            Priority: Minor
>
> PHOENIX-4187 changed upserts into tables with ROW_TIMESTAMP fields to always 
> refresh the table cache before executing the mutation.
> This kills non batched write performance for such tables, as the Table 
> metadata is re-read for every row.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to