phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-5061) PhoenixIndexImportDirectMapper doesn't set SCN right for indexes on transactional tables
Date Tue, 04 Dec 2018 22:23:00 GMT
Geoffrey Jacoby created PHOENIX-5061:
----------------------------------------

             Summary: PhoenixIndexImportDirectMapper doesn't set SCN right for indexes on
transactional tables
                 Key: PHOENIX-5061
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5061
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.14.1, 5.0.0
            Reporter: Geoffrey Jacoby


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)

Mime
View raw message