-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support PostgreSQL event-listener plugin #23281
Comments
cc @mosabua |
IMO the MySQL, Kafka and HTTP event listeners should also live out-of-tree. the SPI is there and community can build and maintain various event listener implementations. At this rate we'll have one for SQLServer, Oracle, Pulsar and maybe more. |
If there is anyone willing to contribute a PostgreSQL event listener .. thats fair game. Feel free to send a PR @nqvuong1998 .. it might even be worth to look at a similar approach as we have for connectors with the BaseJdbcConnector to make implementation easier. In terms of in the main repo or elsewhere as suggested by @hashhar .. for now we would want to go with in the main repo since we are not set up for release process and more with external separate repos and the same reasoning of getting plugins out would apply for connectors. Note that we are trying to improve all that with smarter packaging as well - details in #22597 |
so there is a kafka event listener already ? |
i am just about to merge the docs pr .. has been in the last two releases |
I wrote a simple one for MYSQL in the past - https://github.com/posulliv/trino-simple-db-logger It uses flyway for creating the necessary table in MySQL so you could easily add the SQL for PostgreSQL if you wanted. |
Note that the version from @posulliv is great since it uses flyway .. but is out of date with trino. So if someone starts new .. use the trino project mysql event listener as base and then maybe add the flyway stuff |
PostgreSQL is widely used, but Trino only has MySQL and HTTP event listener plugins. It is essential to add support for PostgreSQL.
The text was updated successfully, but these errors were encountered: