Custom pipes for Docker and Snowflake and deprecate nlu_ref #1869
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.
Improvements to Docker integration
Instead of providing a nlu model reference for deploying a model, users have now 2 options
1) Deploy Pipeline via Name, Language and Bucket
2.1) Deploy custom pipeline by providing a fitted pipeline object
2.2) Deploy NLU pipelines as container
Any nlu pipeline can still be deployed as a custom pipe
Improvements to Snowflake integration
compute_pool_min_nodes
,compute_pool_max_nodes
,compute_pool_instance_family
can now be configured innlp.snowflake_common_setup
with values defined in the Snowflake DocumentationSince the Snowflake integration uses the Docker, all of the changes for the docker utilities are reflected into Snowflake as well.
Instead of providing a nlu model reference for deploying a model, users have now 2 options
Deploy Pipeline via Name, Language and Bucket
Deploy custom pipeline by providing a fitted pipeline object
Deploy NLU pipelines as container
Any nlu pipeline can still be deployed