You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Lars Hofhansl (Jira)" <ji...@apache.org> on 2019/11/05 06:44:00 UTC
[jira] [Comment Edited] (PHOENIX-5559) With short index ids, index
updates are with the same index id in 4.15.0
[ https://issues.apache.org/jira/browse/PHOENIX-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967292#comment-16967292 ]
Lars Hofhansl edited comment on PHOENIX-5559 at 11/5/19 6:43 AM:
-----------------------------------------------------------------
The attached tests shows the problems of both PHOENIX-5559 (the data is written to the *same* index, and hence show up multiple times) and PHOENIX-5550 (no data readable when an index is created on a data that contained data).
I verified that both tests pass with phoenix.index.longViewIndex.enabled set to true.
[~m2je], FYI.
was (Author: lhofhansl):
The attached tests shows the problems of both PHOENIX-5559 (the data is written to the *same* index, and hence show up multiple times) and PHOENIX-5550 (no data readable when an index is created on a data that contained data).
I verified that both tests pass with phoenix.index.longViewIndex.enabled set to true.
> With short index ids, index updates are with the same index id in 4.15.0
> ------------------------------------------------------------------------
>
> Key: PHOENIX-5559
> URL: https://issues.apache.org/jira/browse/PHOENIX-5559
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.15.0, 5.1.0
> Reporter: Lars Hofhansl
> Priority: Blocker
> Fix For: 4.15.0, 5.1.0
>
> Attachments: 5559-test.txt
>
>
>
> {code:java}
> phoenix: CREATE TABLE test (pk INTEGER PRIMARY KEY, v1 INTEGER, v2 integer);
> No rows affected (1.389 seconds)
> phoenix: create local index l1 on test(v1);
> 1 row affected (11.343 seconds)
> phoenix: create local index l2 on test(v1);
> 1 row affected (5.107 seconds)
> phoenix: UPSERT INTO test VALUES(2,2,2);
> 1 row affected (0.037 seconds)
> hbase: scan 'TEST'
> ROW COLUMN+CELL
> \x00\x00\xC1\x03\x00\x80\x00\x00\x02 column=L#0:\x00\x00\x00\x00, timestamp=1572842063925, value=x
> \x80\x00\x00\x02 column=0:\x00\x00\x00\x00, timestamp=1572842063925, value=x
> \x80\x00\x00\x02 column=0:\x80\x0B, timestamp=1572842063925, value=\x80\x00\x00\x02
> \x80\x00\x00\x02 column=0:\x80\x0C, timestamp=1572842063925, value=\x80\x00\x00\x02
> 2 row(s) in 0.0190 seconds{code}
> There should be two index rows.
> And in fact there are with phoenix.index.longViewIndex.enabled set to true, there are correctly two different index entries for both of the local indexes.
> [~gjacoby] [~rajeshbabu]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)