Feedstock license: BSD-3-Clause
Home: https://tiledb.com
Package license: MIT
Summary: TileDB Vector Search
Development: https://github.com/TileDB-Inc/TileDB-Vector-Search
Documentation: https://tiledb-inc.github.io/TileDB-Vector-Search
TileDB Vector Search is an open source, lightweight, embeddable, and cloud-native vector similarity search database implemented in high-performance C++ with an easy Python API.
| Azure |
|
| Name | Downloads | Version | Platforms |
|---|---|---|---|
 |
 |
 |
 |
Installing tiledb-vector-search from the tiledb channel can be achieved by adding tiledb to your channels with:
conda config --add channels tiledb
conda config --set channel_priority strict
Once the tiledb channel has been enabled, tiledb-vector-search can be installed with conda:
conda install tiledb-vector-search
or with mamba:
mamba install tiledb-vector-search
It is possible to list all of the versions of tiledb-vector-search available on your platform with conda:
conda search tiledb-vector-search --channel tiledb
or with mamba:
mamba search tiledb-vector-search --channel tiledb
Alternatively, mamba repoquery may provide more information:
# Search all versions available on your platform:
mamba repoquery search tiledb-vector-search --channel tiledb
# List packages depending on `tiledb-vector-search`:
mamba repoquery whoneeds tiledb-vector-search --channel tiledb
# List dependencies of `tiledb-vector-search`:
mamba repoquery depends tiledb-vector-search --channel tiledb
If you would like to improve the tiledb-vector-search recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
tiledb channel, whereupon the built conda packages will be available for
everybody to install and use from the tiledb channel.
Note that all branches in the conda-forge/tiledb-vector-search-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.
In order to produce a uniquely identifiable distribution:
- If the version of a package is not being increased, please add or increase
the
build/number. - If the version of a package is being increased, please remember to return
the
build/numberback to 0.