添加链接
link管理
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接
  • Automation & Deployment
  • Automation scenarios, metrics, and checks
  • Production deployments and bundles
  • API Node & API Deployer: Real-time APIs
  • Governance
  • Python APIs
  • R API
  • Public REST API
  • Additional APIs
  • Installation & Administration
  • Installing and setting up
  • Elastic AI computation
  • DSS in the cloud
  • DSS and Hadoop
  • Metastore catalog
  • Operating DSS
  • Security
  • User Isolation
  • Other topics
  • Plugins
  • Streaming data
  • Formula language
  • Custom variables expansion
  • Sampling methods
  • Accessibility
  • Troubleshooting
  • Release notes
  • Other Documentation
  • Third-party acknowledgements
  • Using Conda

    In addition to the builtin mechanisms to create and manage code environments (ie, virtualenv for Python and custom mechanism for R), you can choose to use Conda.

    Conda is a third-party packages management system which provides both Python and R packages.

    Warning

    Tier 2 support : Conda code envs are covered by Tier 2 support

    conda packages repositories tend to be very bleeding-edge, and move quickly, with frequent backwards-incompatibles changes.

    Various incompatibilities may happen, and Dataiku can only provide limited support with setup and usage of conda-based code environments.

    For these reasons, Dataiku does not generally recommend using conda for code environments. We recommend that you only use conda if there are reasons for which you cannot use the native virtualenv and R packages systems.

    Prerequisites

    You need to install miniconda or anaconda. The “conda” binary should be in the PATH of DSS.

    Using Conda environments

    To use Conda for an environment instead of the builtin mechanisms, check the “Use conda” checkbox when creating the environment.

    When managing the packages of a Conda-based environment, you actually need to manage two lists of packages:

  • The list of Conda packages

  • The “regular” list of language packages (either pip requirements or R packages)

  • This is due to the fact that not all packages are available through Conda. For packages not available through Conda, you need to put them in the “regular” list.

    It is strongly recommended not to put the same packages in both lists.