[
https://issues.apache.org/jira/browse/PHOENIX-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved PHOENIX-4892.
-
Resolution: Fixed
Fix Version/s: 5.1.0
4.15.0
Thanks for the change,
[
https://issues.apache.org/jira/browse/PHOENIX-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy updated PHOENIX-4909:
-
Description: Missing the phoenix-loadbalancer module dependency in
phoenix-assembly/pom.xml. Also need
Vitaliy created PHOENIX-4909:
Summary: Missing the phoenix-loadbalancer module dependency in
phoenix-assembly/pom.xml
Key: PHOENIX-4909
URL: https://issues.apache.org/jira/browse/PHOENIX-4909
Project: Pho
[
https://issues.apache.org/jira/browse/PHOENIX-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Shi updated PHOENIX-4008:
-
Description: In order to truly measure the size of data when calculating
guide posts, UPDATE STATISTIC
[
https://issues.apache.org/jira/browse/PHOENIX-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved PHOENIX-4903.
-
Resolution: Fixed
Fix Version/s: 5.1.0
4.15.0
> HashCache recreated o
Sandeep Nemuri created PHOENIX-4908:
---
Summary: [Apache Spark Plugin Doc] update save api when using
spark dataframe
Key: PHOENIX-4908
URL: https://issues.apache.org/jira/browse/PHOENIX-4908
Project:
>
> I don't understand what performance issues you think exist based solely on
> the above. Those numbers appear to be precisely in line with my
> expectations. Can you please describe what issues you think exist?
>
1. Performance of the thick client has almost 1~4 time higher than the thin
client
Hi,
I have two salted global secondary indexes (A and B) on a table with row
key (primary key) as the covered column. For both of them, the read single
row latency is fine with less QPS, but as QPS increases from the client
side, query on one of the indexes (A) becomes 10x slow, while the
other (B
