[
https://issues.apache.org/jira/browse/PHOENIX-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906780#comment-13906780
]
Hudson commented on PHOENIX-15:
-------------------------------
ABORTED: Integrated in Apache Phoenix - Branch:master #60 (See
[https://builds.apache.org/job/Phoenix/60/])
PHOENIX-15 Allow forcing a memstore flush for a table (Lars Hofhansl)
(jamestaylor: rev c23c60ee1adf52b952fe70ce9b4d6bf628569b1b)
*
phoenix-core/src/test/java/org/apache/phoenix/end2end/ConnectionQueryServicesTestImpl.java
*
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
*
phoenix-core/src/test/java/org/apache/phoenix/end2end/BaseConnectedQueryTest.java
> 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)
