Bug reports can be submitted here. We will try and get it resolved as soon as possible.
First, thanks. We appreciate it! Next, go ahead and fork Zephyr and the Sample Project.
We could really use help fleshing out our support for Storm and Spark Streaming; while we're very confident the design is there and while we've had Zephyr running within Storm already, we just haven't felt very happy
about the level of polish for what code we did have. The more we made our Storm implementation configurable, the less clean and easy to read it all became - to an extreme degree. Rather than
release something we weren't very happy about, we left it out. Unfortunately, all of the data we are running through Zephyr into our system is batch, so we don't really have any pressing business
needs to support Storm. All of this is a long way of saying we'd love your help.
If providing Storm or Spark Streaming support is a bit much for you to chew off, we're more than happy to accept contributions for Parsers, Normalizers, Validators, and Enrichers; in addition to Zephyr and the Zephyr Sample Project, we also have a Zephyr-Contrib project that could house useful code if you're willing to provide it. If you aren't sure where it can go, email Dwayne Pryce and ask - if it's a general purpose parser that doesn't require overly heavyweight libraries, we may even include it in Zephyr Core, but if it's (for example), an HBaseOutputter or something of that ilk, we'd rather have it as a standalone project under the zephyr-contrib umbrella.