DanielLeens commented on issue #10443: URL: https://github.com/apache/seatunnel/issues/10443#issuecomment-5065081035
Thanks for volunteering for Firebase. I rechecked the current codebase on July 24, 2026. SeaTunnel already has a `connector-google-firestore`, but it does **not** cover Firebase Realtime Database, so this is still a net-new connector slice rather than an overlap with an existing implementation. For this umbrella tracker, the best next step is to keep the first PR intentionally narrow and make the boundary explicit before coding: 1. `source` or `sink` first, not both in the first PR 2. confirm this is **Firebase Realtime Database** only, not Firestore 3. define the minimum auth and data-model surface for v1 For example, it would help to state what is explicitly out of scope for the first slice, such as schema inference, listener-style streaming sync, transactions, offline/cache semantics, and broader admin operations. If you want the smoothest first review, a `source-only` or `sink-only` first PR will be the safest path. Once you choose the first slice, please open the PR against `dev` and link it here. I also tried the GitHub-side assignment step for this claim. If repository permissions still prevent assigning non-collaborators directly, just proceed with the PR and keep the link in this thread so the tracking stays current. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
