need to support WHERE / Index.Cond()
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
An FTS Index that has type mappings is basically translatable, where each type mapping translates to another Index with a different WHERE or Index.Cond().
https://github.com/couchbase/n1fty/blob/7b74840ba11976e200eeecb98eb1c53081441876/index.go#L93
The idea, let's say I have an FTS index "myFTSIdx" on the beer-sample bucket that looks like...
type: beer
mapping of the beer fields
type: brewery
mapping of the brewery fields
default:
mapping of the fields that aren't "type" of beer nor brewery
So, that would get expressed as 3 different Indexes...
Index myFTSIdx-beer
Cond() => "type = 'beer'"
Index myFTSIdx-brewery
Cond() => "type = 'brewery'"
Index myFTSIdx-default
Cond() => "type != 'beer' AND type != 'brewery'"
Also, better double-check with Sitaram that this is the correct expression.
Contributor guide
No contributing guide indexed for this repository
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 index.go at the linked location to understand how an FTS index with type mappings is translated. Confirm the intended WHERE or Index.Cond() expressions with Sitaram, including the default mapping case. Done means each type mapping is represented by a corresponding Index with the correct condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100