Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | MongoSQL |
| Version | 16.0 |
In both MongoJS and MongoSQL, verify that big resultsets "memory leaks" don't occur, i.e. references (to all the DBObject instances for a given resultset) held by our JDBC internal cache(s) and GUI components are properly released (e.g. when Query Analyzer window is closed).
@emil: for v17, also look into whether we can merge traversals #1 & #2 together
@emil: for v17, also look into whether we can merge traversals #1 & #2 together
#2 is not actually a full traversal but rather just tries to retrieve first encountered object (see MongoResultSet#buildPredictObject() method), thus there is no need to merge #1 and #2. By caching the results, the implementation inside the buildPredictObject() method won't create additional workload on the MongoDB Server anymore.
@emil: for v17, also look into whether we can merge traversals #1 & #2 together
#2 is not actually a full traversal but rather just tries to retrieve first encountered object (see MongoResultSet#buildPredictObject() method), thus there is no need to merge #1 and #2. By caching the results, the implementation inside the buildPredictObject() method won't create additional workload on the MongoDB Server anymore.
Issue #13372 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 16.0.5-13, ADS 17.0.0-dev-52 |
| No time estimate |
@emil: for v17, also look into whether we can merge traversals #1 & #2 together