Create external vector databases with code¶

Loading storage/datarobot_docs/ directory

Splitting 726 documents
Created 3464 documents

FAISS VectorDB has 3464 documents

[Document(page_content="title: Add custom model versions\ndescription: Update a model's contents to create a new version of the model due to new package versions, different preprocessing steps, hyperparameters, etc.\n\nAdd custom model versions {: #add-custom-model-versions }\n\nIf you want to update a model due to new package versions, different preprocessing steps, hyperparameters, and more, you can update the file contents to create a new version of the model. To upload a new version of a custom model environment, see Add an environment version.\n\nCreate a new minor version\n\nWhen you update the contents of a model, the minor version (1.1, 1.2, etc.) of the model automatically updates. To create a minor custom model version, select the model from the Custom Model Workshop and navigate to the Assemble tab. Under the Model header, click Add files and upload the files or folders you updated. The minor version is also updated if you delete a file.\n\nCreate a new major version\n\nTo create a new major version of a model (1.0, 2.0, etc.):\n\nSelect the model from the Custom Model Workshop and navigate to the Assemble tab.\n\nUnder the Model header, click New Version and, in the Create new model version dialog box: \n\n\nSelect a custom model version creation strategy: \n\n\nCopy contents of previous version: Bring the contents of the current version to the new version of the custom model.\n\n\nCreate empty version: Discard the contents of the current version and add new files for the new version of the custom model.\n\n\n\n\nSelect a Base Environment. The environment of the current version is selected by default.\n\n\nEnter a New version description. The version description is optional.", metadata={'source': 'https://docs.datarobot.com/en/docs/mlops/deployment/custom-models/custom-model-workshop/custom-model-versions.html'}),
 Document(page_content="When all fields are complete, click Add. The custom environment is ready for use in the Workshop.\n\nAfter you upload an environment, it is only available to you unless you share it with other individuals.\n\nTo make changes to an existing environment, create a new version.\n\nAdd an environment version {: #add-an-environment-version }\n\nTroubleshoot or update a custom environment by adding a new version of it to the Workshop. In the Versions tab, select New version.\n\nUpload the file for a new version and provide a brief description, then click Add.\n\nThe new version is available in the Verison tab; all past environment versions are saved for later use.\n\nView environment information {: #view-environment-information }\n\nThere is a variety of information available for each custom and built-in environment. To view:\n\nNavigate to Model Registry > Custom Model Workshop > Environments. The resulting list shows all environments available to your account, with summary information.\n\nFor more information on an individual environment, click to select:\n\nThe versions tab lists a variety of version-specific information and provides a link for downloading that version's environment context file.\n\nClick Current Deployments to see a list of all deployments in which the current environment has been used.\n\nClick Environment Info to view information about the general environment, not including version information.\n\nShare and download an environment {: #share-and-download-an-environment }\n\nYou can share custom environments with anyone in your organization from the menu options on the right. These options are not available to built-in environments because all organization members have access and these environment options should not be removed.", metadata={'source': 'https://docs.datarobot.com/en/docs/mlops/deployment/custom-models/custom-model-environments/custom-environments.html'}),
 Document(page_content="Navigate to Model Registry > Custom Model Workshop > Environments. The resulting list shows all environments available to your account, with summary information.\n\nFor more information on an individual environment, click to select:\n\nThe versions tab lists a variety of version-specific information and provides a link for downloading that version's environment context file.\n\nClick Current Deployments to see a list of all deployments in which the current environment has been used.\n\nClick Environment Info to view information about the general environment, not including version information.\n\nShare and download an environment {: #share-and-download-an-environment }\n\nYou can share custom environments with anyone in your organization from the menu options on the right. These options are not available to built-in environments because all organization members have access and these environment options should not be removed.\n\n!!! note\n    An environment is not available in the model registry to other users unless it was explicitly shared. That does not, however, limit users' ability to use blueprints that include tasks that use that environment. See the description of implicit sharing for more information.\n\nFrom Model Registry > Custom Model Workshop > Environments, use the menu to share and/or delete any custom environment that you have appropriate permissions for. (Note that the link points to custom model actions, but the options are the same for custom tasks and environments.)\n\nSelf-Managed AI Platform admins {: #self-managed-ai-platform-admins }\n\nThe following is available only on the Self-Managed AI Platform.\n\nEnvironment availability {: #environment-availability }", metadata={'source': 'https://docs.datarobot.com/en/docs/mlops/deployment/custom-models/custom-model-environments/custom-environments.html'}),
 Document(page_content="Replace a model package {: #replace-a-model-package }\n\nActions (\n\nInventory or the\n\nOverview pages.\n\nYou are redirected to the Overview tab of the deployment. Click Import from to choose your method of model replacement.\n\nLocal File: Upload a model package exported from DataRobot AutoML to replace an existing model package (standalone MLOps users only).\n\nModel Registry: Select a model package from the Model Registry to replace an existing model package.\n\nPaste AutoML URL: Copy the URL of the model from the Leaderboard and paste it into the Replacement Model field.\n\nWhen you have confirmed the model package for replacement, select the replacement reason and click Accept and replace.\n\nModel replacement considerations {: #model-replacement-considerations }\n\nWhen replacing a deployed model, note the following:\n\nModel replacement is available for all deployments. Each deployment's model is provided as a model package, which can be replaced with another model package, provided it is compatible.\n!!! note\n    The new model package cannot be the same leaderboad model as an existing champion or challenger; each challenger must be a unique model. If you create multiple model packages from the same leaderboard model, you can't use those models as challengers in the same deployment.\n\nWhile only the most current model is deployed, model history is maintained and can be used as a baseline for data drift.\n\nModel replacement validation {: #model-replacement-validation }\n\nDataRobot validates whether the new model is an appropriate replacement for the existing model and provides warning messages if issues are found. DataRobot compares the models to ensure that:\n\nThe target names and types match. For classification targets, the class names must match.\n\nThe feature types match.", metadata={'source': 'https://docs.datarobot.com/en/docs/mlops/manage-mlops/deploy-replace.html'})]

# Deploying custom model
  - Unable to auto-detect model type; any provided paths and files will be
    exported - dependencies should be explicitly specified using
    extra_requirements
  - Preparing model and environment...
  - Using environment [[DataRobot] Python 3.9 GenAI
    v4](https://staging.datarobot.com/model-registry/custom-environments/64c964448dd3f0c07f47d040)
    for deployment
  - Configuring and uploading custom model...

    100%|█████████████████████████████████████| 104M/104M [00:00<00:00, 113MB/s]

  - Registered custom model [External DR Knowledge
    Base](https://staging.datarobot.com/model-registry/custom-models/65170268672fcc8004090943/info)
    with target type: Unstructured
  - Creating and deploying model package...

  - Created deployment [External DR Knowledge
    Base](https://staging.datarobot.com/deployments/65170277d708c73281b95de4/overview)
# Custom model deployment complete

# Making predictions
  - Making predictions with deployment [External DR Knowledge
    Base](https://staging.datarobot.com/deployments/65170277d708c73281b95de4/overview)
# Predictions complete
{'relevant': ["title: Add custom model versions\ndescription: Update a model's contents to create a new version of the model due to new package versions, different preprocessing steps, hyperparameters, etc.\n\nAdd custom model versions {: #add-custom-model-versions }\n\nIf you want to update a model due to new package versions, different preprocessing steps, hyperparameters, and more, you can update the file contents to create a new version of the model. To upload a new version of a custom model environment, see Add an environment version.\n\nCreate a new minor version\n\nWhen you update the contents of a model, the minor version (1.1, 1.2, etc.) of the model automatically updates. To create a minor custom model version, select the model from the Custom Model Workshop and navigate to the Assemble tab. Under the Model header, click Add files and upload the files or folders you updated. The minor version is also updated if you delete a file.\n\nCreate a new major version\n\nTo create a new major version of a model (1.0, 2.0, etc.):\n\nSelect the model from the Custom Model Workshop and navigate to the Assemble tab.\n\nUnder the Model header, click New Version and, in the Create new model version dialog box: \n\n\nSelect a custom model version creation strategy: \n\n\nCopy contents of previous version: Bring the contents of the current version to the new version of the custom model.\n\n\nCreate empty version: Discard the contents of the current version and add new files for the new version of the custom model.\n\n\n\n\nSelect a Base Environment. The environment of the current version is selected by default.\n\n\nEnter a New version description. The version description is optional.",
  "When all fields are complete, click Add. The custom environment is ready for use in the Workshop.\n\nAfter you upload an environment, it is only available to you unless you share it with other individuals.\n\nTo make changes to an existing environment, create a new version.\n\nAdd an environment version {: #add-an-environment-version }\n\nTroubleshoot or update a custom environment by adding a new version of it to the Workshop. In the Versions tab, select New version.\n\nUpload the file for a new version and provide a brief description, then click Add.\n\nThe new version is available in the Verison tab; all past environment versions are saved for later use.\n\nView environment information {: #view-environment-information }\n\nThere is a variety of information available for each custom and built-in environment. To view:\n\nNavigate to Model Registry > Custom Model Workshop > Environments. The resulting list shows all environments available to your account, with summary information.\n\nFor more information on an individual environment, click to select:\n\nThe versions tab lists a variety of version-specific information and provides a link for downloading that version's environment context file.\n\nClick Current Deployments to see a list of all deployments in which the current environment has been used.\n\nClick Environment Info to view information about the general environment, not including version information.\n\nShare and download an environment {: #share-and-download-an-environment }\n\nYou can share custom environments with anyone in your organization from the menu options on the right. These options are not available to built-in environments because all organization members have access and these environment options should not be removed.",
  "Navigate to Model Registry > Custom Model Workshop > Environments. The resulting list shows all environments available to your account, with summary information.\n\nFor more information on an individual environment, click to select:\n\nThe versions tab lists a variety of version-specific information and provides a link for downloading that version's environment context file.\n\nClick Current Deployments to see a list of all deployments in which the current environment has been used.\n\nClick Environment Info to view information about the general environment, not including version information.\n\nShare and download an environment {: #share-and-download-an-environment }\n\nYou can share custom environments with anyone in your organization from the menu options on the right. These options are not available to built-in environments because all organization members have access and these environment options should not be removed.\n\n!!! note\n    An environment is not available in the model registry to other users unless it was explicitly shared. That does not, however, limit users' ability to use blueprints that include tasks that use that environment. See the description of implicit sharing for more information.\n\nFrom Model Registry > Custom Model Workshop > Environments, use the menu to share and/or delete any custom environment that you have appropriate permissions for. (Note that the link points to custom model actions, but the options are the same for custom tasks and environments.)\n\nSelf-Managed AI Platform admins {: #self-managed-ai-platform-admins }\n\nThe following is available only on the Self-Managed AI Platform.\n\nEnvironment availability {: #environment-availability }",
  "Replace a model package {: #replace-a-model-package }\n\nActions (\n\nInventory or the\n\nOverview pages.\n\nYou are redirected to the Overview tab of the deployment. Click Import from to choose your method of model replacement.\n\nLocal File: Upload a model package exported from DataRobot AutoML to replace an existing model package (standalone MLOps users only).\n\nModel Registry: Select a model package from the Model Registry to replace an existing model package.\n\nPaste AutoML URL: Copy the URL of the model from the Leaderboard and paste it into the Replacement Model field.\n\nWhen you have confirmed the model package for replacement, select the replacement reason and click Accept and replace.\n\nModel replacement considerations {: #model-replacement-considerations }\n\nWhen replacing a deployed model, note the following:\n\nModel replacement is available for all deployments. Each deployment's model is provided as a model package, which can be replaced with another model package, provided it is compatible.\n!!! note\n    The new model package cannot be the same leaderboad model as an existing champion or challenger; each challenger must be a unique model. If you create multiple model packages from the same leaderboard model, you can't use those models as challengers in the same deployment.\n\nWhile only the most current model is deployed, model history is maintained and can be used as a baseline for data drift.\n\nModel replacement validation {: #model-replacement-validation }\n\nDataRobot validates whether the new model is an appropriate replacement for the existing model and provides warning messages if issues are found. DataRobot compares the models to ensure that:\n\nThe target names and types match. For classification targets, the class names must match.\n\nThe feature types match."]}