phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maddineni Sukumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3910) Tests in UpgradeIT failing after PHOENIX-3823
Date Tue, 06 Jun 2017 21:47:18 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039711#comment-16039711
] 

Maddineni Sukumar commented on PHOENIX-3910:
--------------------------------------------

Thanks [~jamestaylor] . Sorry for the delay. Injured my Knee last weekend and running around
hospitals and labs. 

Looked into it and found that our force update cache for every upsert select on same table
logic causing this error in case of upgrade i.e.
When we upgrade table we are doing upsert select on SYSCAT table and our logic to force update
cache coming into picture and then when we do force update cache for SYSCAT it is resulting
TABLE_ALREADY_EXISTS result with result table null. 

I think we dont need force update cache for SYSCAT as this META table and also we cannot configure
UPDATE_CACHE_FREQUECNY for SYSCAT.    [~jamestaylor] / [~samarthjain]  ,  correct me if we
need above upsert select logic on SYSCAT also.  If you are fine with this then I will submit
patch with ignoring force update SYSCAT during upsert select .

> Tests in UpgradeIT failing after PHOENIX-3823
> ---------------------------------------------
>
>                 Key: PHOENIX-3910
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3910
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Maddineni Sukumar
>             Fix For: 4.11.0
>
>
> [~sukunaidu@gmail.com], can you please take a look? 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message