Skip to content

es client afterFn should check the case of resp == nil #1440

Closed

Description

Requirement - jaeger working with ElasticSearch

Problem - jaeger not checking whether es response is nil, and then process panic and exit

Proposal - what do you suggest to solve the problem or improve the existing situation?

add nil pointer check before using es response pointer, such as :

if response.Errors {

Any open questions to address

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions