New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zipkin trace is not continued #3
Comments
Hmm, might be related to https://issues.apache.org/jira/browse/CASSANDRA-11706. |
@hkroger And you are sure that cassandra is running with |
Yes, it turned out to be the bug in the Cassandra 3.9. It works fine with 3.10.SNAPSHOT. |
This could be fixed also in this cassandra zipkin tracing module. It was partially already done, I think but this would need to be done as well in the
|
This change can be seen in with
|
Actually it's not completely fixed in 3.10.SNAPSHOT. I created a JIRA ticket: https://issues.apache.org/jira/browse/CASSANDRA-12835 |
CASSANDRA-12835 got resolved |
I'm testing out the cassandra-zipkin-tracing and I have an issue with custom payload. The application sends out the trace and custom payload existence is shown by the datastax driver:
However when I added some logging as seen in the PR that I created (https://github.com/thelastpickle/cassandra-zipkin-tracing/pull/2/files), I'm getting only
I'm running Cassandra 3.9 and using prepared statements (using the object mapper).
Is it a problem with Cassandra? Cassandra driver is 3.1.1.
The text was updated successfully, but these errors were encountered: