[ 
https://issues.apache.org/jira/browse/PHOENIX-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Lomore updated PHOENIX-3441:
---------------------------------
    Description: 
This is similar to PHOENIX-3394 in that rs.next() is causing unit tests to 
fail. It looks like DELETE statements end up in PhoenixTableModify.deleteRows() 
which ultimately tries to use a ResultSet, and hence 
ConnectionlessQueryServicvesImpl.getTable()

{{conn.createStatement().execute("DELETE FROM t1 WHERE k=2")}}
{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:361)
        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:860)
        ... 62 more
{code}

  was:
This is similar to the resolveSequence issue in that rs.next() is causing unit 
tests to fail. It looks like DELETE statements end up in 
PhoenixTableModify.deleteRows() which ultimately tries to use a ResultSet, and 
hence ConnectionlessQueryServicvesImpl.getTable()

{{conn.createStatement().execute("DELETE FROM t1 WHERE k=2")}}
{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:361)
        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:860)
        ... 62 more
{code}


> PhoenixTableModify calls on ResultSet for unit tests
> ----------------------------------------------------
>
>                 Key: PHOENIX-3441
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3441
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Eric Lomore
>
> This is similar to PHOENIX-3394 in that rs.next() is causing unit tests to 
> fail. It looks like DELETE statements end up in 
> PhoenixTableModify.deleteRows() which ultimately tries to use a ResultSet, 
> and hence ConnectionlessQueryServicvesImpl.getTable()
> {{conn.createStatement().execute("DELETE FROM t1 WHERE k=2")}}
> {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:361)
>       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:860)
>       ... 62 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to