# Event Stream API support

**URL:** <https://forum.yugabyte.com/t/event-stream-api-support/202>\
**Category:** General\
**Created:** [September 18, 2018, 6:02am UTC](https://forum.yugabyte.com/t/event-stream-api-support/202 "2018-09-18T06:02:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joe\_Lour](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Joe\_Lour](https://forum.yugabyte.com/u/Joe_Lour)\
**Post date:** [September 18, 2018, 6:02am UTC](https://forum.yugabyte.com/t/event-stream-api-support/202/1 "2018-09-18T06:02:11Z")

</div>

Hi There , Any plans for event stream listener api ? Use case would be to hookup Solr for full text search and need to listen to the DB events to build search index

---

<div class="post-metadata">

**Author:** ![kannan](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/kannan/32/18_2.png) [@kannan](https://forum.yugabyte.com/u/kannan)\
**Post date:** [September 19, 2018, 7:48am UTC](https://forum.yugabyte.com/t/event-stream-api-support/202/2 "2018-09-19T07:48:54Z")

</div>

This is a roadmap item (essentially a change data capture mechanism) slated for a future release.

Can you share a bit more details? Presumably you want ability to turn this feature on on a per-table basis and capture all changes to the table or finer-grained - such as changes only to specific columns on the table?

---

<div class="post-metadata">

**Author:** ![tinkerbotfoo](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/tinkerbotfoo/32/94_2.png) [@tinkerbotfoo](https://forum.yugabyte.com/u/tinkerbotfoo)\
**Post date:** [April 27, 2019, 5:51pm UTC](https://forum.yugabyte.com/t/event-stream-api-support/202/3 "2019-04-27T17:51:55Z")

</div>

+1

1. CDC event stream. Can be modeled similar to existing systems such as goldengate, dynamodb streams, mongo change streams. (previous version & new version, changed fields only with primary key)
2. **Push Model :** Optional delivery to Kafka and or a webhook with security & authentication
3. **Pull Model :** Optional persistence of change events to another yugabyte table with offsets/ sequence id
4. **Advanced** : Ability to setup multiple subscriptions for delivery of events based on certain filters / conditions met