Yeah, I can confirm that the issue is persists and that it is unrelated to version mismatch.
I also rolled back to 2.3.0 and it works. I suspect the issue is associated with this commit removing listenable future from guava during packaging. I’ll take a stab at fixing this issue within this week if the committer doesn’t get to it by then. On Sun, Oct 7, 2018 at 7:33 AM Asmir Avdicevic <notificati...@github.com> wrote: > I've currently just fixed the beam-sdks-java-io-cassandra to 2.3.0 while > keeping the rest to 2.5.0 > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/beam/pull/5112#issuecomment-427646175>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAj24keMpzGMyjeqPQMCdpJbsz1wMP2bks5uieaXgaJpZM4TRSVJ> > . > [ Full content available at: https://github.com/apache/beam/pull/5112 ] This message was relayed via gitbox.apache.org for devnull@infra.apache.org
