You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in the mongodb issue log - https://jira.mongodb.org/browse/SERVER-30524 - the date from part operator for milliseconds was changed from "milliseconds" to "millisecond" (singular). However, when using the date part from spring mongodb, it still creates the aggregation query with "milliseconds" and hence the query fails with an unrecognized operator error. Based on the initial investigation, it feels like this line causes the issue
taher435 opened DATAMONGO-2671 and commented
As mentioned in the mongodb issue log - https://jira.mongodb.org/browse/SERVER-30524 - the date from part operator for milliseconds was changed from "milliseconds" to "millisecond" (singular). However, when using the date part from spring mongodb, it still creates the aggregation query with "milliseconds" and hence the query fails with an unrecognized operator error. Based on the initial investigation, it feels like this line causes the issue
Referenced from: pull request #897
The text was updated successfully, but these errors were encountered: