phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3394) Handle SequenceResolving through ConnectionQueryServices interface
Date Fri, 11 Nov 2016 00:39:58 GMT


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:
>             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
> {code}
> Caused by: java.lang.UnsupportedOperationException
> 	at org.apache.phoenix.query.ConnectionlessQueryServicesImpl.getTable(
> 	at org.apache.phoenix.query.DelegateConnectionQueryServices.getTable(
> 	at org.apache.phoenix.execute.MutationState.getHTable(
> 	at org.apache.phoenix.iterate.TableResultIterator.<init>(
> 	at org.apache.phoenix.iterate.DefaultTableResultIteratorFactory.newIterator(
> 	at org.apache.phoenix.iterate.ParallelIterators.submitWork(
> 	at org.apache.phoenix.iterate.BaseResultIterators.getIterators(
> 	... 71 more
> {code}

This message was sent by Atlassian JIRA

View raw message