HailDB Cursor not resetting this->cursor to clustered index after secondary index operations (causing sysbench failure)
Bug #655805 reported by
Lee Bieber
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Fix Released
|
Undecided
|
Unassigned | ||
7.0 |
Fix Released
|
High
|
Stewart Smith |
Bug Description
Initial symptom was Sysbench failing with HailDB.
http://
http://
Investigation showed that we weren't resetting the cursor we track in the HailDBCursor object (to help avoid lots of malloc/free cycles we keep a cursor around) back to the clustered index after an operation on a secondary index (e.g. index scan). This mean we were attempting the UPDATE on the wrong index, ending up with a DB_ERROR from ib_cursor_
Related branches
To post a comment you must log in.
all branches needed for htis should now be in trunk.