You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/03/02 02:19:19 UTC
[jira] [Commented] (PHOENIX-62) Precision loss for decimal type
when creation of Immutable Index happens after the record insertion
[ https://issues.apache.org/jira/browse/PHOENIX-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917249#comment-13917249 ]
James Taylor commented on PHOENIX-62:
-------------------------------------
[~maryannxue] - can you write a unit test for this?
> Precision loss for decimal type when creation of Immutable Index happens after the record insertion
> ---------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-62
> URL: https://issues.apache.org/jira/browse/PHOENIX-62
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 2.2.3
> Reporter: Maryann Xue
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Sql script:
> CREATE TABLE IF NOT EXISTS "Items"
> ("ItemID" VARCHAR(10) NOT NULL PRIMARY KEY,
> "ItemName" VARCHAR(50),
> "Price" DECIMAL)
> IMMUTABLE_ROWS=true;
> UPSERT INTO "Items" ("ItemID", "ItemName", "Price")
> VALUES ('I001', 'BX016', 15.96);
> CREATE INDEX IF NOT EXISTS "iItems" ON "Items"
> ("ItemName")
> INCLUDE
> ("Price");
> SELECT "ItemName", "Price" FROM "Items";
> Output:
> ItemName Price
> ---------- ----------
> BX016 15
> But if we put "CREATE INDEX ..." in front of "UPSERT INTO ...", the result comes out right as:
> ItemName Price
> ---------- ----------
> BX016 15.96
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)