[
https://issues.apache.org/jira/browse/PHOENIX-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906315#comment-13906315
]
James Taylor commented on PHOENIX-15:
-------------------------------------
It's really the same - your calling flush from the addColumn method of
MetaDataClient and I'm calling it one level below in the addColumn method of
ConnectionQueryServicesImpl. Because I'm calling it in the lower level method,
there's no need to surface a flushTable method in ConnectionQueryServices. This
is simpler.
If/when we introduce a FLUSH command, then I agree, we can add the flushTable
method to the ConnectionQueryServices interface. Until then, though, we don't
need it. I'm trying to keep this interface to a minimum.
> 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)
