[
https://issues.apache.org/jira/browse/PHOENIX-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627246#comment-14627246
]
Samarth Jain commented on PHOENIX-2111:
---------------------------------------
Good point.
So we have two options then:
1) Would it then make sense to skip loading the parent table of a view
altogether if we are on an older client? Because of the bug in the previous
versions, we were never loading the parent table of a view. So the validation
of verifying the parent table's sequence number as well as whether the parent
table is deleted wasn't happening. This is what the previous behavior was.
2) We check whether the parent table was deleted but we don't compare the
parent table's sequence number.
I vote for 2).
> Race condition on creation of new view and adding of column to base table
> -------------------------------------------------------------------------
>
> Key: PHOENIX-2111
> URL: https://issues.apache.org/jira/browse/PHOENIX-2111
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Samarth Jain
> Attachments: PHOENIX-2111.patch
>
>
> There's currently a potential race condition between creating a view and
> adding a column to the base table. The logic to find the parent row key is
> incorrect for this scenario.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
