Re: Some Questions on consuming/restarting/monitoring Apex Kafka consumer

W.r.t. item 3, it may be an issue of whether the group is active or not and whether it has been flushed from the memory cache. Some discussion here: http://grokbase.com/t/kafka/users/15bsxxgp49/new-kafka-consumer-groups-sh-not-showing-inactive-consumer-gorup Ram On Thu, Dec 8, 2016 at 8:36 AM,

Ab initio vs Apex

Hello all, I was wondering if anyone has done any tests comparing Apex with Ab initio. If yes could you please share your experiences. I guess Abinitio is closed source and there is not much I could gather from the internet Regards Ananth

Re: Ab initio vs Apex

Ananth, Customers have talked about Ab initio vs Hadoop-Apex, but there is no data available on any benchmarking or feature compare that I know of. You may want to look at Hadoop vs Ab initio to find data on internet. Thks Amol On Fri, Dec 9, 2016 at 2:19 AM, Ananth G

Dependency confliction

I am having a dependency confliction with my S3 Input Operator using Jackson 2.5.3 and apex using 1.9.2. Is there a way to fix that without excluding the apex Jackson 1.9.2 dependency from my S3 Input Operator pom? Thanks, Austin

Re: Some Questions on consuming/restarting/monitoring Apex Kafka consumer

To add to Ram's point, Kafka Input operator uses Application Name as consumer group name. When you restart the application, it should automatically restart from the stored offset. 1st problem you mentioned is because of the behavior you mentioned in the point 3. Can you please verify Kafka once