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.

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

[DOC] Document the request/response format required by neural search for data exchange facilitated by AI connectors #5699

Open
3 tasks
dylan-tong-aws opened this issue Nov 29, 2023 · 1 comment

Comments

@dylan-tong-aws
Copy link

What do you want to do?

Document the request/response format required by neural search for data exchange facilitated by AI connectors.

  • Request a change to existing documentation
  • [ x] Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request and all versions that are affected.

Document the request/response format required by neural search for data exchange facilitated by AI connectors.

Connectors that are designed for powering neural search will receive requests in a specific format. Neural search also requires a response in a specific format. Users need to know the format of the request and respond payload for various reasons like:

  1. If I'm an integrator and I'm building a connector blueprint, I need to know the format to implement the appropriate pre/post processing logic
  2. If I'm an application developer who wants to integrate a custom model via the Amazon SageMaker connector, I need to know the format so that I can write the appropriate pre/post processing logic in my model serving script.

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

@hdhalter
Copy link
Contributor

hdhalter commented Dec 5, 2023

@dylan-tong-aws - Can you please provide the format for the request/response?

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

No branches or pull requests

2 participants