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

Don't panic if presented with a field of unknown type #2166

Merged
merged 1 commit into from
Apr 4, 2015

Conversation

otoolep
Copy link
Contributor

@otoolep otoolep commented Apr 3, 2015

This can happen, though is very unlikely. If this node receives encoded
data, to be written to disk, and is queried for that data before its
metastore is updated, there will be no field mapping for the data during
decode. All this can happen because data is encoded by the node that first
received the write request, not the node that actually writes the data to
disk. So if this happens, skip the data.

@otoolep
Copy link
Contributor Author

otoolep commented Apr 3, 2015

@benbjohnson @jwilder

@otoolep otoolep force-pushed the dont_panic_on_missing_field_mapping branch from 6020ebb to 9a2ac21 Compare April 3, 2015 22:22
// mapping for the data during decode. All this can happen because data is encoded by the node
// that first received the write request, not the node that actually writes the data to disk.
// So if this happens, skip the data.
continue
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually, I need to push the reader ahead -- let me fix this.

@jwilder
Copy link
Contributor

jwilder commented Apr 3, 2015

LGTM

@otoolep otoolep force-pushed the dont_panic_on_missing_field_mapping branch from 9a2ac21 to af0d59b Compare April 3, 2015 23:01
@toddboom
Copy link
Contributor

toddboom commented Apr 4, 2015

👍

@pauldix
Copy link
Member

pauldix commented Apr 4, 2015

@otoolep needs a rebase. Will merge on green

@benbjohnson
Copy link
Contributor

👍

This can happen, though is very unlikely. If this node receives encoded
data, to be written to disk, and is queried for that data before its
metastore is updated, there will be no field mapping for the data during
decode. All this can happen because data is encoded by the node that first
received the write request, not the node that actually writes the data to
disk. So if this happens, skip the data.
@otoolep otoolep force-pushed the dont_panic_on_missing_field_mapping branch from af0d59b to 501b4ce Compare April 4, 2015 17:34
otoolep added a commit that referenced this pull request Apr 4, 2015
…pping

Don't panic if presented with a field of unknown type
@otoolep otoolep merged commit 8a0f67f into master Apr 4, 2015
@otoolep otoolep deleted the dont_panic_on_missing_field_mapping branch April 4, 2015 17:39
mark-rushakoff pushed a commit that referenced this pull request Jan 11, 2019
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.

5 participants