[JAVA-164] Collection cache stale after drop/renameCollection Created: 11/Sep/10  Updated: 29/Oct/10  Resolved: 03/Oct/10

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 2.2

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by auto [ 03/Oct/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: reset index cache on rename and drop. also make createIndex( keys , options ) public so can call that directly JAVA-164
http://github.com/mongodb/mongo-java-driver/commit/7b30e0ae302fc7b2bfad11822bc082534ad4470d

Comment by Scott Hernandez (Inactive) [ 03/Oct/10 ]

Yep, it was a problem when running tests where the indexes existed even after the collection was dropped, by the same mongo instance.

It might be nice to have this "cache" info timeout periodically. Esp. since Mongo is suggested to be used as a singtlon in the jvm.

Comment by Eliot Horowitz (Inactive) [ 01/Oct/10 ]

Why does this matter?
Index cache?

Comment by Scott Hernandez (Inactive) [ 11/Sep/10 ]

http://github.com/scotthernandez/mongo-java-driver/commit/6ad17bd0251134674595ff188593efc4f1624363

Generated at Thu Feb 08 08:51:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.