[
https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068812#comment-15068812
]
James Taylor commented on PHOENIX-2525:
---------------------------------------
Good idea, [~tdsilva]. Looks like you left that extra commit in which I don't
think you need anymore:
{code}
+ // we need to commit here for transactional tables, so that the table
will be resolved (along with the new stats) for the next transaction
+ conn.commit();
{code}
Also, I don't think this change should be necessary:
{code}
- Scan s = MetaDataUtil.newTableRowsScan(tableNameBytes,
MetaDataProtocol.MIN_TABLE_TIMESTAMP, clientTimeStamp);
+ // always use the latest timestamp in order to view the latest
available stats
+ Scan s = MetaDataUtil.newTableRowsScan(tableNameBytes,
MetaDataProtocol.MIN_TABLE_TIMESTAMP, HConstants.LATEST_TIMESTAMP);
{code}
+1 after those changes.
> 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-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)
