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

[dbnode] Fix overzealous log message for missing schema with non-protobuf namespace #2013

Merged
merged 4 commits into from
Oct 25, 2019

Conversation

robskillington
Copy link
Collaborator

What this PR does / why we need it:

This was confusing as an operator since this is not an error state, it is the regular expected case when operating a DB node with namespaces that are not configured with protobuf schemas.

Special notes for your reviewer:

Does this PR introduce a user-facing and/or backwards incompatible change?:

NONE

Does this PR require updating code package or user-facing documentation?:

NONE

Copy link
Collaborator

@benraskin92 benraskin92 left a comment

Choose a reason for hiding this comment

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

couple nits, but lgtm

zap.String("currentSchema", curSchemaID))
merr = merr.Add(fmt.Errorf("can not update namespace(%v) schema to empty", metadata.ID().String()))
if !curSchemaNone {
// NB(r): Only interpret this as a warning/error if already had a schema
Copy link
Collaborator

Choose a reason for hiding this comment

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

, at end.

@@ -33,35 +33,53 @@ func UpdateSchemaRegistry(newNamespaces Map, schemaReg SchemaRegistry, log *zap.
schemaUpdates := newNamespaces.Metadatas()
merr := xerrors.NewMultiError()
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe name this multiErr?

@codecov
Copy link

codecov bot commented Oct 22, 2019

Codecov Report

Merging #2013 into master will decrease coverage by 2.4%.
The diff coverage is 36.6%.

Impacted file tree graph

@@           Coverage Diff            @@
##           master   #2013     +/-   ##
========================================
- Coverage    71.7%   69.3%   -2.5%     
========================================
  Files        1007     999      -8     
  Lines       86272   86288     +16     
========================================
- Hits        61932   59840   -2092     
- Misses      20162   22187   +2025     
- Partials     4178    4261     +83
Flag Coverage Δ
#aggregator 71.3% <ø> (+15.4%) ⬆️
#cluster 58% <ø> (-7.3%) ⬇️
#collector 35.3% <ø> (+0.2%) ⬆️
#dbnode 73.1% <36.6%> (-3.8%) ⬇️
#m3em 28.8% <ø> (-21.5%) ⬇️
#m3ninx 71% <ø> (+36.7%) ⬆️
#m3nsch 60.6% <ø> (+0.5%) ⬆️
#metrics 17.7% <ø> (-11.3%) ⬇️
#msg 32% <ø> (-19.5%) ⬇️
#query 70.6% <ø> (+0.5%) ⬆️
#x 64.7% <ø> (+4.1%) ⬆️

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 b39a79f...4360c02. Read the comment docs.

@notbdu notbdu force-pushed the r/namespace-registry-update branch 2 times, most recently from d19d29b to b10442c Compare October 25, 2019 19:36
@notbdu notbdu force-pushed the r/namespace-registry-update branch from ea5a454 to 4360c02 Compare October 25, 2019 20:33
@notbdu notbdu merged commit 9baa7da into master Oct 25, 2019
@notbdu notbdu deleted the r/namespace-registry-update branch October 25, 2019 20:50
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