No Match(...) Against(...) in N1QL?


#1

I notice that match and against aren’t in the reserved words. Any plans for full text search, or will we still be dependent on ElasticSearch for that?


#2

Per the Dev Guide, the list of reserved words is not (yet) definitive, and we reserve the right to reserve more :). Please don’t read anything into the absence of a reserved word.

As we look at the feature pipeline, we see that search is available via ElasticSearch, while other features (e.g. DML – UPDATE / DELETE / INSERT – statements via N1QL) are not yet available. So it’s likely that we will address the unavailable features.