[
https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731602#comment-16731602
]
Lars Hofhansl edited comment on PHOENIX-5084 at 1/1/19 2:14 PM:
----------------------------------------------------------------
Hmm... The more I think about this, the more it is wrong to start a transaction
in updateCache, we need to find a different solution! Metadata queries should
not affect running transactions at all.
About about this:
We check whether a transaction is already open. If so we use that one for
resolving, which is the right thing to do anyway. If no transaction is open we
open a new one *and* close it (or perhaps resolve the table(s) without any
transaction.)
That way the metadata operations are transaction neutral.
was (Author: lhofhansl):
Hmm... The more I think about this, the more it is wrong to start a transaction
in updateCache, we need to find a different solution! Metadata queries should
not affect running transactions at all.
About about this:
We check whether a transaction is already open. If so we use that one for
resolving, which is the right thing to do anyway. If no transaction is open we
either open a new one *and* close it (or perhaps resolve the table(s) without
any transaction.)
That way the metadata operations are transaction neutral.
> 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
> Assignee: Lars Hofhansl
> Priority: Blocker
> Attachments: PHOENIX-5084-v2.txt, PHOENIX-5084.txt
>
>
> 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)
