Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/531
@basvdl I should have first said, thanks for all your hard work!
You probably have already thought through many of these options, so please
educate me on their pros/cons. I am going to lay out all of the possibilities
that I can think of just so that we don't leave any stone unturned.
(1) Alter the Source of Telemetry - This is the option that you chose.
This has the downside that we now have a forked, external dependency that we
are relying on you to maintain going forward. That's a lot of work for you!
(2) Use an Alternative Source of Telemetry - Is there an alternative to
`DHCPDump` out there that we could use instead? I think this would be the
simplest approach assuming one exists.
(3) Reunite lines at the parser - Each line would come in as a separate
Kafka message. We cannot rely on ordering of those messages, so we would need
some kind of unique identifier contained within each message to then reunite
them all into a single DHCPDump record. This would be very different from our
current architecture and is not currently supported.
(4) Transport Mechanism - How do you envision getting the DHCPDump records
into Kafka? aka the transport mechanism? No matter what, we need some kind of
transport mechanism. You could potentially create a solution that takes the
separate record lines, stitches them into a single line, then pushes them to
Kafka as a complete DHCPDump record.
---
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.
---
