-
Notifications
You must be signed in to change notification settings - Fork 500
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
Update workflow template documentation #6883
Conversation
Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
@@ -6,9 +6,11 @@ nav_order: 25 | |||
|
|||
# Workflow templates | |||
|
|||
OpenSearch provides several workflow templates for some common machine learning (ML) use cases, such as semantic or conversational search. | |||
OpenSearch provides several workflow templates for some common machine learning (ML) use cases. Using a template simplifies complex setups required for use cases like semantic or conversational search. |
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.
Can we explain here maybe that we also support pre defined template based on a given use case? and also user can give there own template if they want and then link to create workflow API?
Then we can give example:
|
||
You can specify a workflow template when you call the [Create Workflow API]({{site.url}}{{site.baseurl}}/automating-configurations/api/create-workflow/). To provision the workflow, specify `provision=true` as a query parameter. For example, you can configure [neural sparse search]({{site.url}}{{site.baseurl}}/search-plugins/neural-sparse-search/) by providing the `local_neural_sparse_search_bi_encoder` query parameter as `use_case`, as shown in the following request: | ||
For example, you can configure the setup required for [neural sparse search]({{site.url}}{{site.baseurl}}/search-plugins/neural-sparse-search/) by using the `local_neural_sparse_search_bi_encoder` predefined template. When you use a template, the multi-step setup that required running separate API requests is accomplished with a single request. |
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.
I am also still unsure if we should have this as the first example as the other one simplifies a lot more complexity vs this one that simplifies 3 API calls only
Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
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.
Thank you for these changes!
Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
Co-authored-by: Daniel Widdis <widdis@gmail.com> Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com>
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.
LGTM. See my one comment.
@@ -16,7 +16,7 @@ You can automate complex OpenSearch setup and preprocessing tasks by providing t | |||
In OpenSearch 2.12, configuration automation is limited to ML tasks. | |||
{: .info} | |||
|
|||
OpenSearch use case templates provide a compact description of the setup process in a JSON or YAML document. These templates describe automated workflow configurations for conversational chat or query generation, AI connectors, tools, agents, and other components that prepare OpenSearch as a backend for generative models. For template examples, see [Sample templates](https://github.com/opensearch-project/flow-framework/tree/main/sample-templates). | |||
OpenSearch use case templates provide a compact description of the setup process in a JSON or YAML document. These templates describe automated workflow configurations for conversational chat or query generation, AI connectors, tools, agents, and other components that prepare OpenSearch as a backend for generative models. For custom template examples, see [Sample templates](https://github.com/opensearch-project/flow-framework/tree/main/sample-templates). For OpenSearch-provided templates, see [Workflow templates]({{site.url}}{{site.baseurl}}/automating-configurations/workflow-templates/). |
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.
Should AI be defined on first mention?
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.
* Update workflow template documentation Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Tech review comments Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Explain custom and os-provided templates Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Add link to supported templates Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Update _automating-configurations/workflow-templates.md Co-authored-by: Daniel Widdis <widdis@gmail.com> Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> --------- Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Co-authored-by: Daniel Widdis <widdis@gmail.com> (cherry picked from commit eb55593) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* Update workflow template documentation * Tech review comments * Explain custom and os-provided templates * Add link to supported templates * Update _automating-configurations/workflow-templates.md --------- (cherry picked from commit eb55593) Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Daniel Widdis <widdis@gmail.com>
Update workflow template documentation
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.