Module com.darkcollective.relix.processor

Package com.darkcollective.relix.processor.connector.internal

package com.darkcollective.relix.processor.connector.internal
The engine-side machinery behind com.darkcollective.relix.processor.connector: not exported by the published artifact. What follows describes the package as a whole, as it stood before the split. The pluggable connector SPI — the open replacement for the closed, three-way CSV/JSON/JDBC connector dispatch.

A RelixConnector bridges one or more type tokens (the word after from in a connection declaration) to the executor's Row model, reading its backend-specific settings from a type-agnostic ConnectorConfig. Capabilities (schema introspection, statistics, query pushdown) are opt-in via the optional methods a connector overrides.

The ConnectorRegistry indexes connectors by token and dispatches to them: built-ins are discovered from the module path via ServiceLoader, while external plugins are loaded from ~/.relix/connectors/ by a ConnectorPluginLoader — so a new backend (e.g. MongoDB) ships as a JAR with no rebuild of relix.

  • Classes
    Class
    Description
    ConnectorPluginLoader
    Loads external RelixConnector plugins from JAR files in a connector directory — ~/.relix/connectors/ by default, overridable via RELIX_CONNECTORS.
    ConnectorRegistry
    The open dispatch point for connectors — it replaces the hardcoded CompositeDataSourceConnector switch.
    DriverDownloader
    Downloads driver Artifacts into the driver directory, verifying each against its SHA-256 before it is trusted.