Meilisearch Sink

The Wallaby.Sinks.Meilisearch package keeps Meilisearch indexes continuously in sync with your Postgres tables. Upserts are written with a stable primary key (so updates are idempotent) and deletions remove by that same id.

Register

cdc.AddMeilisearchSink("meili", m =>
{
    m.Host = "http://localhost:7700";
    m.ApiKey = key;            // master or a write key; null for an unsecured instance
    m.DefaultIndex = "search"; // optional fallback when a mapping has no destination
});

Then route mappings to it, using the destination as the index name:

cdc.Map<Product>()
   .ToSink("meili", destination: "products")
   .UsingTransform(/* ... */);

Options

Option	Default	Purpose
Host	(required)	Meilisearch base URL.
ApiKey	null	Master/write key; null for unsecured.
DefaultIndex	null	Index used when a routed record has no destination.
PrimaryKey	id	Document key field Wallaby injects into every document.
WaitForCompletion	true	Await each indexing task before the batch is acked (honest at-least-once).
WaitTimeoutMs	60000	Max wait per task when WaitForCompletion.
WaitIntervalMs	50	Poll interval while waiting.

Index configuration

By default Meilisearch auto-creates an index on first write (inferring its primary key). To create and configure an index up front instead, declare it with ConfigureIndex. Declared indexes are created (with the sink's PrimaryKey) and have their settings applied on startup.

cdc.AddMeilisearchSink("meili", m =>
{
    m.Host = "http://localhost:7700";
    m.ConfigureIndex("products", i => i.Settings = new Settings
    {
        SearchableAttributes = ["name", "description"],
        FilterableAttributes = ["category", "tenantId"],
        SortableAttributes   = ["price"],
    });
});

Settings is Meilisearch's own settings type, so you have full control (ranking rules, stop words, synonyms, faceting, …). Setup is idempotent and re-applied on each leadership acquisition.

Indexes created at runtime — per-tenant indexes from ScopedDestination — are not declared here; they auto-create on first write with the sink's PrimaryKey and use Meilisearch defaults.

How documents are written

• Your transform's CdcDocument fields become the Meilisearch document. Wallaby stamps the configured PrimaryKey field with the record's document id (derived from the source primary key, or your KeyedBy(...) rule) - so you don't include it yourself.
• Document ids are sanitized to Meilisearch's allowed set ([a-zA-Z0-9-_]); composite-key separators are replaced, so composite keys work transparently.
• A transform that returns null for a key (or omits it) issues a delete for that id.
• Records are grouped by index; within an index, upserts are applied before deletes, and distinct indexes are dispatched in parallel.

Delivery semantics

Network/HTTP/task failures are reported as retryable - the dispatcher retries with exponential backoff. With WaitForCompletion = true, a task that finishes Failed/Canceled also surfaces as a failure so the batch isn't acked prematurely. Because Meilisearch upserts are by primary key, redelivery after a crash is safe.

Per-tenant indexes

Route each tenant to its own index with ScopedDestination — see Multi-tenancy.