Skip to content

VectorDB always embeds starting from id 1. So, exisiting data will throw error #3

@Raghvender1205

Description

@Raghvender1205

Upon running the example script in vectordb_client. If the vectordb server already has some data. It tries to embed the documents from id 1.

Now as some documents already exists at those ids. It throws this error

image

So, maybe introduce collections to VectorDB or add some checks for this edge case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions