You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2014/02/03 06:54:09 UTC

[jira] [Commented] (PHOENIX-15) Allow forcing a memstore flush for a table

    [ https://issues.apache.org/jira/browse/PHOENIX-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889244#comment-13889244 ] 

Lars Hofhansl commented on PHOENIX-15:
--------------------------------------

For this, can't we make our own syntax? Something "FLUSH <table>"?

It's not really tied to a session but to a table. For ALTER SESSION FLUSH we would have to keep track of exactly what tables were modified in the session since the last time we flushed.

Alternatively we could enforce that {{ALTER TABLE <t> SET disableWAL = false}} automatically flushes the table, since this is the really the only point in Phoenix where one would actually want to flush a table's memstores to disk.


> 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.
> [~giacomotaylor@gmail.com] 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)