Advanced Analytica Advanced Analytica: IBOM
← All connectors
End-to-End Testing (/dev/null) logo

Destination connector

End-to-End Testing (/dev/null)

Send governed data into End-to-End Testing (/dev/null) with a clear, practical setup guide.

Version 0.9.9 certified generally available

End-to-end testing with the (/dev/null) destination

Use the /dev/null destination to test source connectors without writing data anywhere. It accepts every source record and discards it by default. You can benchmark a source connector or confirm that a connection completes. You can also reproduce specific destination behaviours, including slow processing or failure after N messages.

:::danger In Logging mode, this destination writes source records to the sync logs. Anyone with access to the Airbyte logs can read this data. Don’t use Logging mode with production or sensitive data. :::

Prerequisites

You don’t need any prerequisites. The destination has no external dependencies. The connection check always succeeds when the configuration is valid.

Set up the destination

  1. In the Airbyte UI, go to Destinations, click New destination, then select End-to-End Testing (/dev/null).
  2. Enter a Destination name.
  3. Under Test Destination, choose a mode described in Modes, then complete its options.
  4. Click Set up destination.

Modes

The available modes depend on where Airbyte runs.

ModeSelf-ManagedAirbyte Cloud
SilentYesYes
LoggingYesNo
ThrottledYesNo
FailingYesNo

Silent

Silent mode acts as a true /dev/null. It accepts and discards every record. State messages are still acknowledged, so the source advances its cursor as it would with a real destination. Use it to test source performance or confirm that a sync completes end to end.

This is the only mode available on Airbyte Cloud.

Logging

Logging mode writes a subset of records to the sync log at INFO level, then discards them. Each log line includes the stream, record index and record fields:

Logging Destination(stream=public.users, recordIndex=0, logEntry=1/100): {...}

Each stream is logged independently. The destination logs no more than 1,000 entries per stream, regardless of the logging type you choose.

Logging typeBehaviorOptions
First N EntriesLog the first N records of each stream.N: number of records to log (default 100, maximum 1000).
Every N-th EntryLog every N-th record of each stream. N = 1 logs every record, N = 2 every other record, and so on.N: the interval. Max Log Entries: cap on the number of records logged (default 100, maximum 1000).
Random SamplingLog each record with a given probability.Sampling Ratio: a number between 0 and 1 (default 0.001). Random Number Generator Seed (optional): fix the seed for reproducible sampling; defaults to the current time. Max Log Entries: cap on the number of records logged (default 100, maximum 1000).

Throttled

Throttled mode waits for a configurable number of milliseconds (millis_per_record) before processing each record, then discards it. Use it to simulate a slow destination. You can then observe how the source and platform behave under back-pressure.

Failing

Failing mode discards records until a stream receives the configured number of messages (num_messages). It then throws an exception, which fails the sync. Use it to test failure handling, retries and alerting.

Sync modes

Sync modeSupported?
Full Refresh - OverwriteYes
Full Refresh - AppendYes
Full Refresh - Overwrite + DedupedYes
Incremental Sync - AppendYes
Incremental Sync - Append + DedupedYes

The destination accepts every sync mode because it stores no data. Deduplication and overwrite have no visible effect. It also accepts file-based (file transfer) streams and discards the files.

Namespace support

Namespaces don’t affect this destination. In Logging mode, the stream namespace appears only in the output as part of the stream identifier.

Limitations

  • No data is persisted. After a sync, you can inspect only the logs.
  • Logging mode limits output to 1,000 entries per stream and may expose source data in logs.
  • Airbyte Cloud offers only Silent mode.

Changelog

Expand to review

The self-managed and Cloud variants have the same version number starting from version 0.2.2.

VersionDatePull RequestSubject
0.9.92026-10-3090277Promote to certified (GA). Logging/Failing modes count records per stream instead of per internal batch; FAILING now fails on exactly the Nth record.
0.9.82026-10-2289655Upgrade to Bulk CDK 1.1.9: fix critical CVEs in Apache MINA (mina-core 2.0.31), MINA SSHD 2.20.0 and BouncyCastle 1.86; netty 4.1.139
0.9.72026-10-1689066Bump Bulk CDK to base 1.0.6 / load 1.1.7 (Kotlin 2.4 / K2 toolchain, Micronaut 4.10.31, Jackson 2.21.7).
0.9.62026-10-0988426Upgrade to Bulk CDK 1.1.1.
0.9.52026-09-1586330Version bump to republish the Cloud-specific connector spec.
0.9.42026-05-1978228Upgrade CDK to 1.0.13
0.9.32026-02-0472856Upgrade CDK to 0.2.8
0.9.22026-01-2172291Upgrade CDK to 0.2.0
0.9.12026-01-2172226No-op version bump to test release cycle
0.9.02026-01-0971264Promoting release candidate 0.9.0-rc.2 to a main version.
0.9.0-rc.22026-01-0871242Add missing configuration bean.
0.9.0-rc.12026-01-0871191Migrate to modern dataflow CDK architecture.
0.8.62025-11-0569128Upgrade to Bulk CDK 0.1.61.
0.8.52025-10-2167153Implement new proto schema implementation
0.8.42025-09-2466684Pin to CDK artifact.
0.8.32025-09-0865999Testing publishing flow.
0.8.22025-08-1264897Testing publishing flow.
0.8.12025-07-3064117Re-release with latest CDK for socket related fixes.
0.8.02025-06-1761585Upgrade dev null to the new data channel based architecture.
0.7.272025-06-1361587Test publishing logic.
0.7.262025-05-2760938Revert to base 2.0.1, test default IPC Options
0.7.252025-05-1560312Migrate to base 2.0.2.
0.7.242025-05-1560301Add support for file-based syncs
0.7.232025-05-0959766Test publishing in new flow.
0.7.222025-05-0959759Migrate to new flow.
0.7.212025-05-0759710CDK: bugfixes
0.7.202025-03-2155906CDK: Pass DestinationRecordRaw around instead of DestinationRecordAirbyteValue
0.7.192025-03-1355737CDK: Pass DestinationRecordRaw around instead of DestinationRecordAirbyteValue
0.7.182025-02-2554179Use new CDK interface; perf improvements, skip initial staging
0.7.172025-01-2451600Internal refactor
0.7.162024-12-1952076Test improvements
0.7.152024-12-1949931Non-functional CDK changes
0.7.142024-12-2049974Non-functional CDK changes
0.7.132024-12-1849899Use a base image: airbyte/java-connector-base:1.0.0
0.7.122024-12-0448794Promoting release candidate 0.7.12-rc.2 to a main version.
0.7.12-rc.22024-11-2648693Update for testing progressive rollout
0.7.12-rc.12024-11-2548693Update for testing progressive rollout
0.7.112024-11-1848468Implement File CDk
0.7.102024-11-0848429Bugfix: correctly handle state ID field
0.7.92024-11-0748417Only pass through the state ID field, not all additional properties
0.7.82024-11-0748416Bugfix: global state correclty sends additional properties
0.7.72024-10-1746692Internal code changes
0.7.62024-10-0846683Bugfix: pick up checkpoint safety check fix
0.7.52024-10-0846683Bugfix: checkpoints in order, all checkpoints processed before shutdown
0.7.42024-10-0846650Internal code changes
0.7.32024-10-0146559From load CDK: async improvements, stream incomplete, additionalProperties on state messages
0.7.22024-10-0145929Internal code changes
0.7.12024-09-3046276Upgrade to latest bulk CDK
0.7.02024-09-2045704
0.6.12024-09-2045715add destination to cloud registry
0.6.02024-09-1845651merge destination-e2e(OSS) and destination-dev-null(cloud)
0.5.02024-09-1845650upgrade cdk
0.4.12024-09-1845649convert test code to kotlin
0.4.02024-09-1845648convert production code to kotlin
0.3.62024-05-0938097Support dedup
0.3.52024-04-2937366Support refreshes
0.3.42024-04-1637366Fix NPE
0.3.32024-04-1637366Fix Log trace messages
0.3.22024-02-1436812Log trace messages
0.3.12024-02-1435278Adopt CDK 0.20.6
0.3.02023-05-0825776Standardize spec and change property field to non-keyword
0.2.42022-06-1713864Updated stacktrace format for any trace message errors
0.2.32022-02-1410256Add -XX:+ExitOnOutOfMemoryError JVM option
0.2.22022-01-29#9745Integrate with Sentry.
0.2.12021-12-19#8824Fix documentation URL.
0.2.02021-12-16#8824Add multiple logging modes.
0.1.02021-05-25#3290Create initial version.
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.