[
https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva updated PHOENIX-2525:
------------------------------------
Attachment: PHOENIX-2525.patch
[~jamestaylor]
Can you please review?
In addition to calling commit after UPDATE STATS for transactional tables, I
had to change the max timestamp of the scan StatisticsUtil.readStatistics()
to clientTimeStamp +1. This is because the stats gets written with the previous
txn write pointer, which becomes the current txn read pointer , which is what
clientTimeStamp is set to. I am not sure if this change will affect connections
with an scn set.
{code}
Scan s = MetaDataUtil.newTableRowsScan(tableNameBytes,
MetaDataProtocol.MIN_TABLE_TIMESTAMP, clientTimeStamp!=
HConstants.LATEST_TIMESTAMP ? clientTimeStamp +1 : clientTimeStamp);
{code}
> 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-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)
