[
https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068947#comment-15068947
]
James Taylor commented on PHOENIX-2525:
---------------------------------------
Running UPDATE STATISTICS shouldn't be impacted by the table being
transactional.
bq. The commit is required because we only resolve a table once during a
transaction. If we commit it forces the table to be re-resolved.
The MetaDataClient.updateStatisticsInternal() call should should either send
over the SCN if it's set or LATEST_TIMESTAMP if not set. Keep the resolution of
the <table> on which UPDATE STATISTICS is running, but don't use the timestamp
at which it was resolved - you should be able to muck with the TableRef we
create there to get this logic worked out.
bq. The clientTimeStamp to HConstants.LATEST_TIMESTAMP is required
The clientTimeStamp should be controlled by the client. I believe if you make
the above changes, then LATEST_TIMESTAMP will be passed through here on the
server side and you won't need to hard code it.
> 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)
