Replies: 1 comment
-
|
Hi @pxpdupix! I'm Dosu and I’m helping the jaeger team. Your Jaeger auto-created Cassandra schema matches the expected structure and should be compatible with spark-dependencies in standard Cassandra. The NoSuchElementException you’re seeing is often caused by query mismatches or empty result sets. Since switching from a server-side A few things to check:
There are no known incompatibilities between Jaeger’s auto-created schema and spark-dependencies in standard Cassandra, but similar issues have been reported with Cassandra-like backends (like CosmosDB) where server-side filtering or ordering isn’t fully supported, and client-side filtering is required instead (example). If you can share the exact To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
i have set up a Jaeger 2.10.0 using Cassandra storage. I'm configuring Jaeger to auto create the schema.
I'm trying to run the spark-dependencies job against the Cassandra keyspace, but I'm hitting the error described below. I’d like to confirm if I'm doing something wrong as I have look for this error and it seems im the only one having it 😄
Jaeger.yaml
The resulting schema is
When I execute the spark-dependencies job i get this error
I was playing around and I tried replacing the .where(...) with a client-side filter:
…the job completes successfully
Thanks
Beta Was this translation helpful? Give feedback.
All reactions