-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Environment:OS:
node.js / npm versions:
Additional info:
-
Not Needed
-
Developer Tools
Hi Team,
I am facing two critical issues while executing queries, which are leading to incorrect data retrieval:
- Incorrect Field Name Not Throwing an Error:
-
- When using the condition {}{transactionAmount: {$nin: ["000000000000"]{}}}, the query works as expected.
- However, if I mistakenly enter {trasactionAmount: {$nin: ["000000000000"]}} (with a typo in the field name), the query still runs but does not filter correctly.
- Ideally, the query should fail or throw an error if an incorrect field name is used. Instead, it executes and includes both financial and non-financial transactions, leading to inaccurate data.
- Mismatch in Pre-execution and Final Query Output Count:
-
- When applying $match and $project stages in aggregation, the preview count (side view result) before execution shows a different value than the actual output after running the query.
- Example: The side view result shows 1000, but after executing the query, the final count is 1230.
- This discrepancy is misleading and affects report accuracy.
These issues are leading to incorrect data retrieval and impacting our reports. Please investigate and provide an update ASAP.
By
Devanathan S
9344081154.
- split to
-
COMPASS-8943 Warn when query use a field which is not present in any documents
-
- Needs Triage
-