-
Notifications
You must be signed in to change notification settings - Fork 202
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
Remove validation that made keys starting or ending with . - or _ invalid, catch all exceptions in the parse json processor #2936
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -64,34 +64,37 @@ public Collection<Record<Event>> doExecute(final Collection<Record<Event>> recor | |
final boolean doUsePointer = Objects.nonNull(pointer); | ||
|
||
for (final Record<Event> record : records) { | ||
final Event event = record.getData(); | ||
|
||
if (Objects.nonNull(parseWhen) && !expressionEvaluator.evaluateConditional(parseWhen, event)) { | ||
continue; | ||
} | ||
|
||
final String message = event.get(source, String.class); | ||
if (Objects.isNull(message)) { | ||
continue; | ||
} | ||
|
||
try { | ||
final TypeReference<HashMap<String, Object>> hashMapTypeReference = new TypeReference<HashMap<String, Object>>() {}; | ||
Map<String, Object> parsedJson = objectMapper.readValue(message, hashMapTypeReference); | ||
|
||
if (doUsePointer) { | ||
parsedJson = parseUsingPointer(event, parsedJson, pointer, doWriteToRoot); | ||
} | ||
|
||
if (doWriteToRoot) { | ||
writeToRoot(event, parsedJson); | ||
} else { | ||
event.put(destination, parsedJson); | ||
final Event event = record.getData(); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: seems like this block is double indented which is showing more of a diff than there actually is |
||
try { | ||
if (Objects.nonNull(parseWhen) && !expressionEvaluator.evaluateConditional(parseWhen, event)) { | ||
continue; | ||
} | ||
|
||
final String message = event.get(source, String.class); | ||
if (Objects.isNull(message)) { | ||
continue; | ||
} | ||
final TypeReference<HashMap<String, Object>> hashMapTypeReference = new TypeReference<HashMap<String, Object>>() { | ||
}; | ||
Map<String, Object> parsedJson = objectMapper.readValue(message, hashMapTypeReference); | ||
|
||
if (doUsePointer) { | ||
parsedJson = parseUsingPointer(event, parsedJson, pointer, doWriteToRoot); | ||
} | ||
|
||
if (doWriteToRoot) { | ||
writeToRoot(event, parsedJson); | ||
} else { | ||
event.put(destination, parsedJson); | ||
} | ||
} catch (final JsonProcessingException jsonException) { | ||
event.getMetadata().addTags(tagsOnFailure); | ||
LOG.error(EVENT, "An exception occurred due to invalid JSON while reading event [{}]", event, jsonException); | ||
} catch (final Exception e) { | ||
event.getMetadata().addTags(tagsOnFailure); | ||
LOG.error(EVENT, "An exception occurred while using the parse_json processor on Event [{}]", event, e); | ||
} | ||
} catch (final JsonProcessingException jsonException) { | ||
event.getMetadata().addTags(tagsOnFailure); | ||
LOG.error(EVENT, "An exception occurred due to invalid JSON while reading event [{}]", event, jsonException); | ||
} | ||
} | ||
return records; | ||
} | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
What was the motivation for not allowing these characters initially? I'm wondering what the consequences of this change would be
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.
I am not sure what the reasoning was
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.
This is the PR where I added this custom code (https://github.com/opensearch-project/data-prepper/pull/725/files). But the regex pattern that was used to validate before (which disallowed starting or ending with these characters) was added by @cmanning09