Skip to content

Ensure Cassandra bucket number is not negative#599

Merged
yurishkuro merged 1 commit intomasterfrom
unsigned-buckets
Dec 17, 2017
Merged

Ensure Cassandra bucket number is not negative#599
yurishkuro merged 1 commit intomasterfrom
unsigned-buckets

Conversation

@yurishkuro
Copy link
Copy Markdown
Member

Span hash is used for cassandra buckets, but since it's signed it can produce negative numbers.

Related to #587, replaces #595

Resolves jaegertracing/spark-dependencies#23

Signed-off-by: Yuri Shkuro <ys@uber.com>
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling e682d88 on unsigned-buckets into 6baabac on master.

@pavolloffay
Copy link
Copy Markdown
Member

anyways I wanted to update my PR with this change

@yurishkuro
Copy link
Copy Markdown
Member Author

ah ok, wasn't sure. I'll merge this since is't a very small change that evidently solves the spark job issue, but I am not sure about the other PR that changes the DB model.

@yurishkuro yurishkuro merged commit 05c9958 into master Dec 17, 2017
@ghost ghost removed the review label Dec 17, 2017
@pavolloffay
Copy link
Copy Markdown
Member

it seems that storage tests are not sufficient. They were passing even though, query service could not get spans.

@yurishkuro yurishkuro deleted the unsigned-buckets branch December 23, 2017 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants