-
Notifications
You must be signed in to change notification settings - Fork 10
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
filter presets and processors based on backend version #537
Conversation
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.
Getting close! Few comments.
Only remaining piece I think we can add is integrating with the quick-configure fields for the newly-added presets. This will help set defaults for the text embedding & text/image embedding processors, such as the model IDs, fields, etc.
You can look at the quick configure components here for some reference: https://github.com/opensearch-project/dashboards-flow-framework/tree/main/public/pages/workflows/new_workflow
I wouldn't consider a blocker for this PR though. I'll follow up by pulling these changes and testing locally for another sanity test as well, once you've addressed comments. Thanks!
@kamahuan Btw, I'm ok to close the previous PRs, quickly went through comments, nothing else to carry over. |
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.
Few remaining things, getting closer. Some more items from previous review I've unresolved as well, please have a look.
In general, it is much easier from my end to add comments / details into the changes made for each comment instead of just resolving, otherwise I have to go digging for each individually. please consider for the future :)
public/pages/workflow_detail/workflow_inputs/processors_list.tsx
Outdated
Show resolved
Hide resolved
public/pages/workflow_detail/workflow_inputs/processors_list.tsx
Outdated
Show resolved
Hide resolved
public/pages/workflow_detail/workflow_inputs/processors_list.tsx
Outdated
Show resolved
Hide resolved
Hey Tyler, I think the loading state might due to that we do not have any data source configured. Once we configured a datasource, it will show the presets. The loading state is added to indicate when the user first render the page and not data source is configured. |
There should be a check if multiple data source (MDS) is disabled, which is the default / existing behavior, and if so, not do such checks. If it is disabled, we can assume it is 2.19+. |
Gotcha, will add this check |
public/pages/workflow_detail/workflow_inputs/processors_list.tsx
Outdated
Show resolved
Hide resolved
5e853ab
to
af7ed8c
Compare
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.
Tested locally on a 2.19 cluster, built semantic search and RAG workflows, checked the processor lists etc. Noticed a few regressions on the existing preset values, should be one line changes a few places.
Other than that LGTM! Will approve after those changes are made.
and change enrich data section processors based on the version. Signed-off-by: Kama Huang <[email protected]>
Signed-off-by: Kama Huang <[email protected]>
…ading the page. If disabled, the version should be set to 2.19+ Signed-off-by: Kama Huang <[email protected]>
…ersion to 2.19 Signed-off-by: Kama Huang <[email protected]>
Signed-off-by: Kama Huang <[email protected]>
Signed-off-by: Kama Huang <[email protected]>
Signed-off-by: Kama Huang <[email protected]>
…workflows file and modify processors for each preset in the fetch function Signed-off-by: Kama Huang <[email protected]>
Signed-off-by: Kama Huang <[email protected]>
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!
Please follow up by front-porting to main (3.0) branch. |
Signed-off-by: Kama Huang <[email protected]> Co-authored-by: Kama Huang <[email protected]> (cherry picked from commit ea08b7d) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
(cherry picked from commit ea08b7d) Signed-off-by: Kama Huang <[email protected]> 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: Kama Huang <[email protected]>
Filter presets and processors based on backend version
Description
This PR consists of 3 parts:
If no datasource is configured during the first render, the create work flow page will have a loading state.
Issues Resolved
NONE
Check List
--signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.