-
Notifications
You must be signed in to change notification settings - Fork 15
chore: [Orchestration] (and OpenAI) Migrate max_token parameter
#629
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
base: main
Are you sure you want to change the base?
Conversation
max_token parametermax_token parameter
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 would test it once locally to make sure the behaviour is the same
| request = | ||
| request | ||
| .withStop(options.getStopSequences()) | ||
| .withMaxCompletionTokens(options.getMaxTokens()); |
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.
Why change OpenAI, I thought only orchestration deprecated it.
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.
Apparently we didn't even notice that OpenAI deprecated the field last year 😅
rpanackal
left a comment
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
Context
Orchestration BLI
https://github.tools.sap/AI/llm-orchestration/issues/1764
Announcement
https://sap-ml.slack.com/archives/C090TSZ2M1N/p1761228331127799
Discussion
https://sap-ml.slack.com/archives/C070WHEH35L/p1761295434796079
Not changing documented / public API

Definition of Done
Aligned changes with the JavaScript SDKDocumentation updatedRelease notes updated(housekeeping)