phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client
Date Sun, 30 Dec 2018 22:46:00 GMT

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

Lars Hofhansl commented on PHOENIX-5084:
----------------------------------------

Hmm... The fix is not immediately clear to me. updateCache() is called from all over the place.
Places where a transaction might be active, places where it is not. Do we *need* to start
a transaction from in there?

> Changes from Transactional Tables are not visible to query in different client
> ------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5084
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5084
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.0, 4.14.1
>            Reporter: Lars Hofhansl
>            Priority: Blocker
>
> Scenario:
> # Upsert and commit some data into a transactional table. (Autocommit or following by
explicit commit)
> # Query same table from another client
> The first query on the other client will not see the newly upserted/committed data (regardless
of how long one waits).
> A second identical query will see the new data.
> This happens with both Omid and Tephra.
> I guess we can't write a test for this, since it requires multiple JVMs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message