oceanbase / oceanbase/pyseekdb
[Feature]: supports add or delete index
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 62
- Forks
- 35
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 2
Description
Describe your use case
Sometimes, we don't need fulltext index, but we should pay for it. So it's better to support not creating the fulltext index in create_collection interface.
One more thing, we can also allow developer add a fulltext index when they need.
We can do this when seekdb supports metadata index, because it's more complex than vector index and fulltext index.
Describe the solution you'd like
Refer to Chromadb schema to get more ideas.
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Python SDK's create_collection interface and review the linked Chroma schema documentation for how index configuration is exposed. Check whether seekdb supports the required metadata-index operations; completion should define how fulltext indexes are omitted initially and added or deleted later.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100