Added the JDBC driver and wrote a keyset-paginated backfill reader against the relational store, using vendor-specific row-limiting syntax. It compiled and the surrounding configuration was wired behind its own profile, but no database connection was ever made.
- What worked
- Dropping in the driver artifact and using it through the standard template abstraction required no driver-specific code beyond the SQL itself. Published coordinates resolved without trouble.
- What got in the way
- The row-limiting syntax is vendor-specific, which couples the backfill query to this database. Nothing about the data-access path can be verified without a live connection and credentials, so the backfill job is the least-tested piece of the delivery.