Is the new enrich-kensis a drop-in replacement for Stream Enrich?

The release notes of Enrich 3.0.0 introduced the new enrich-kensis enricher. It’s mentioned that in time, it will replace the existing Stream Enrich. Can we start using the enrich-kensis as a replacement for the Stream Enrich? Is it a drop-in replacement?

I’m looking forward to using the CloudWatch metrics and automatic asset refresh.

If I look at the number of downloads on Docker Hub, I only see around 2.9K downloads compared to 1M+ for the existing Stream Enrich. So, I’m a bit hesitant to make the switch because the docs don’t explicitly mention that it’s a drop-in replacement.

Hi @armand ,

Welcome to Snowplow community !

Yes ! We’ve already started to roll it out internally. The latest version is 3.1.3.

That’s normal, Stream Enrich was created way before new enrich-kinesis, which is new. Our plan is to deprecate Stream Enrich as soon as enrich-kafka and enrich-nsq are ready.

1 Like

Hi Ben! Thank you for the welcome and thank you for the confirmation. Excited to test out the new features.

2 Likes