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.

Sign up for GitHub

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

Jump to bottom

Weaviate: Allow custom HTTP headers to pass to weaviate client #3916

Closed
hsm207 opened this issue Jan 23, 2023 · 0 comments · Fixed by #4040
Closed

Weaviate: Allow custom HTTP headers to pass to weaviate client #3916

hsm207 opened this issue Jan 23, 2023 · 0 comments · Fixed by #4040
Assignees
@vblagoje

Comments

@hsm207
Copy link
Contributor

hsm207 commented Jan 23, 2023 •
edited
Loading

Is your feature request related to a problem? Please describe.
The weaviate client supports passing custom HTTP headers by passing the additional_headers parameter on creation since version 3.9.0. This interface is not exposed in Haystack.

Describe the solution you'd like
The WeaviateDocumentStore constructor should take a parameter named additional_headers that gets passed to the weaviate client on construction.

Describe alternatives you've considered
NA

Additional context
@hsm207 hsm207 changed the title Allow custom HTTP headers to pass to weaviate client Weaviate: Allow custom HTTP headers to pass to weaviate client Jan 27, 2023
@hsm207 hsm207 mentioned this issue Feb 2, 2023
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vblagoje vblagoje

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: add support for custom headers hsm207/haystack
2 participants
@vblagoje @hsm207