jaeger v1.10.0 Release Notes

Release Date: 2019-02-15 // about 5 years ago
  • Backend Changes

    ๐Ÿ’ฅ Breaking Changes

    Migration Path:

    1. Run plugin/storage/cassandra/schema/migration/v001tov002part1.sh which will copy dependencies into a csv, update the dependency UDT, create a new dependencies_v2 table, and write dependencies from the csv into the dependencies_v2 table.
    2. Run the collector and query services with the cassandra flag cassandra.enable-dependencies-v2=true which will instruct jaeger to write and read to and from the new dependencies_v2 table. โšก๏ธ 3. Update spark job to write to the new dependencies_v2 table. The feature will be done in #58. ๐Ÿ”Œ 4. Run plugin/storage/cassandra/schema/migration/v001tov002part2.sh which will DELETE the old dependency table and the SASI index.

    ๐Ÿšš Users who wish to continue to use the v1 table don't have to do anything as the cassandra flag cassandra.enable-dependencies-v2 will default to false. Users may migrate on their own timeline however new features will be built solely on the dependencies_v2 table. In the future, we will remove support for v1 completely.

    • โœ‚ Remove ErrorBusy metric, it essentially duplicates SpansDropped (#1091, @cstyan)

    ๐Ÿ†• New Features

    ๐Ÿ› Bug fixes, Minor Improvements

    • ๐Ÿ‘‰ Use Zipkin annotations if the timestamp is zero (#1341, @geobeau)
    • ๐Ÿ‘‰ Use GRPC round robin balancing even if only one hostname (#1329, @benley)
    • Tolerate whitespaces in ES servers and kafka brokers (#1305, @verma-varsha)
    • Let cassandra servers contain whitespace in config (#1301, @karlpokus)

    ๐Ÿ’ป UI Changes