[
https://issues.apache.org/jira/browse/PHOENIX-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891893#comment-13891893
]
James Taylor commented on PHOENIX-15:
-------------------------------------
For your patch, rather than introduce a new flush method, I think it might be
better to hide this in ConnectionQueryServices.addColumn. Also, you'll need to
modify the upsert code as mentioned above. We'll need to strip Delete markers
from tableMetaData in this case too (or just not set the value if it's null).
It's kind of a pain to conditionally set it. We could break it up into multiple
upsert statements, I suppose.
> 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.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.
> [~giacomotay...@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)
