[
https://issues.apache.org/jira/browse/PHOENIX-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906308#comment-13906308
]
Lars Hofhansl commented on PHOENIX-15:
--------------------------------------
Still seems cleaner to separate this from addColumn. It would be confusing
later I think.
addColumn adds a column and flushTable flushes a table :)
You are right, though, that the flushTable boolean is not needed since it is
equivalent to disableWAL != null && !disableWAL.
> 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
> Attachments: phoenix-15-v2.txt, phoenix-15-v3.txt, phoenix-15-v4.txt,
> phoenix-15.txt
>
>
> 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)
