[
https://issues.apache.org/jira/browse/PHOENIX-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709351#comment-16709351
]
Geoffrey Jacoby commented on PHOENIX-5061:
------------------------------------------
Another potential issue is that the TXN_SCN_VALUE is set in
IndexTool.JobBuilder by assuming that the SCN needs to be converted to nanos
for all transactional tables. I know that's the case for Tephra, but is that
also the case for Omid? It's been a year or two since I read up on Omid, but I
seem to remember it uses shadow column families rather than HBase timestamps to
do its work. [~jamestaylor] [~ohads]
> PhoenixIndexImportDirectMapper doesn't set correctly for indexes on
> transactional tables
> ----------------------------------------------------------------------------------------
>
> Key: PHOENIX-5061
> URL: https://issues.apache.org/jira/browse/PHOENIX-5061
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.14.1
> Reporter: Geoffrey Jacoby
> Priority: Major
>
> In PhoenixIndexImportDirectMapper, there's a section where the scn is set
> before getting the Phoenix connection.
> It appears the intention is to use a transactional scn value if one exists
> (it's set in IndexTool if a table's transactional), otherwise use a normal
> scn. However, the transactional scn value is never used.
> {code:java}
> final Properties overrideProps = new Properties();
> String scn = configuration.get(PhoenixConfigurationUtil.CURRENT_SCN_VALUE);
> String txScnValue = configuration.get(PhoenixConfigurationUtil.TX_SCN_VALUE);
> if(txScnValue==null) {
> overrideProps.put(PhoenixRuntime.BUILD_INDEX_AT_ATTRIB, scn);
> }
> connection = ConnectionUtil.getOutputConnection(configuration, overrideProps);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
