| commit | a2b2ef5ff84c38d984fefc0f62a1dfe27e66cdf3 | [log] [tgz] |
|---|---|---|
| author | salsubaiee <salsubaiee@123451ca-8445-de46-9d55-352943316053> | Tue May 08 02:52:48 2012 +0000 |
| committer | salsubaiee <salsubaiee@123451ca-8445-de46-9d55-352943316053> | Tue May 08 02:52:48 2012 +0000 |
| tree | c540131ac3c9cd9bb2479b2ce546c65b9c42cc03 | |
| parent | cad9e08a7f020504fb686c45f1aef473c644fc19 [diff] |
Fixed the following bug: 1) Insert to the tree tuple A. 2) Flushed tuple A. 3) Delete tuple A (still in the in-memory btree). 4) Insert tuple A, which will cause the tuple A in the in-memory btree to be deleted. 5) Tuple A will be inserted in the in-memory tree. Thus, searchers will see 2 copies of tuple A. The bug is fixed now by skipping the second insertion. git-svn-id: https://hyracks.googlecode.com/svn/branches/hyracks_rtree_bulkload@1442 123451ca-8445-de46-9d55-352943316053