[
https://issues.apache.org/jira/browse/PHOENIX-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156588#comment-16156588
]
Samarth Jain commented on PHOENIX-4176:
---------------------------------------
Good idea, [~rajeshbabu]. In this case, we would need to execute a SELECT
COUNT(1) query which would pass down to the co-processor as scan attribute the
column families we are expecting. And then on the client side, we could
basically retry when a column family not found exception is thrown. One
question, when regions are being opened, does HBase client retry the scanner
rpc transparently?
> Reduce chances of tests flapping with ColumnFamilyNotFoundException for HBase
> 1.x
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-4176
> URL: https://issues.apache.org/jira/browse/PHOENIX-4176
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Attachments: PHOENIX-4176.patch, PHOENIX-4176_v2.patch
>
>
> In HBase 1.x, when adding a new column family, the check to detect whether
> the HTableDescriptor is updated isn't enough. Tests that add a new column
> family run the risk of flapping when number of regions on the table are high
> (since the column family has to be added to all the regions). Till we figure
> out a permanent solution for this, we can possibly decrease chances of such
> tests from flapping by reducing number of regions/pre-splits and possibly
> configuring hbase.online.schema.update.enable to false in our tests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
