Skip to content
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

Make dependencies_v2 the default for Cassandra #1344

Closed
yurishkuro opened this issue Feb 13, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@yurishkuro
Copy link
Member

commented Feb 13, 2019

After #1328 is released:

  • make dependencies_v2 the default for Cassandra
  • make v002 schema the default
  • fix documentation

@yurishkuro yurishkuro referenced this issue Feb 13, 2019

Closed

Release 1.11 scope #1343

2 of 3 tasks complete
@pavolloffay

This comment has been minimized.

Copy link
Member

commented Feb 27, 2019

I have marked * make v002 schema the default as done - the create schema script uses the new schema by default.

The make dependencies_v2 the default for Cassandra can be also considered done - Jaeger components uses v2 if dependencies_v2 table is present.

So is there anything apart from docs what should be done? What docs should be updated? How to migrate to v2?

cc @black-adder

@pavolloffay

This comment has been minimized.

Copy link
Member

commented Mar 7, 2019

I am closing this:

  • V2 schema is used by default in create schema script and docker image
  • migrations steps are in changelog
  • jaeger binaries automatically regognizes if v2 schema is initialized

@pavolloffay pavolloffay closed this Mar 7, 2019

@pavolloffay

This comment has been minimized.

Copy link
Member

commented Mar 11, 2019

Note that Cassandra create schema script creates keyspace jaeger_v1_${datacenter} (note V1 in name) for V1 and V2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.