phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Hacker <dhac...@salesforce.com>
Subject Re: Type mismatch. FLOAT and BIGINT for -1
Date Wed, 25 Mar 2015 21:58:42 GMT
Hi Ron,

I've just submitted a patch for this.  It should make it into the upcoming
4.3.1 patch.  If you need the fix sooner you can find the patch here.
https://issues.apache.org/jira/browse/PHOENIX-1776

-Dave

On Thu, Mar 19, 2015 at 2:52 PM, David Hacker <dhacker@salesforce.com>
wrote:

> 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 <
> ron.van.der.vegt@openindex.io> 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
>>
>
>

Mime
View raw message