Integrations · NoSQL

NoSQL test data management

Document and key-value stores hold nested, schema-flexible records: a customer document may embed addresses, devices and preferences that a relational model would split into tables.

Test data for these systems needs classification that understands nested fields and masking that keeps identifiers consistent with the relational systems around them.

What test data management needs here

  • Field-shape discovery computed inside your network from a bounded sample, reported as structure only.
  • Flattening of nested documents for classification and masking, then faithful re-nesting.
  • Identity mappings between document keys and relational keys, approved by an owner.

How DataNivra approaches it

  • NoSQL connectors are roadmap work: the design reuses the same masking domains, relationship graph and certification gates as relational sources.
  • Any matching that needs values would run in the agent, never in DataNivra Cloud.
  • Whatever the system, row-level work happens in the DataNivra agent inside your network: only metadata, aggregates and evidence reach DataNivra Cloud.

NoSQL: connector status (4)

3 of these connectors can be used today (available or in preview); the others are shown with their honest status. Statuses are derived from recorded conformance evidence.

Available now

MongoDB

Shipped in the standard agent and backed by recorded conformance evidence.

MongoDB connector (pymongo): collection discovery, field shapes inferred from a bounded sample inside your network, _id or unique-index-backed business keys, document counts, aggregate profiles and bounded streaming reads with nested documents carried as JSON text.

Available now — details about MongoDB

Available now

Azure Cosmos DB

Shipped in the standard agent and backed by recorded conformance evidence.

Azure Cosmos DB for NoSQL connector (azure-cosmos): container discovery, field shapes inferred from a bounded sample inside your network, partition-key-aware keys, RU-budgeted paged queries and nested items carried as JSON text.

Available now — details about Azure Cosmos DB

Available now

Amazon DynamoDB

Shipped in the standard agent and backed by recorded conformance evidence.

Amazon DynamoDB connector (boto3): table discovery, partition and sort keys, attribute shapes inferred from a bounded scan inside your network, and eventually consistent, paginated scans under a read-capacity budget with nested attributes carried as JSON text.

Available now — details about Amazon DynamoDB

Coming next

Amazon DocumentDB

Active implementation; not yet available for production use.

Amazon DocumentDB (instance-based clusters) through the MongoDB connector, with its own compatibility record: collection discovery, field shapes inferred from a bounded sample inside your network, _id or unique-index-backed business keys, document counts, aggregate profiles and bounded streaming reads. MongoDB compatibility is never assumed: DocumentDB is detected and tested separately.

Coming next — details about Amazon DocumentDB

Learn, try, then start

See the whole workflow — discovery, classification, masking, subsetting and certification — in the synthetic playground, then start a free trial. The product overview explains how the customer-resident agent and DataNivra Cloud divide the work.

Other categories: Databases · Data warehouses · Lakehouses · Object storage · Files · SaaS applications · Mainframe · Streaming · APIs.