-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add support for array parsing in azure-eventhub input #18585
Conversation
Pinging @elastic/integrations (Team:Integrations) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
|
// in some cases the message is an array | ||
a.log.Debugw(fmt.Sprintf("deserializing multiple messages using the group object `records`"), "warning", err) | ||
var arrayObject []interface{} | ||
err = json.Unmarshal(bMessage, &arrayObject) |
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.
No error checking in this line?
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.
hmm, somehow I missed it, also updated the tests
* add array as parser * changelog * update test (cherry picked from commit c742662)
* add array as parser * changelog * update test (cherry picked from commit c742662)
What does this PR do?
Adds support to parse array of eventhub messages into separate events.
Expected type was an object containing a list of messages.
Why is it important?
List of eventhub messages were published in single Elasticsearch event.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Ex before:
to: