[
https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4849:
---
Attachment: PHOENIX-4849-all.patch
> UPSERT SELECT fails with stale region boundary excepti
[
https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4849:
---
Affects Version/s: (was: 4.13.0)
4.14.0
> UPSERT SELECT fails wi
[
https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4849:
---
Affects Version/s: 4.13.0
> UPSERT SELECT fails with stale region boundary exception after
[
https://issues.apache.org/jira/browse/PHOENIX-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl reassigned PHOENIX-4885:
--
Assignee: Lars Hofhansl
> After HBASE-20940 any local index query will open all HFil
[
https://issues.apache.org/jira/browse/PHOENIX-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4885:
---
Attachment: PHOENIX-4885-master.01.patch
> After HBASE-20940 any local index query will ope
100% agreement.
A bit worried about "boiling the ocean" and risking not getting done anything.
Speaking of modules. I would *love* if we had a simple HBase abstraction API
and then a module for each version of HBase, rather than a different branch
each.Most differences are presumably in coproces
I will point out that the thin client can have advantages too:1. The query
engine pool can be sized independently of clients and region servers now.2.
Appropriate machine/VM configurations can be picked that are optimal for query
execution.3. Client and (region) servers can be upgraded entirely
