[
https://issues.apache.org/jira/browse/PHOENIX-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891889#comment-13891889
]
James Taylor commented on PHOENIX-15:
-------------------------------------
When we do an alter table, we set the disableWal to what it was before or to
the new value if it's changed. For your purposes, it'd be better if we didn't
set it unless it changed. To do that, you'd need to use a Boolean instead of a
boolean and only set it if the value is changing. In the UPSERT statement in
incrementTableSeqNum, you'd need to do a tableUpsert.setNull(8, Types.BOOLEAN);
in the case of null.
FWIW, we have helper functions in MetaDataUtil.getMutationKVByteValue that'll
search the tableMetaData just so you don't have to re-invent it (for when you
want to see if disableWal is being set to false).
For multi-tenant, not sure what the best way to handle would be. Flush part of
the table, or like you said identify the particular regions to flush. Not sure
this functionality would be used for multi-tenant tables.
> 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.
> [[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)
