Extractors can take parameters, but none of the current connectors can (StreamConnector, JdbcConnector). This limits connector architectures to preset connectors that are configured once on startup.
There are some compelling scenarios of dynamic connectors, such as getting data from a REST call against the same remote service by passing additional URL parameters not known in advance (very useful when running multiple coordinated tasks, so task 1 retrieves object ids, and task 2 resolves data for those ids).
Per this task going to change StreamConnector method signature to take extractor parameters. Will not change JdbcConnector as it is not an interface, and wouldn't know what to do with parameters (and we'll hopefully redefine the latter connector per #166 )
Extractors can take parameters, but none of the current connectors can (StreamConnector, JdbcConnector). This limits connector architectures to preset connectors that are configured once on startup.
There are some compelling scenarios of dynamic connectors, such as getting data from a REST call against the same remote service by passing additional URL parameters not known in advance (very useful when running multiple coordinated tasks, so task 1 retrieves object ids, and task 2 resolves data for those ids).
Per this task going to change
StreamConnectormethod signature to take extractor parameters. Will not changeJdbcConnectoras it is not an interface, and wouldn't know what to do with parameters (and we'll hopefully redefine the latter connector per #166 )