- problem description
query interface error: OL>
{"errorMessage":
"Command failed with error 16412: 'FieldPath field names may not contain '.'.' on server 10.21.20.8:27019. The full response is { \"ok\" : 0.0, \"errmsg\" : \"FieldPath field names may not contain '.'.\", \"code\" : 16412, \"codeName\" : \"Location16412\" }"}
com.mongodb.MongoCommandException: Command failed with error 16412: 'FieldPath field names may not contain '.'.' on server 10.21.20.8:27019. The full response is { "ok" : 0.0, "errmsg" : "FieldPath field names may not contain '.'.", "code" : 16412, "codeName" : "Location16412" }
at com.mongodb.connection.ProtocolHelper.getCommandFailureException(ProtocolHelper.java:115)
at com.mongodb.connection.CommandProtocol.execute(CommandProtocol.java:114)
at com.mongodb.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:168)
at com.mongodb.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:289)
at com.mongodb.connection.DefaultServerConnection.command(DefaultServerConnection.java:176)
at com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:216)
at com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:207)
at com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:113)
at com.mongodb.operation.AggregateOperation$1.call(AggregateOperation.java:257)
at com.mongodb.operation.AggregateOperation$1.call(AggregateOperation.java:253)
at com.mongodb.operation.OperationHelper.withConnectionSource(OperationHelper.java:435)
at com.mongodb.operation.OperationHelper.withConnection(OperationHelper.java:408)
at com.mongodb.operation.AggregateOperation.execute(AggregateOperation.java:253)
at com.mongodb.operation.AggregateOperation.execute(AggregateOperation.java:67)
at com.mongodb.Mongo.execute(Mongo.java:836)
at com.mongodb.Mongo$2.execute(Mongo.java:823)
at com.mongodb.DBCollection.aggregate(DBCollection.java:1455)
at com.mongodb.DBCollection.aggregate(DBCollection.java:1418)
at com.mongodb.DBCollection.aggregate(DBCollection.java:1403)
at com.linkus.biz.prj.service.impl.PrjDevTaskStatServiceImpl.getPrjDevTaskStatData(PrjDevTaskStatServiceImpl.java:127)
- problem solving
check the fields in the group. The grouping fields are wrong. The value “joinbiz. Resp” of resp in the group is changed to “resp” OL>
"$group":{
"_id":{
"prjSys":"$prjSys",
"prjMod":"$prjMod",
"resp":"$_joinBiz_.resp",
},
"devTasksCount":{
"$sum":1
},
"minPlanEndDate":{
"$min":"$_joinBiz_.planEndDate"
},
"maxPlanEndData":{
"$max":"$_joinBiz_.planEndDate"
},
"planCompletionCount":{
"$sum":"$planCompletionNum"
},
"actualCompletionCount":{
"$sum":"$actualCompletionNum"
}
}
Read More:
- 13. R language: Error in match.names(clabs, names(xi)): The name is not relative to the original name
- R language error in match.names (clabs, names(xi)) :
- Batch modification of file names on MAC Linux rename command line
- Use xx [‘xx ‘] = XX to set field value or does not support field: XXX
- Command line access to passive mode FTP server failed, 425 failed to establish connection
- Alibaba cloud builds FTP server 200 port command successful. Consider using PASV. 425 failed to establish connection
- MongoDB Error: Query failed with error code 2 and error message ‘Field ‘locale’ is invalid
- nbconvert failed: xelatex not found on PATH, if you have not installed xelatex you may need to do so
- Linux basic command execution error: the solution of command not found
- Redis reports an error when integrating springsecurity: could not read JSON: unrecognized field “enabled”“
- [solved] – bash: rabbitmq plugins: command not found or RA bbitmqctl:command not found
- Tainted canvases may not be exported
- Error: could’t connect to server 127.0.0.1:27017, connection attempt failed
- May cause (ora-01006: binding variable does not exist) problems
- Mongodb uses Mongo to report error: could’t connect to server 127.0.0.1:27017, connection attempt failed: socket
- Error: Command failed: git describe –always fatal: Not a valid object name HEAD
- This error may also indicate that the docker daemon is not running.
- Could not publish server configuration for Tomcat v8.5 server at localhost
- error: declaration may not appear after executable statement in block
- Try not to use @reference after using Dubbo, which may cause conflicts