[
https://issues.apache.org/jira/browse/PHOENIX-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655668#comment-15655668
]
James Taylor commented on PHOENIX-3394:
---------------------------------------
How do you know when to call SchemaManager.reset() then? Seems like something
may be missing on the Calcite side to hook into the Statement lifecycle. FYI,
that's probably why the CURRENT VALUE FOR <seq> is acting differently than
Phoenix.
You might be able to put the SequenceManager in the StatementContext as its
lifecycle is similar to a Statement lifecycle (except you can execute a
Statement multiple times and you get a new StatementContext each time).
> Handle SequenceResolving through ConnectionQueryServices interface
> ------------------------------------------------------------------
>
> Key: PHOENIX-3394
> URL: https://issues.apache.org/jira/browse/PHOENIX-3394
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Eric Lomore
> Assignee: Eric Lomore
>
> Tons of unit tests have this same stack trace. It appears that this call
> shouldn't reach ConnectionlessQueryServicesImpl.getTable?
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.phoenix.query.ConnectionlessQueryServicesImpl.getTable(ConnectionlessQueryServicesImpl.java:157)
> at
> org.apache.phoenix.query.DelegateConnectionQueryServices.getTable(DelegateConnectionQueryServices.java:70)
> at
> org.apache.phoenix.execute.MutationState.getHTable(MutationState.java:360)
> at
> org.apache.phoenix.iterate.TableResultIterator.<init>(TableResultIterator.java:101)
> at
> org.apache.phoenix.iterate.DefaultTableResultIteratorFactory.newIterator(DefaultTableResultIteratorFactory.java:33)
> at
> org.apache.phoenix.iterate.ParallelIterators.submitWork(ParallelIterators.java:104)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getIterators(BaseResultIterators.java:871)
> ... 71 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
