You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Loknath Priyatham Teja Singamsetty (JIRA)" <ji...@apache.org> on 2016/08/02 16:52:20 UTC
[jira] [Comment Edited] (PHOENIX-3114) PhoenixMRJobSubmitter fails
to create async secondary indexes after PHOENIX-2966
[ https://issues.apache.org/jira/browse/PHOENIX-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404339#comment-15404339 ]
Loknath Priyatham Teja Singamsetty edited comment on PHOENIX-3114 at 8/2/16 4:51 PM:
--------------------------------------------------------------------------------------
[~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 that time itself. I have updated the subject and description now to include PHOENIX-2966 to clearly signify the timeline.
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.
was (Author: singamteja):
[~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 timeline.
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: https://issues.apache.org/jira/browse/PHOENIX-3114
> 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(RowProjector.java:159)
> at org.apache.phoenix.jdbc.PhoenixResultSet.findColumn(PhoenixResultSet.java:178)
> at org.apache.phoenix.jdbc.PhoenixResultSet.getByte(PhoenixResultSet.java:334)
> at org.apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter.getCandidateJobs(PhoenixMRJobSubmitter.java:151)
> at org.apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter.scheduleIndexBuilds(PhoenixMRJobSubmitter.java:179)
> at org.apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter.main(PhoenixMRJobSubmitter.java:272)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)