Hi Ron, Looks like you did indeed find a bug. It looks to be occur during parsing and somehow -1.00 is getting converted into a BigInt instead of a BigDecimal like in all the other cases. I'll keep digging into this.
-Dave On Thu, Mar 19, 2015 at 7:34 AM, Ron van der Vegt < [email protected]> wrote: > Hi, > > Im trying to upsert some records to my phoenix table but i'm getting the > following error: > > Error: ERROR 203 (22005): Type mismatch. FLOAT and BIGINT for -1 > > It seems that only the value "-1.00" as float is causing this problem. > Please check the example sql below: > > CREATE TABLE test ( > id VARCHAR not null primary key, > name VARCHAR, > lat FLOAT > ); > > UPSERT INTO test(id,name,lat) VALUES ('testid', 'testname', -1.00); > > adding rows with values -2.00 or 3.00 is working without problems. Does > anybody knows why? Is the sign bit causing this error, and therefore I > found a bug? > > Phoenix version: 4.3.0 > Hbase version: 0.98.10.1 > > Thanks in advice, > > Ron >
