Mongodb迁移导致重复的密钥

Question

在一个老项目中，我们试图从基本的spring迁移到spring boot 2.3.1。为此，因为我们有一个mongo数据库，所以我们必须从编写这段代码的spring-data-mongodb:1.10.18迁移:

DBCollection contextCollection = this.mongoTemplate.getCollection("productStock");
BulkWriteOperation builder = contextCollection.initializeUnorderedBulkOperation();
StockType stockItem = stockMessage.getStockItem();

final BasicDBObject id = new BasicDBObject("storeID", stockItem.getStoreID()).append("productID", stockItem.getProductID());
BulkWriteRequestBuilder bulkWriteRequestBuilder = builder.find(new BasicDBObject("_id", id));
HashMap<String, Object> stock = new HashMap<>();
Date currentDate = Calendar.getInstance().getTime();

stock.put("value", stockItem.getValue());
if (stockItem.getAssociateDate() != null) {
    stock.put("associateDate", stockItem.getAssociateDate());
}

if (stockItem.getLastAccessDateSource() != null) {
    stock.put("lastAccessDateSource", stockItem.getLastAccessDateSource());

    // check
    BasicDBObject ltLast = new BasicDBObject("$lt", stockItem.getLastAccessDateSource());
    BasicDBList dbList = new BasicDBList();
    dbList.add(new BasicDBObject(stockItem.getStockCategory() + ".lastAccessDateSource", ltLast));
    dbList.add(new BasicDBObject(stockItem.getStockCategory() + ".lastAccessDateSource", null));
    bulkWriteRequestBuilder = builder.find(new BasicDBObject("_id", id).append("$or", dbList));
} else {
    stock.put("lastAccessDateSource", currentDate);
}

stock.put("lastUpdateDate", currentDate);
BasicDBObject set = new BasicDBObject(stockItem.getStockCategory(), new Document(stock));
bulkWriteRequestBuilder.upsert().updateOne(new BasicDBObject("$set", set));
builder.execute();

到spring-data-mongodb：3.0.1.RELEASE与此更新的代码

Map<String, List<StockType>> mapMultiUpdate = new HashMap<>();
StockType stockItem = stockMessage.getStockItem();

final Document id = new Document("storeID", stockItem.getStoreID()).append("productID", stockItem.getProductID());
HashMap<String, Object> stock = new HashMap<>();
Date currentDate = Calendar.getInstance().getTime();
Document searchQuery = new Document("_id", id).append("$or", dbList);
stock.put("value", stockItem.getValue());
if (stockItem.getAssociateDate() != null) {
    stock.put("associateDate", stockItem.getAssociateDate());
}

if (stockItem.getLastAccessDateSource() != null) {
    stock.put("lastAccessDateSource", stockItem.getLastAccessDateSource());

    // check
    Document ltLast = new Document("$lt", stockItem.getLastAccessDateSource());
    List<Document> dbList = Lists.newArrayList();
    dbList.add(new Document(stockItem.getStockCategory() + ".lastAccessDateSource", ltLast));
    dbList.add(new Document(stockItem.getStockCategory() + ".lastAccessDateSource", null));
} else {
    stock.put("lastAccessDateSource", currentDate);
}


//Bulk write options
BulkWriteOptions bulkWriteOptions = new BulkWriteOptions();
bulkWriteOptions.ordered(false);
bulkWriteOptions.bypassDocumentValidation(true);

MongoCollection<Document> mongoCollection = this.mongoTemplate.getCollection("productStoreStock");
mongoCollection.bulkWrite(updateDocuments, bulkWriteOptions);

但是当新代码在已经存在的对象上执行时，我们得到一个重复的键错误

com.mongodb.MongoBulkWriteException: Bulk write operation error on server localhost:27017. Write errors: [BulkWriteError{index=0, code=11000, message='E11000 duplicate key error collection: test.productStoreStock index: _id_ dup key: { : { storeID: 400, productID: 100000 } }', details={}}]. 

我们还从 mongo-java-driver：3.6.4 切换到 mongodb-driver-sync：4.0.4

编辑：

此错误在测试阶段的第 3 步，在空数据库/集合上引发。步骤：

在特定
• 日期使用产品上的一个库存启动收集
• 检查基数的值
• 在 Java 中修改股票的价值，但不修改日期并尝试更新它
• 检查值仍然是第一个，因为 mongo 查询上的 LT 过滤器

我们从未达到检查值，在迁移之前，此测试一切都很好

Answer 1

Mongo没有更新，当没有找到匹配项时，它正在更新（插入新行）。

Answer 2

test.productStoreStock index: _id_ dup key: { : { storeID: 400, productID: 100000 } }', details={}}

看起来您正在用自己的“构造”id替换内部id字段。这不是一件好事。让mongo创建它自己的id，这些id保证在使用中是唯一的..永远不会重复。将您自己的companyId作为一个附加字段没有问题，但是替换mongodbs的auto generated _id字段是危险的...正如你所发现的。