[SERVER-14738] Updates to documents with text-indexed fields may lead to incorrect entries Created: 31/Jul/14 Updated: 11/Jul/16 Resolved: 01/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Text Search |
| Affects Version/s: | 2.4.10, 2.6.1, 2.7.4 |
| Fix Version/s: | 2.4.11, 2.6.4, 2.7.5 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Mathieu [X] | Assignee: | J Rassi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
| Comments |
| Comment by Githook User [ 22/Aug/14 ] |
|
Author: {u'username': u'kkmongo', u'name': u'Kamran Khan', u'email': u'kamran.khan@mongodb.com'}Message: Closes #752 Signed-off-by: Benety Goh <benety@mongodb.com> |
| Comment by Githook User [ 07/Aug/14 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (backport of 1f00ffcd22e671f5adeece53c68b5e462ba01ec0) |
| Comment by Ramon Fernandez Marina [ 07/Aug/14 ] |
|
david.bachrach@staples.com, yes, you can re-index your documents after updating them (there's no need to drop the index first) to work around this issue, but this is not listed as a workaround because index rebuilds can take a long time for large collections, so it's not a universal workaround. Inserting an additional field in your documents (e.g. {x:1}) and building an index on it (db.col.ensureIndex({x:1})) also avoids the issue altogether, but this is a bit of a hack so is not listed as a universal workaround either. |
| Comment by David Bachrach [ 07/Aug/14 ] |
|
We have a collection with 8 documents. We can easily drop the index before doing updates and then recreate the index after doing the update. The documents are relatively static so won't be changing often. Is this an option until we schedule an upgrade to 2.4.11 or 2.6.4? I didn't see it listed as a workaround, but curious if this would work. Again, drop the index before doing any updates and create the index after any updates. Thanks |
| Comment by David Bachrach [ 07/Aug/14 ] |
|
That's what i was looking for. Whether 2.4.8 was affected, which it looks like it is. Thanks |
| Comment by Githook User [ 04/Aug/14 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |
| Comment by Githook User [ 01/Aug/14 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (cherry picked from commit 1f00ffcd22e671f5adeece53c68b5e462ba01ec0) |
| Comment by Githook User [ 01/Aug/14 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |
| Comment by J Rassi [ 31/Jul/14 ] |
|
Hi Mathieu_Laporte, We are able to reproduce this issue. Thanks for reporting it. Please continue to watch this ticket for workaround information and updates on when a fix will be available. ~ Jason Rassi |