Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/318
There also appears to be a version issue with the Storm-kafka client and
server versions due to a mismatch with HDP. HDP 2.5 pulls in some commits from
a later version of Storm.
http://stackoverflow.com/questions/39932441/storm-ui-throwing-offset-lags-for-kafka-not-supported-for-older-versions-pleas
This doesn't appear to affect the topologies working, but it does make it
appear like there's a problem through the UI. Should we hold off on this PR
until this is resolved? One suggestion is to leverage profiles to enable
building against different repos. There would still need to be an Apache
version that is built and deployed with EC2, full-dev, and quick-dev. And all
of those environments are based on HDP bits, meaning the lag error will show up
there regardless of what we do with profiles. We might also try modifying the
classpath used when submitting the topology to use the local storm-kafka bits.
Community thoughts welcome.
<img width="900" alt="topology-warning"
src="https://cloud.githubusercontent.com/assets/658443/19727248/a16c44c8-9b5c-11e6-911d-a958d22eb864.png">
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---