[
https://issues.apache.org/jira/browse/PHOENIX-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rejeb ben rejeb updated PHOENIX-7377:
-
Flags: Important
Language: Java Scala
> phoenix5-spark dataframe issue with sche
This is a cleanup before the 2.0.0 release.
The umbrella issue is HBASE-18169, the issue for WALObserver is HBASE-19074.
I think the intention here is to not expose too many internal states
to CP users which may mess things up, like changing the memstore size
without adding any actual data...
Is
For me, since we have already exposed WALKey(which is already an
interface which only allow adding attributes) and WALEdit(which we do
allow adding customized cells to it) in other coprocessor interface
like RegionObserver, it does not make sense to remove these methods in
WALObserver just because
[
https://issues.apache.org/jira/browse/PHOENIX-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kadir Ozdemir reassigned PHOENIX-7382:
--
Assignee: Kadir Ozdemir
> Eliminating index building and treating max lookback as TT
Kadir Ozdemir created PHOENIX-7382:
--
Summary: Eliminating index building and treating max lookback as
TTL for CDC Index
Key: PHOENIX-7382
URL: https://issues.apache.org/jira/browse/PHOENIX-7382
Proje
Tanuj Khurana created PHOENIX-7383:
--
Summary: Unify in-memory representation of Conditional TTL
expressions and Literal TTL values
Key: PHOENIX-7383
URL: https://issues.apache.org/jira/browse/PHOENIX-7383
