[ 
https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013592#comment-17013592
 ] 

Lars Hofhansl commented on PHOENIX-5580:
----------------------------------------

Hmm... I also see it's using the same plan in both cases:
{code}
0: jdbc:phoenix:localhost> explain select /*+ NO_INDEX */ * from v1;
+----------------------------------------------------------------------------------------------+-----------------+----------------+--------------+
|                                             PLAN                              
               | EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
+----------------------------------------------------------------------------------------------+-----------------+----------------+--------------+
| CLIENT 1-CHUNK 1 ROWS 141 BYTES PARALLEL 1-WAY ROUND ROBIN POINT LOOKUP ON 1 
KEY OVER TEST1  | 141             | 1              | 0            |
+----------------------------------------------------------------------------------------------+-----------------+----------------+--------------+
1 row selected (0.025 seconds)
0: jdbc:phoenix:localhost> explain select * from v1;
+----------------------------------------------------------------------------------------------+-----------------+----------------+--------------+
|                                             PLAN                              
               | EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
+----------------------------------------------------------------------------------------------+-----------------+----------------+--------------+
| CLIENT 1-CHUNK 1 ROWS 141 BYTES PARALLEL 1-WAY ROUND ROBIN POINT LOOKUP ON 1 
KEY OVER TEST1  | 141             | 1              | 0            |
+----------------------------------------------------------------------------------------------+-----------------+----------------+--------------+
1 row selected (0.026 seconds)
{code}


> Wrong values seen when updating a view for a table that has an index
> --------------------------------------------------------------------
>
>                 Key: PHOENIX-5580
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5580
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.0, 4.14.1, 4.14.3
>            Reporter: Swaroopa Kadam
>            Assignee: Abhishek Singh Chouhan
>            Priority: Major
>              Labels: indexing, phoenix-hardening
>             Fix For: 5.1.0, 4.15.1
>
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST 
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
>  CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
>  UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to