[
https://issues.apache.org/jira/browse/TRAFODION-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713650#comment-14713650
]
Suresh Subbiah commented on TRAFODION-340:
------------------------------------------
I tried the following on a table and I was not able to reproduce the problem:
Begin work;
Update some rows in table t ;
Select * from t;
Commit work;
I also did an update to the same table outside of a transaction and I was not
able to reproduce the problem either.
Atanu Mishra (atanu-mishra) on 2014-06-03
Changed in trafodion:
importance: Medium → Critical
status: New → In Progress
Atanu Mishra (atanu-mishra) wrote on 2014-06-03: #2
Adriana is now able to reproduce the problem.
Adriana Fuentes (adriana-fuentes) wrote on 2014-06-05: #3
The problem is reproducible and I figured out that the problem started
appearing after the following check-in in github:
13e3f70 2014-05-30 | Changes to improve the performance of select statement
[Selvaganesan]
I added the changes for the early reply that Oliver/John did and it did not
make a difference in the select after an update.
Stacey Johnson (sjohnson-w) on 2014-06-10
information type: Proprietary → Public
Adriana Fuentes (adriana-fuentes) on 2014-06-11
Changed in trafodion:
assignee: Adriana Fuentes (adriana-fuentes) → Suresh Subbiah
(suresh-subbiah)
Pavani Puppala (pavani-puppala) on 2014-06-11
tags: added: sql-exe
removed: dtm
Suresh Subbiah (suresh-subbiah) wrote on 2014-06-11: #4
create table t1 (a int not null not droppable primary key, b int not null not
droppable) ;
insert into t1 values (1,9),(2,9),(3,9);
Begin work;
Update t1 set b = 4 ;
Select * from t1;
commit;
will show the problem. It shows every time and is easily reproducible.
The issue was that while executing the update statement the executor calls
scanner.next() with the correct transid. It gets 2 values for column b, both
the "old" (before update value) and the "new" (after update value). Executor
was expecting only only one version per column since the previous Thrift class
provided that to the executor. Logic has been added in executor to copy the
most recent version into the SQL row for each column.
Changed in trafodion:
status: In Progress → Fix Committed
Alice Chen (alchen) on 2014-10-15
Changed in trafodion:
status: Fix Committed → Fix Released
See full activity log
> LP Bug: 1325443 - SELECT after an UPDATE continues to show old values
> ---------------------------------------------------------------------
>
> Key: TRAFODION-340
> URL: https://issues.apache.org/jira/browse/TRAFODION-340
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
> Reporter: Atanu Mishra
> Assignee: Suresh Subbiah
> Priority: Blocker
> Fix For: 0.8 (pre-incubation)
>
>
> Reported by Selva --
> Begin work;
> Update some rows in table t ;
> Select * from t;
> Commit work;
> The test was expecting the updated rows to have new values in the select
> statement. But the select statement continue to show the old values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
