[
https://issues.apache.org/jira/browse/PHOENIX-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512757#comment-14512757
]
Thomas D'Silva commented on PHOENIX-1881:
-----------------------------------------
The"data.tx.allow.empty.values" property that tephra uses to not treat empty
values as a DELETE must be set on the server side (since it is read from the
TransactionProcessor coprocessor). Since STORE_NULLS is a table property, how
should we handle this? Should we just not allow setting STORE_NULLS to true for
a transactional table (since STORE_NULLS is used for flashback queries which
are not currently supported by transactional tables)?
> Set value in our empty key value to Tephra won't treat it like a column delete
> ------------------------------------------------------------------------------
>
> Key: PHOENIX-1881
> URL: https://issues.apache.org/jira/browse/PHOENIX-1881
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Thomas D'Silva
>
> Tephra interprets an empty column value as a Column delete. We don't want
> this to be the case for our empty KeyValue. Since we're only allowing a new
> table to be set as transactional, let's set the value in our empty KeyValue
> for transactional tables to a single byte. Then we can undo the change I made
> to force STORE_NULLS to be true for transactional tables (in MetaDataClient).
> In addition, we can set the TransactionAwareHTable flag to *not* treat an
> empty value as a delete if STORE_NULLS is true.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
