You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2016/07/21 18:57:20 UTC

[jira] [Created] (PHOENIX-3108) ImmutableIndexIT fails when run on its own

Samarth Jain created PHOENIX-3108:
-------------------------------------

             Summary: ImmutableIndexIT fails when run on its own
                 Key: PHOENIX-3108
                 URL: https://issues.apache.org/jira/browse/PHOENIX-3108
             Project: Phoenix
          Issue Type: Bug
            Reporter: Samarth Jain
            Assignee: Thomas D'Silva


[~prakul] and I noticed that when running ImmutableIndexIT on its own, the test fails for parameters localIndex = true and transactional = false. The failure stacktrace is:

My first guess is that the UPSERT SELECT running for building the local index isn't setting timestamp correctly. This is probably causing the select part to read the records that are being upserted. FYI, [~rajeshbabu]. 


There is another bug in the test class - because it wants custom co-processor to be installed, the test class should extend BaseOwnClusterHBaseManagedTimeIT. In fact, any test that wants custom server side property should spawn its own mini-cluster which is what would end up happening if you extend BaseOwnClusterHBaseManagedTimeIT. 
Otherwise, running tests via mvn install may not install the co-processor and the test case, specifically testCreateIndexDuringUpsertSelect, isn't testing out the race condition like it should. FYI, [~tdsilva]. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)