[
https://issues.apache.org/jira/browse/PHOENIX-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220476#comment-14220476
]
Samarth Jain commented on PHOENIX-1466:
---------------------------------------
[~jamestaylor] - do you expect delegate to be seen by multiple threads? In
other words do you expect tableResultIterator.next() to be called concurrently
with tableResultIterator.close()? If yes, then you would need explicit locking
to make sure only one thread can call one of the two methods. If you expect one
thread to call delegate.next() and another thread to call delegate.close() but
not at the same time, then at you would need to make delegate at least
volatile.
> Prevent multiple scans when query run serially
> ----------------------------------------------
>
> Key: PHOENIX-1466
> URL: https://issues.apache.org/jira/browse/PHOENIX-1466
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Attachments: PHOENIX-1466.patch, PHOENIX-1466_v2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
