Skip to main content

mkpipe-loader-sqlite

SQLite loader plugin for MkPipe. Writes Spark DataFrames into SQLite database files via JDBC.

Documentation

For more detailed documentation, please visit the GitHub repository.

License

This project is licensed under the Apache 2.0 License - see the LICENSE file for details.


Connection Configuration

connections:
  sqlite_target:
    variant: sqlite
    database: /full/path/to/mydb.db

Table Configuration

pipelines:
  - name: pg_to_sqlite
    source: pg_source
    destination: sqlite_target
    tables:
      - name: public.users
        target_name: stg_users
        replication_method: full
        batchsize: 5000

Write Strategy

Control how data is written to SQLite:

      - name: public.users
        target_name: stg_users
        write_strategy: upsert       # append | replace | upsert | merge
        write_key: [id]              # required for upsert/merge
Strategy SQLite Behavior
append Plain INSERT via JDBC (default for incremental)
replace Drop and recreate table, then insert (default for full). With if_exists: append: truncate + insert (preserves schema/indexes)
upsert INSERT ... ON CONFLICT (write_key) DO UPDATE via temp table
merge Same as upsert for SQLite

Write Throughput

      - name: public.users
        target_name: stg_users
        replication_method: full
        batchsize: 5000

Performance Notes

  • SQLite uses file-level locking — write_partitions has no benefit here as concurrent writes will serialize or fail. Set write_partitions: 1 to avoid contention.
  • Keep batchsize moderate (1,000–10,000) — large transactions in SQLite can cause memory pressure.
  • SQLite is best suited for small-to-medium outputs (local development, testing, lightweight pipelines).

All Table Parameters

Parameter Type Default Description
name string required Source table name
target_name string required SQLite destination table name
replication_method full / incremental full Replication strategy
batchsize int 10000 Rows per JDBC batch insert
write_partitions int — Set to 1 to avoid SQLite lock contention
write_strategy string — append, replace, upsert, merge
write_key list — Key columns for upsert/merge (required)
if_exists string — replace (drop+create) or append (preserve table, truncate+insert). Inherits from settings
dedup_columns list — Columns used for mkpipe_id hash deduplication
tags list [] Tags for selective pipeline execution
pass_on_error bool false Skip table on error instead of failing

Metadata

Release files for mkpipe-loader-sqlite 0.7.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mkpipe-loader-sqlite 0.7.0
File Size Uploaded Provenance
mkpipe_loader_sqlite-0.7.0.tar.gz 7.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for mkpipe-loader-sqlite 0.7.0
File Interpreter ABI Platform
mkpipe_loader_sqlite-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 14.8 kB

Release files / mkpipe_loader_sqlite-0.7.0.tar.gz

Download URL mkpipe_loader_sqlite-0.7.0.tar.gz
Size 7.1 kB
Tags Source
SHA-256 checksum
How to use checksums
be91d53904e1673c34ce1ba7688069bf9ed42213e04f4871a0b0bb2cd374df10
BLAKE2b-256 checksum
How to use checksums
f0815436fcf887ff8162dd67cafb277560065b99cc5487ae778e69cf60b67bbe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.15

Release files / mkpipe_loader_sqlite-0.7.0-py3-none-any.whl

Download URL mkpipe_loader_sqlite-0.7.0-py3-none-any.whl
Size 7.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
79fffabcea36f1a944c59fb70a5858f64303c7099d992331d92526dec78cb876
BLAKE2b-256 checksum
How to use checksums
4a22d1087c53664738e20acf31f709d8161cab44ea0339be2e2df06bff8d4fff
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.15

Security for mkpipe-loader-sqlite 0.7.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page