Skip to content

Latest commit

 

History

History
240 lines (143 loc) · 10.2 KB

changelog.md

File metadata and controls

240 lines (143 loc) · 10.2 KB
Raw

v0.5.1

What's Changed

We add a new method Collection.filter to filter the vector records based on the metadata. This method returns a HashMap of the filtered vector records and their corresponding vector IDs. This implementation performs a linear search through the collection and thus might be slow for large datasets.

This implementation includes support for the following metadata to filter:

  • String: Stored value must include the filter string.
  • Float: Stored value must be equal to the filter float.
  • Integer: Stored value must be equal to the filter integer.
  • Object: Stored value must match all the key-value pairs in the filter object.

We currently don't support filtering based on the array type metadata because I am not sure of the best way to implement it. If you have any suggestions, please let me know.

Contributors

  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.5.0...v0.5.1

v0.5.0

What's Changed

  • BREAKING CHANGE: Although there is no change in the database API, the underlying storage format has been changed to save the collection data to dedicated files directly. The details of the new persistent system and how to migrate from v0.4.x to v0.5.0 can be found in this migration guide.

  • By adding the feature gen, you can now use the EmbeddingModel trait and OpenAI's embedding models to generate vectors or records from text without external dependencies. This feature is optional and can be enabled by adding the feature to the Cargo.toml file.

    [dependencies]
oasysdb = { version = "0.5.0", features = ["gen"] }

Contributors

  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.4.5...v0.5.0

v0.4.5

What's Changed

  • Add insert benchmark to measure the performance of inserting vectors into the collection. The benchmark can be run using the cargo bench command.
  • Fix the issue with large-size dirty IO buffers caused by the database operation. This issue is fixed by flushing the dirty IO buffers after the operation is completed. This operation can be done synchronously or asynchronously based on the user's preference since this operation might take some time to complete.

Contributors

  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.4.4...v0.4.5

v0.4.4

What's Changed

  • Maximize compatibility with the standard library error types to allow users to convert OasysDB errors to most commonly used error handling libraries such as anyhow, thiserror, etc.
  • Add conversion methods to convert metadata to JSON value by serde_json and vice versa. This allows users to store JSON format metadata easily.
  • Add normalized cosine distance metric to the collection search functionality. Read more about the normalized cosine distance metric here.
  • Fix the search distance calculation to use the correct distance metric and sort it accordingly based on the collection configuration.
  • Add vector ID utility methods to the VectorID struct to make it easier to work with the vector ID.

Additional Notes

  • Add a new benchmark to measure the true search AKA brute-force search performance of the collection. If possible, dealing with a small dataset, it is recommended to use the true search method for better accuracy. The benchmark can be run using the cargo bench command.
  • Improve the documentation to include more examples and explanations on how to use the library: Comprehensive Guide.

Contributors

  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.4.3...v0.4.4

v0.4.3

What's Changed

  • Add SIMD acceleration to calculate the distance between vectors. This improves the performance of inserting and searching vectors in the collection.
  • Improve OasysDB native error type implementation to include the type/kind of error that occurred in addition to the error message. For example, ErrorKind::CollectionError is used to represent errors that occur during collection operations.
  • Fix the Config.ml default value from 0.3 to 0.2885 which is the optimal value for the HNSW with M of 32. The optimal value formula for ml is 1/ln(M).

Contributors

  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.4.2...v0.4.3

v0.4.2

What's Changed

Due to an issue (#62) with the Python release of v0.4.1, this patch version is released to fix the build wheels for Python users. The issue is caused due to the new optional PyO3 feature for the v0.4.1 Rust crate release which exclude PyO3 dependencies from the build process. To solve this, the Python package build and deploy script now includes --features py argument.

For Rust users, this version doesn't offer any additional features or functionality compared to v0.4.1 release.

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.4.1...v0.4.2

v0.4.1

What's Changed

  • Added quality of life improvements to the VectorID type interoperability.
  • Improved the README.md file with additional data points on the database performance.
  • Changed to Collection.insert method to return the new VectorID after inserting a new vector record.
  • Pyo3 dependencies are now hidden behind the py feature. This allows users to build the library without the Python bindings if they don't need it, which is probably all of them.

Contributors

  • @dteare
  • @edwinkys
  • @noneback

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.4.0...v0.4.1

v0.4.0

What's Changed

  • CONDITIONAL BREAKING CHANGE: Add an option to configure distance for the vector collection via Config struct. The new field distance can be set using the Distance enum. This includes Euclidean, Cosine, and Dot distance metrics. The default distance metric is Euclidean. This change is backward compatible if you are creating a config using the Config::default() method. Otherwise, you need to update the config to include the distance metric.

    let config = Config {
    ...
    distance: Distance::Cosine,
};

  • With the new distance metric feature, now, you can set a relevancy threshold for the search results. This will filter out the results that are below or above the threshold depending on the distance metric used. This feature is disabled by default which is set to -1.0. To enable this feature, you can set the relevancy field in the Collection struct.

    ...
let mut collection = Collection::new(&config)?;
collection.relevancy = 3.0;

  • Add a new method Collection::insert_many to insert multiple vector records into the collection at once. This method is more optimized than using the Collection::insert method in a loop.

Contributors

  • @noneback
  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.3.0...v0.4.0

v0.3.0

This release introduces a BREAKING CHANGE to one of the method from the Database struct. The Database::create_collection method has been removed from the library due to redundancy. The Database::save_collection method can be used to create a new collection or update an existing one. This change is made to simplify the API and to make it more consistent with the other methods in the Database struct.

What's Changed

  • BREAKING CHANGE: Removed the Database::create_collection method from the library. To replace this, you can use the code snippet below:

    // Before: this creates a new empty collection.
db.create_collection("vectors", None, Some(records))?;

// After: create new or build a collection then save it.
// let collection = Collection::new(&config)?;
let collection = Collection::build(&config, &records)?;
db.save_collection("vectors", &collection)?;

  • Added the Collection::list method to list all the vector records in the collection.

  • Created a full Python binding for OasysDB which is available on PyPI. This allows you to use OasysDB directly from Python. The Python binding is available at https://pypi.org/project/oasysdb.

Contributors

  • @edwinkys
  • @Zelaren
  • @FebianFebian1

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.2.1...v0.3.0

v0.2.1

What's Changed

  • Metadata enum can now be accessed publicly using oasysdb::metadata::Metadata. This allows users to use match statements to extract the data from it.
  • Added a prelude module that re-exports the most commonly used types and traits. This makes it easier to use the library by importing the prelude module by use oasysdb::prelude::*.

Contributors

  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.2.0...v0.2.1

v0.2.0

What's Changed

  • For Collection struct, the generic parameter D has been replaced with Metadata enum which allows one collection to store different types of data as needed.
  • The Vector now uses Vec<f32> instead of [f32, N] which removes the N generic parameter from the Vector struct. Since there is a chance of using different vector dimensions in the same collection with this change, An additional functionality is added to the Collection to make sure that the vector dimension is uniform.
  • The M generic parameter in the Collection struct has been replaced with a constant of 32. This removes the flexibility to tweak the indexing configuration for this value. But for most use cases, this value should be sufficient.
  • Added multiple utility functions to structs such as Record, Vector, and Collection to make it easier to work with the data.

Contributors

  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/compare/v0.1.0...v0.2.0

v0.1.0

What's Changed

  • OasysDB release as an embedded vector database available directly via cargo add oasysdb command.
  • Using HNSW algorithm implementation for the collection indexing along with Euclidean distance metrics.
  • Incremental updates on the vector collections allowing inserts, deletes, and modifications without rebuilding the index.
  • Add a benchmark on the collection search functionality using SIFT dataset that can be run using cargo bench command.

Contributors

  • @edwinkys

Full Changelog

https://github.com/oasysai/oasysdb/commits/v0.1.0