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

Optimize fetch pathway to avoid decoding more data than required to satisfy consistency #1966

Merged
merged 6 commits into from
Oct 11, 2019

Conversation

richardartoul
Copy link
Contributor

No description provided.

@richardartoul richardartoul changed the title [WIP] - Optimize fetch pathway to avoid decoding more data than required to satisfy consistency Optimize fetch pathway to avoid decoding more data than required to satisfy consistency Oct 10, 2019
@codecov
Copy link

codecov bot commented Oct 10, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@5a830ae). Click here to learn what that means.
The diff coverage is 63.1%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #1966   +/-   ##
=========================================
  Coverage          ?    63.5%           
=========================================
  Files             ?     1121           
  Lines             ?   106180           
  Branches          ?        0           
=========================================
  Hits              ?    67466           
  Misses            ?    34403           
  Partials          ?     4311
Flag Coverage Δ
#aggregator 79.7% <ø> (?)
#cluster 56.4% <ø> (?)
#collector 63.7% <ø> (?)
#dbnode 65% <63.1%> (?)
#m3em 59.6% <ø> (?)
#m3ninx 61.1% <ø> (?)
#m3nsch 51.1% <ø> (?)
#metrics 17.7% <ø> (?)
#msg 74.7% <ø> (?)
#query 68.2% <ø> (?)
#x 75% <ø> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5a830ae...0ef98a8. Read the comment docs.

case ReadConsistencyLevelNone:
return 0
}
panic(fmt.Errorf("unrecognized consistency level: %s", level.String()))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why panic instead of returning an error here? Seems unidiomatic especially for just a simple helper function. If you really want to panic in the client session, it should catch the error thrown here and panic at the client session code.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alllright, seems like all other functions here panic instead of returning an error...

Copy link
Collaborator

@justinjc justinjc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@richardartoul richardartoul merged commit 1260780 into master Oct 11, 2019
@richardartoul richardartoul deleted the ra/optimize-fetch branch October 11, 2019 16:36
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.

2 participants