Open xiaofan-luan opened 4 months ago
why not consider read before write to ensure primary key or vector is unique?
why not consider read before write to ensure primary key or vector is unique?
That is exactaly we are trying to deliver. The overgoal is to make retrieve on PK and retrieve on vector fast. We already have a PK index. BF is probably gonna to improve to prune the candidate segment
why not consider read before write to ensure primary key or vector is unique?
That is exactaly we are trying to deliver. The overgoal is to make retrieve on PK and retrieve on vector fast. We already have a PK index. BF is probably gonna to improve to prune the candidate segment
when it will be done, and what function we can call to drop the duplicate content?
/assign @czs007
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
When user insert, duplicated primary key or bloom filter need to be returned error or idempotent.
This means:
Describe the solution you'd like.
No response
Describe an alternate solution.
No response
Anything else? (Additional Context)
No response