Hi all, I would instead recommend to actually add it to the duckdb repo, if that’s possible. The reason is, that usually this way the plugin receives more attention by the folks that the integration is for. Also do the people very knowledgeable about the target platform usually come back with interesting feedback, which usually doesn’t happen if it’s in a completely disconnected repo.
With PLC4X we also try to develop plugins in the PLC4X project, but move them over to the target platforms as soon as possible. Also with really separate repos for every target, the beaurocratic effort for the TsFile project increases. That’s why for example we have all integration modules in PLC4X in a plc4x-extras repo so we don’t have to release 100 individual reos (Each one requiring the full staging, reviewing, voting, releasing process) Just my opinion … Chris Von: ColinLee <[email protected]> Datum: Freitag, 7. August 2026 um 05:48 An: [email protected] <[email protected]> Betreff: Re:Re: [DISCUSS] Integrate Apache TsFile with DuckDB Hi Yuan, Thanks for the suggestion. I agree with creating the repository as: https://github.com/apache/tsfile-duckdb The name clearly reflects the integration between Apache TsFile and DuckDB. I can prepare the initial code and documentation for the new repository. Best regards, Colin Lee At 2026-08-07 11:28:41, "Yuan Tian" <[email protected]> wrote: >Hi Colin, > >I think we can add a new repo under apache github org: >https://github.com/apache, and named it as >https://github.com/apache/tsfile-duckdb > >What do you think? > > >Best regards, >-------------------- >Yuan Tian > >On Fri, Aug 7, 2026 at 11:25 AM ColinLee <[email protected]> wrote: > >> Hi all, >> >> >> I have created an experimental DuckDB extension to query Apache TsFile >> table-model files directly: >> >> >> https://github.com/ColinLeeo/tsfile-duckdb >> >> >> The extension exposes a table function such as: >> >> >> SELECT time, timeseries_id, value >> FROM read_tsfile('/data/measurements.tsfile', 'greend_1') >> WHERE time BETWEEN 100000 AND 200000; >> >> >> The current implementation includes: >> >> >> 1. Integration of the TsFile C++ reader with DuckDB's table function API. >> 2. Static builds of TsFile and its compression dependencies. >> 3. TsFile-to-DuckDB type mapping and streaming result batches. >> 4. Projection pushdown and time predicate pushdown. >> 5. Build verification on Linux, macOS, and Windows through DuckDB Community >> Extensions CI. >> >> >> The DuckDB Community Extensions PR is available here: >> >> >> https://github.com/duckdb/community-extensions/pull/2435 >> >> >> Based on this initial implementation and validation, I would like to >> discuss >> bringing this work into a repository under the Apache TsFile organization. >> The current repository is still hosted under my personal GitHub account: >> >> >> https://github.com/ColinLeeo/tsfile-duckdb >> >> >> If the community agrees with this direction, we can move the DuckDB >> extension >> to an Apache-owned repository in a future step. >> >> >> The current prototype supports one local TsFile and one table per query. >> Directory scans, automatic table discovery, multi-file scans, and >> DuckDB-WASM support are not included yet. >> >> >> Reviews and suggestions are welcome. >> >> >> Best regards, >> >> >> Colin Lee
