You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.Update operator to use jaeger 1.65.0
2. Deploy jaeger with cassandra
3. See the schema container fails
Expected behavior
The correct template should be applied, no errors
Relevant log output
Using template file /cassandra-schema/v004-go-tmpl.cql.tmpl with parameters:
mode = test
datacenter = datacenter3
keyspace = jaeger_v1_datacenter3
replication = {'class': 'SimpleStrategy', 'replication_factor': '1'}
trace_ttl = 172800
dependencies_ttl = 0
compaction_window_size = 96
compaction_window_unit = MINUTES
<stdin>:5:SyntaxException: line 1:0 no viable alternative at input 'HOLA' ([HOLA]...)
<stdin>:15:SyntaxException: line 1:26 no viable alternative at input '{' (CREATE TYPE IF NOT EXISTS [{]...)
<stdin>:20:SyntaxException: line 1:26 no viable alternative at input '{' (CREATE TYPE IF NOT EXISTS [{]...)
<stdin>:26:SyntaxException: line 1:26 no viable alternative at input '{' (CREATE TYPE IF NOT EXISTS [{]...)
<stdin>:31:SyntaxException: line 1:26 no viable alternative at input '{' (CREATE TYPE IF NOT EXISTS [{]...
Screenshot
No response
Additional context
No response
Jaeger backend version
1.65.0
SDK
No response
Pipeline
No response
Stogage backend
Cassandra
Operating system
Linux
Deployment model
No response
Deployment configs
The text was updated successfully, but these errors were encountered:
What happened?
Is trying to apply the golang template.
Steps to reproduce
1.Update operator to use jaeger 1.65.0
2. Deploy jaeger with cassandra
3. See the schema container fails
Expected behavior
The correct template should be applied, no errors
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
1.65.0
SDK
No response
Pipeline
No response
Stogage backend
Cassandra
Operating system
Linux
Deployment model
No response
Deployment configs
The text was updated successfully, but these errors were encountered: