[
https://issues.apache.org/jira/browse/PHOENIX-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891877#comment-13891877
]
Lars Hofhansl commented on PHOENIX-15:
--------------------------------------
So looking at the code... Every time we do an alter table and add a column or
change another property we'd set disableWal back to false? That does not seem
right anyway.
Also, what does this mean for a multi tenant table? In HBase we can only flush
a physical table. So if one tenant reenables the WAL we'd flush the entire
table.
> Allow forcing a memstore flush for a table
> ------------------------------------------
>
> Key: PHOENIX-15
> URL: https://issues.apache.org/jira/browse/PHOENIX-15
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Lars Hofhansl
>
> This is useful with PHOENIX-14.
> I.e. one could do a "bulk load" without writing to the WAL, following by a
> memstore flush in order to guarantee the data is on disk.
> [[email protected]] suggested: ALTER SESSION FLUSH. And somehow we'd
> need to indicate which table to flush.
> This probably needs a bit more discussion.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)