phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Loknath Priyatham Teja Singamsetty (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3114) PhoenixMRJobSubmitter fails to create async secondary indexes after PHOENIX-2966
Date Tue, 02 Aug 2016 16:38:20 GMT


Loknath Priyatham Teja Singamsetty  commented on PHOENIX-3114:

[~rvaleti] Yes, after the PHOENIX-2966 refactoring changes, the async secondary index started
failing and hence this bug is created. This was discussed and conveyed to James and Thomas.
I have updated the subject and description to include PHOENIX-2966 to clearly signify the

However, the existing builds passed successfully and unit tests were passing giving the wrong
impression that the refactored changes are done correctly. Only during manual testing, was
able to find the async secondary index functionality was broken and placed my observations
here. There is need to add more tests to cover complete functionality. Created PHOENIX-3115
and working on the same.

> PhoenixMRJobSubmitter fails to create async secondary indexes after PHOENIX-2966
> --------------------------------------------------------------------------------
>                 Key: PHOENIX-3114
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.8.0
>            Reporter: Loknath Priyatham Teja Singamsetty 
>            Assignee: Loknath Priyatham Teja Singamsetty 
>             Fix For: 4.8.0
>         Attachments: phoenix-3114.patch
> After the refactoring done as part of PHOENIX-2966, The INDEX_TYPE column is missing
in the ASYNC_SECONDARY_INDEX query to fetch the async index rows from system.catalog table.
This is being used inside PhoenixMRJobSubmitter. Unfortunately, the existing async secondary
index test cases for phoenix-mr-automation are succeeding. Created separate JIRA for writing
e2e test for secondary indexes
> 2016-07-25 07:36:10,744 DEBUG [8ff-shared--pool2-t1] security.HBaseSaslRpcClient - Will
read input token of size 32 for processing by initSASLContext
> 2016-07-25 07:36:10,745 DEBUG [8ff-shared--pool2-t1] security.HBaseSaslRpcClient - Will
send token of size 32 from initSASLContext.
> 2016-07-25 07:36:10,745 DEBUG [8ff-shared--pool2-t1] security.HBaseSaslRpcClient - SASL
client context established. Negotiated QoP: auth
> Exception in thread "main" org.apache.phoenix.schema.ColumnNotFoundException: ERROR 504
(42703): Undefined column. columnName=INDEX_TYPE
> 	at org.apache.phoenix.compile.RowProjector.getColumnIndex(
> 	at org.apache.phoenix.jdbc.PhoenixResultSet.findColumn(
> 	at org.apache.phoenix.jdbc.PhoenixResultSet.getByte(
> 	at org.apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter.getCandidateJobs(
> 	at org.apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter.scheduleIndexBuilds(
> 	at org.apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter.main(

This message was sent by Atlassian JIRA

View raw message