Databricks finetuning integration #1770
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Databricks finetuning support.
Most of the complexity results from orchestrating the databricks jobs, this integration handles the following things:
Similar to OpenAI provider, we are making blocking calls in
finetune()method, which means the method will block until the serving endpoint is successfully created (or crash in the middle). The blocking method is wrapped in theLM.finetune()method, which sends this blocking method into a background thread. But essentially as the optimizer waits for the finetuning to finish before proceeding, this is still blocking call.Below is the full log of running the
examples/finetune/databricks_finetune.py: