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
#493 introduced docker-compose for cassandra storage.
Further improvements could include support for ES storage. We could have one compose file for jaeger services and one compose file per storage. Storage compose file would define (configs)[https://docs.docker.com/compose/compose-file/#configs] which would be used in the main compose file (Similar what we did in k8s jaegertracing/jaeger-kubernetes#53).
Once this is done we could run crossdock against different storages.
The text was updated successfully, but these errors were encountered:
I think we should not be running crossdock against any real/heavy storage. We have storage integration tests. End to end tests don't add much to that, since their goal is testing connectivity between components.
But we do need external storage to be shared between collector and query. The path I see is
badger PR
grpc storage API
run badger behind that grpc API as standalone component
#493 introduced docker-compose for cassandra storage.
Further improvements could include support for ES storage. We could have one compose file for jaeger services and one compose file per storage. Storage compose file would define (configs)[https://docs.docker.com/compose/compose-file/#configs] which would be used in the main compose file (Similar what we did in k8s jaegertracing/jaeger-kubernetes#53).
Once this is done we could run crossdock against different storages.
The text was updated successfully, but these errors were encountered: