[
https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070245#comment-15070245
]
Poorna Chandra commented on PHOENIX-2525:
-----------------------------------------
[~jamestaylor] Read pointer is the largest committed write pointer at any given
time. It gives us the boundary to filter committed transactions and in-progress
transactions. It is the write pointer that is in sync with the time when it was
generated (though it is an implementation detail).
Just curious, why do you expect read pointer to be in sync with current time?
> Views on transactional tables return no rows
> --------------------------------------------
>
> Key: PHOENIX-2525
> URL: https://issues.apache.org/jira/browse/PHOENIX-2525
> Project: Phoenix
> Issue Type: Bug
> Reporter: Mujtaba Chohan
> Assignee: Thomas D'Silva
> Attachments: PHOENIX-2525-v2.patch, PHOENIX-2525-v3.patch,
> PHOENIX-2525-v4.patch, PHOENIX-2525-wip.patch, PHOENIX-2525.patch
>
>
> Aggregate or non-aggregate queries do not return any rows to the client for
> views created over transactional table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
