测试POST创建Mongo条目后，无DELETE端点时如何用JMeter清理数据？

Great question—your constraints around compliance and code repository cleanliness make total sense, especially with sensitive medical data. Let’s break down feasible options, starting with modern JMeter approaches and moving to practical workarounds:

1. Modern JMeter Integration with MongoDB (No Deprecated Plugins) #

The old MongoDB JMeter plugin is indeed outdated, but you can use the official MongoDB Java Driver directly via JMeter’s JSR223 elements (like JSR223 Sampler) for full, up-to-date control. This avoids relying on deprecated tools and lets you execute delete operations (or any MongoDB command) directly.

Here’s a step-by-step example:

• First, add the MongoDB Java Driver JARs (e.g., mongodb-driver-sync, mongodb-driver-core, bson) to JMeter’s lib/ext folder and restart JMeter.
• Create a JSR223 Sampler with code like this (adjust to your environment):

import com.mongodb.client.MongoClients;
import com.mongodb.client.MongoClient;
import com.mongodb.client.MongoDatabase;
import com.mongodb.client.MongoCollection;
import org.bson.Document;
import com.mongodb.client.model.Filters;

// Connect to MongoDB (use environment variables for credentials in non-local setups!)
MongoClient mongoClient = MongoClients.create("mongodb://your-host:27017");
MongoDatabase database = mongoClient.getDatabase("your-medical-db");
MongoCollection<Document> collection = database.getCollection("target-collection");

// Option 1: Delete entire collection (use ONLY if compliance rules allow!)
// collection.drop();

// Option 2: Delete filtered documents (e.g., test-only entries)
collection.deleteMany(Filters.eq("dataType", "test"));

mongoClient.close();

Critical Note: Since you’re working with medical data, double-check compliance policies before executing direct deletes. Even if JMeter supports the operation, ensure it aligns with your organization’s data retention and audit requirements.

2. Leverage Existing Endpoints for Bulk "Soft Delete" #

Instead of bypassing your system’s compliance layer, use JMeter to automate bulk calls to your existing PUT endpoint that marks entries as DONT SHOW/REMOVED. This keeps you within the system’s designed workflow and avoids compliance risks.

How to set this up:

• Use an HTTP Sampler to fetch the list of entries you need to mark as removed (e.g., a GET endpoint for test records).
• Use a JSON Extractor to pull all relevant entry IDs from the response.
• Wrap the PUT endpoint call in a Loop Controller to iterate over each ID and apply the "removed" flag.

This approach requires no new code and works within your existing compliance framework—ideal if direct MongoDB deletes are off-limits.

3. External Cleanup Endpoint (Your Proposed Idea) #

If the above options don’t fit, adding a dedicated cleanup endpoint outside your main code repository is a valid choice. To keep it compliant:

• Restrict access strictly to test environments (never production).
• Add robust authentication (e.g., API keys, IP whitelisting) and authorization controls.
• Log every operation fully for audit trails (non-negotiable for medical data).
• Ensure the endpoint only targets non-production or test-specific data to avoid accidental loss.

4. OS Process Sampler with mongosh #

For a quick (but less controlled) workaround, use JMeter’s OS Process Sampler to run mongosh commands directly. Example command:

mongosh "mongodb://your-host:27017" --eval "db.target-collection.deleteMany({dataType: 'test'})"

This is fast to set up but carries more risk: you’ll need to manage MongoDB credentials securely (avoid hardcoding!) and ensure the JMeter runtime has mongosh installed. It’s less ideal for medical data due to reduced auditability compared to the JSR223 approach.

Final Recommendation #

Start with Option 2 if possible—it aligns with your existing compliance controls and requires no new code. If you need faster cleanup for test environments, Option 1 (JSR223 + MongoDB Driver) is the modern, flexible alternative. Only consider Option 3 if the first two aren’t feasible, and keep Option 4 as a last resort due to security/audit concerns.

内容的提问来源于stack exchange，提问作者Jo Dod