hi all , any idea why a flow condition might not be filtering its results , i know the predicate is getting called and that the value its matching on should cause items to be filtered , i only have a single flow condition if that makes a difference

i know that items should be filtered since the return value for the flow condition is true in certain cases

heh as seems to be the case with me many hours later things are working (not sure why ) possibly related to kafka that we are testing

Sometimes I see this error

KeeperErrorCode = BadVersion for /onyx/onyx-kafka/checkpoint/onyx-consumer-test-0

Any ideas why ?

@len Do you see any subsequent errors? That message from ZooKeeper indicates that we did a compare-and-swap that failed, which is alright and possibly expected depending on where it was invoked.

It's seems to work and further issues. It also does not occur all the time

No further issues

It's coming from the Kafka output plugin

So tomorrow will test if we get duplicates. I.e the checkpoint was not saved

ZooKeeper logs a lot of ominous sounding messages at the INFO level that are expected. Leader election algorithms, for example, rely on racing to do a CAS write to a znode. It logs a message that appears to be a warning that a znode has multiple writes attempted when that’s the expected behavior. Shrug

There’s a been a lot of discussion about ZooKeeper changing some of their log level or messages over the years, but it hasn’t budged.

Good news! The first technical preview of our next major release is out. Please read the README at https://github.com/onyx-platform/onyx/tree/0.10.x to see what’s new, and to give it a go. We’re very excited about this release, which greatly simplifies the plugin interfaces, allows for exactly once aggregations without the need for deduplication, and will improve performance over the long run. Check it out and let us know if you hit any trouble. We will be iterating on it to get alphas and betas, and a release out soon.

WOOT!

Sorry, we don’t support sending messages down to downstream tasks yet, but it’s coming in the next week 🙂

Just want to get the API right there. The technical details are easy

We're having issues where we're trying to use Logback, then when Onyx starts, it switches the log engine to something else.

@aengelberg hmm, is it possible that it’s because we’re bringing in [org.slf4j/slf4j-nop “1.7.12”]?

that may be bad practice for a library that is consumed. The other cause would be something that timbre is doing.