[
https://issues.apache.org/jira/browse/HBASE-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-19033:
------------------------------
Attachment: HBASE-19033-v1.patch
Maybe something wrong in memory compaction...
In MemStoreCompactorSegmentsIterator.createScanner, the comment says 'Get all
available versions', but actually the old implementation will not read all
available versions, it just follow the ScanInfo for this store. In the previous
patch I reset the max versions to Integer.MAX_VALUE and lots of tests failed...
And also other problem but not very related, for
TestWalAndCompactingMemStoreFlush, we sometimes run into the unexpected code
path at line 1020, where it is an 'assert false'. Although the tests can pass
but I think this maybe a problem.
> Allow CP users to change versions and TTL before opening StoreScanner
> ---------------------------------------------------------------------
>
> Key: HBASE-19033
> URL: https://issues.apache.org/jira/browse/HBASE-19033
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19033-v1.patch, HBASE-19033.patch
>
>
> See the discussion in HBASE-19001. Changing versions and TTL is safe for
> flush/compaction so we can expose them.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
