[
https://issues.apache.org/jira/browse/PHOENIX-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655712#comment-15655712
]
James Taylor commented on PHOENIX-3394:
---------------------------------------
Thanks, [~maryannxue] - forgot about the resolving schema issue. I think we can
make the requirement that namespaces are enabled. We can just fail at startup
if it's not. At some point, we should just get rid of the option to not have
namespaces on. It's getting to difficult to get good test coverage on all these
possible combinations of things being on/off.
> 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)
