Feature Request: Add File System Connection Port to SQLite Connector for KNIME Hub Support

[PanteleyShmele1]

Hi KNIME Team,

I would like to request an update to the SQLite Connector node to support remote file systems (specifically KNIME Hub Spaces) directly, similar to how modern file reader nodes work.

The Current Problem: Currently, the SQLite Connector primarily relies on local file paths. While this works fine for local development, it becomes a significant bottleneck when deploying workflows to KNIME Business Hub.

To connect to a .sqlite database stored in a Hub Space, I cannot simply point the node to the file. Instead, I have to build a complex “staging” workflow to:

1. Authenticate with the Hub.

2. Create a temporary local folder.

3. Use Transfer Files to copy the database from the Hub to the temp folder.

4. Extract the local path string.

5. Finally pass that string to the SQLite Connector.

As shown in the attached screenshot, what should be a single node operation turns into a 7-node workaround chain just to establish a connection:

Could you add an optional File System Connection input port (blue square port) to the SQLite Connector node?

This would allow us to connect a KNIME Hub Connector directly to the node and select the database file via the remote path, eliminating the need for temporary file transfers and complex path manipulation.

This would bring the SQLite Connector in line with other modern nodes like Excel Reader or CSV Reader that seamlessly handle remote file systems.

Thanks!

[thor]

In contrast to most reader nodes, which are happy to simply get a data stream for the remote file, SQLite needs random access to the file therefore the file must be available locally. While technically the SQLite connector could do the same preparations as you did manually in your workflow it will give users the false impression that also any modifications (INSERT, DELETE, …) will be mirrored to the remote file. Which is not the case since it’s working on a temporary local copy only.