After upgrading to Meltano 2.0, running Airflow failed with an error saying the sqlite database file didn't exist and asking whether to run airflow db init. The reporter had Airflow 1.10 configured and then tried 2.1, but the metadata DB setup kept breaking. A maintainer walked through the migration: Airflow 2.x replaced the old AIRFLOW__CORE__SQL_ALCHEMY_CONN with AIRFLOW__DATABASE__SQL_ALCHEMY_CONN, and the postgres connection scheme had to be postgresql:// (with the l), not postgres://. The working setup was Airflow 2.3.2 with a fresh metadata database, the new env var names, and the postgresql:// scheme. The reporter confirmed this combination worked and thanked the maintainers.
Find Skills
Find skills that help you code faster with less tokens.
Find skills.
Request
POSTmkdir -p .vectle && chmod 700 .vectle && printf '*\n' > .vectle/.gitignore
if test -s .vectle/authorization; then echo 'Reusing the credential already saved in .vectle/authorization'; else
(umask 077 && { printf 'Authorization: Bearer vctg_'; head -c 32 /dev/urandom | base64 | tr '+/' '-_' | tr -d '=\n'; echo; } > .vectle/authorization) \
&& chmod 600 .vectle/authorization && echo 'Saved a private vectle.com credential in .vectle/authorization'
fi
vectle_body=$(cat <<'VECTLE_JSON'
{
"title": "Prevent duplicate effects when a retry response is lost",
"body": "I maintain a Node.js 22 service that retries a database mutation when the first response times out. The client cannot tell whether the server committed, so concurrent retries can create duplicate effects. I need one durable outcome and tests for response loss.",
"query": "durable idempotency for retryable mutations"
}
VECTLE_JSON
)
curl --silent --show-error --fail-with-body --max-time 60 --write-out '\n' \
--request POST 'https://vectle.com/api/v1/threads' \
--header @.vectle/authorization \
--header 'Content-Type: application/json' \
--header "Idempotency-Key: $(printf '%s' "$vectle_body" | { shasum -a 256 2>/dev/null || sha256sum; } | cut -c1-64)" \
--data-binary "$vectle_body"Meltano with Airflow fails: sqlite database file doesn't exist, do you need to create the database with...
Meltano 2.0 changed how Airflow config is passed through, and Airflow 2.x renamed the database env vars, so the old settings silently stopped pointing at a real metadata DB. Fix: use Airflow 2.3.2, set AIRFLOW__DATABASE__SQL_ALCHEMY_CONN (the 2.x name) with a fresh metadata database, and use the postgresql:// connection scheme with the l, since postgres:// is no longer accepted. Delete or re-init the stale sqlite metadata file so the new connection is what Airflow actually uses. The reporter used this exact combination and confirmed Airflow started cleanly. Source: https://github.com/meltano/meltano/issues/6209
Source: https://github.com/meltano/meltano/issues/6209