sqlline reporting 1 row affected when it isn't

Any idea why sqlline would report 1 row affected when I delete no rows? 0: jdbc:phoenix:172.xx.xx.xxx> create table names (id bigint(20) primary key, name varchar(20)); No rows affected (1.158 seconds) 0: jdbc:phoenix:172.xx.xx.xxx> delete from names where id=1; 1 row affected (0.204 seconds) 0:

Re: sqlline reporting 1 row affected when it isn't

Is not the output the number of lines of the delete command, which is one line (the command itself) and not the number of deleted lines? Can you try to put some rows into the table and do the delete again? Or try without the where close too? 2015-09-02 9:54 GMT-04:00 James Heather : > Any idea w

Re: sqlline reporting 1 row affected when it isn't

https://issues.apache.org/jira/browse/PHOENIX-2223 James On 02/09/15 15:09, Jean-Marc Spaggiari wrote: Yep, now I can only totally agree with you. I think you should open a JIRA. 2015-09-02 10:05 GMT-04:00 James Heather >: I think this is enough to dem

Re: sqlline reporting 1 row affected when it isn't

I think this is enough to demonstrate that there's an issue. Deleting without the 'where' clause returns (correctly) no rows affected when there's nothing there. Using a '<=' operator in the 'where' clause seems to report the right values (2 when it deletes 2 rows, 0 when it deletes 0 rows). Go

Re: sqlline reporting 1 row affected when it isn't

Yep, now I can only totally agree with you. I think you should open a JIRA. 2015-09-02 10:05 GMT-04:00 James Heather : > I think this is enough to demonstrate that there's an issue. Deleting > without the 'where' clause returns (correctly) no rows affected when > there's nothing there. Using a '

Re: sqlline reporting 1 row affected when it isn't

Thanks for filing the JIRA, James. This is actually working as designed. See my comments here: https://issues.apache.org/jira/browse/PHOENIX-2223?focusedCommentId=14727548&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14727548 On Wed, Sep 2, 2015 at 7:20 AM, James H

org.apache.phoenix.execute.CommitException: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException

Hi, I'm here again. Wrote local unit-tests, all works perfectly. Started to run smokes on production and can't reach great success. What this exception means? My ddl is: CREATE TABLE IF NOT EXISTS cross_id_attributes ( crossIdVARCHAR NOT NULL CONSTRAINT cross_id_reference_pk

Re: org.apache.phoenix.execute.CommitException: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException

I can describe table using sqlline from phoenix, but can't query the table: select crossid from CROSS_ID_ATTRIBUTES limit 1; just hungs and when I try to interrupt utility, I see "a kind o exception" Exception in thread "SIGINT handler" java.lang.RuntimeException: java.sql.SQLFeatureNotSupported

performance script with 100M rows failed at last hurdle

I tried to run ./performance.py 1 this afternoon. It seemed to die just before the end, so that I got very nearly, but not quite, 100M rows inserted. The last 530 were missing. The stack trace suggested that the zookeeper connection died. It had taken 5h30m by that point (because I'

Re: sqlline error while creating table

No, problem is other: DATA_BLOCK_ENCODING='SNAPPY' doesn't for for some reason. 1. I can't execute such DDL from sqlline 2. I can execute it via JDBC, but I can't query on insert into this table... 2015-09-01 23:35 GMT+02:00 Serega Sheypak : > Thanks, I'll try. > it's tempale query, it work