Kareemingit opened a new pull request, #12232:
URL: https://github.com/apache/seatunnel/pull/12232

   <!--
   
   Thank you for contributing to SeaTunnel! Please make sure that your code 
changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   ## Contribution Checklist
     - Make sure that the pull request corresponds to a [GITHUB 
issue](https://github.com/apache/seatunnel/issues).
     - Name the pull request in the form "[Feature] [component] Title of the 
pull request", where *Feature* can be replaced by `Hotfix`, `Bug`, etc.
     - Minor fixes should be named following this pattern: `[hotfix] [docs] Fix 
typo in README.md doc`.
   -->
   
   ### Purpose of this pull request
   
   This pull request introduces the **Firebase Connector V2** (Sink) for Apache 
SeaTunnel, enabling data writing capabilities for Google Firebase Realtime 
Database.
   
   Key additions:
   - **Firebase Sink:** Writes batch data to Firebase Realtime Database with 
support for `INSERT`, `UPDATE`, and `DELETE` CDC operations.
   - **Documentation:** Added comprehensive English and Chinese documentation 
(`docs/en/connectors/sink/Firebase.md`, `docs/zh/connectors/sink/Firebase.md`).
   
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. 
   
   This PR adds a new connector plugin (`connector-firebase`)(sink). Users can 
now configure `sink { Firebase { ... } }` in their SeaTunnel HOCON job 
configurations to integrate with Firebase Realtime Database.
   
   ### How was this patch tested?
   
   1. **Unit Tests:** Added tests verifying configuration validation, primary 
key resolution (`key_prefix`, `key_postfix`, composite delimiters), and JSON 
payload formatting.
   2. **E2E Integration Tests:** Added `FirebaseSinkIT` under 
`seatunnel-e2e/seatunnel-connector-v2-e2e` utilizing the official Google 
Firebase Realtime Database Emulator in a Testcontainers environment.
   
   ### Check list
   
   * [ ] If any new Jar binary package adding in your PR, please add License 
Notice according
     [New License 
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
   * [x] If necessary, please update the documentation to describe the new 
feature. https://github.com/apache/seatunnel/tree/dev/docs
   * [ ] If necessary, please update `incompatible-changes.md` to describe the 
incompatibility caused by this PR.
   * [x] If you are contributing the connector code, please check that the 
following files are updated:
     1. Update 
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
 and add new connector information in it
     2. Update the pom file of 
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
     3. Add ci label in 
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
     4. Add e2e testcase in 
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
     5. Update connector 
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
   


-- 
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]

Reply via email to