-
Notifications
You must be signed in to change notification settings - Fork 453
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
Conversation
There was a problem hiding this 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 |
There was a problem hiding this comment.
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() |
There was a problem hiding this comment.
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 Report
@@ 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
Continue to review full report at Codecov.
|
d19d29b
to
b10442c
Compare
ea5a454
to
4360c02
Compare
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?:
Does this PR require updating code package or user-facing documentation?: