Use a FunctionName.REMOTE for all ML inference requests - #1897
Conversation
PR Code Analyzer ❗AI-powered 'Code-Diff-Analyzer' found issues on commit 800191f.
The table above displays the top 10 most important findings. Pull Requests Author(s): Please update your Pull Request according to the report above. Repository Maintainer(s): You can Thanks. |
PR Reviewer Guide 🔍(Review updated until commit bbc551c)Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1897 +/- ##
============================================
- Coverage 83.46% 83.44% -0.03%
+ Complexity 3893 3891 -2
============================================
Files 291 291
Lines 13835 13829 -6
Branches 2300 2298 -2
============================================
- Hits 11547 11539 -8
- Misses 1455 1457 +2
Partials 833 833 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
FunctionName is not used by ml-commons for inference, so centralize it as a single DEFAULT_FUNCTION_NAME constant (REMOTE) and remove it from all internal method signatures to avoid confusion. Signed-off-by: Heemin Kim <heemin@amazon.com>
|
Persistent review updated to latest commit bbc551c |
|
Description
FunctionName is not used by ml-commons for inference, so centralize it as a single FunctionName.REMOTE and remove it from all internal method signatures to avoid confusion.
Related Issues
opensearch-project/ml-commons#4891
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.