need to support WHERE / Index.Cond()

[steveyen]

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().

n1fty/index.go

Line 93 in 7b74840

// WHERE clause stuff, not supported

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.

[steveyen]

Another related thought is that this probably means convertIndexDefs() needs to change where it converts each type-mapping into a separate index.

Looks like convertIndexDefs() is going to need some scrubbing and/or discussion.

[steveyen]

Oh, looks like this might be more of a concern for the future "use case 5".

To handle this for today / Mad Hatter, I think perhaps we just need to ensure some naming convention that allows for a "use case 5" future.