Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

Adding query_id to the response headers #43

Merged
merged 2 commits into from
Feb 19, 2024
Merged

Adding query_id to the response headers #43

merged 2 commits into from
Feb 19, 2024

Conversation

jzonthemtn
Copy link
Collaborator

@jzonthemtn jzonthemtn commented Feb 17, 2024

Adding query_id to the response headers for #9.

I'm not sure if this a robust solution and the "right" way to do it, but based on old documentation it should work at least for our purposes right now.

The query ID is set in a query_id header:

curl -v http://localhost:9200/.awesome_events/_search 
*   Trying 127.0.0.1:9200...
* Connected to localhost (127.0.0.1) port 9200 (#0)
> GET /.awesome_events/_search HTTP/1.1
> Host: localhost:9200
> User-Agent: curl/7.81.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< query_id: f2bad461-19cf-41cf-bda5-f6885df0525b                              <------ query_id
< content-type: application/json; charset=UTF-8
< content-length: 502

Copy link
Member

@epugh epugh left a comment

Choose a reason for hiding this comment

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

LGTM

@jzonthemtn jzonthemtn merged commit f26f334 into main Feb 19, 2024
1 check passed
@jzonthemtn jzonthemtn deleted the query_id branch February 19, 2024 23:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants