CB-7.x-beta & N1QL/FTS error

SQL++
,
1

I have CouchBase-7.0-beta running and trying to do this query below with N1QL & Full text search. I’m getting this error.

QUERY

SELECT b.* FROM SEARCH_QUERY("myFTS",
                             {
  "explain": true,
  "fields": [
    "*"
  ],
  "highlight": {},
  "query": {
    "query": "texas"
  }
}) as b

OUTPUT

[
  {
    "code": 5010,
    "msg": "Error evaluating ExpressionScan. - cause: Issue with accessing node information for rest endpoint nodesExt - cause: nodesExt"
  }
]

I have this below already set.

Screen Shot 2021-05-20 at 9.23.20 AM
Screen Shot 2021-05-20 at 9.23.20 AM1324×898 75 KB

2

Try to use SEARCH() function. SEARCH_QUERY() never documented and will be deprecated.

3

I looked up docs and blogs below.

This link on SEARCH() : Search Functions | Couchbase Docs
This Blog on N1QL: Introducing Full-Text Search Capability via the Query Interface - DZone Database

I’m still not able to SEARCH … I have the: bucket name , picking _default collection , query string, FTS index name. This is very confusing.

Screen Shot 2021-05-21 at 4.15.17 PM
Screen Shot 2021-05-21 at 4.15.17 PM1950×348 67.8 KB

Screen Shot 2021-05-21 at 4.15.23 PM
Screen Shot 2021-05-21 at 4.15.23 PM1924×394 81.1 KB

4

query_context is is set bucket snake, scope _default, so, snake is consider as collection.

Option 1: Remove query_context (above screen shot top right corner ) list boxes.

Option 2: Use full path of default collection
SELECT * FROM snake._default._default AS s

5

Screen Shot 2021-05-21 at 4.59.09 PM
Screen Shot 2021-05-21 at 4.59.09 PM1960×264 34.8 KB

OUTPUT

Screen Shot 2021-05-21 at 4.59.16 PM
Screen Shot 2021-05-21 at 4.59.16 PM1930×544 69.4 KB

Looks like the query is not pathing to the Bucket correctly.

Here is the bucket info BELOW

Screen Shot 2021-05-21 at 5.01.43 PM
Screen Shot 2021-05-21 at 5.01.43 PM1286×718 23.3 KB

6

Did you use keyword analyzer. cc @abhinav
OR try this

SERACH(s, {"query": {
    "query": "texas"
  }}, {"index":"snakeFull"});
7

Worked … Looks like the FTS index snakeFull was hung at 11.5% completed for days so N1QL was not able to find the FTS index… Dropped the snakeFull index recreated to 100% …Works.

Screen Shot 2021-05-21 at 5.07.52 PM
Screen Shot 2021-05-21 at 5.07.52 PM1946×258 57.8 KB

1 Like
8

@vsr1 … Could have debugged it sooner if N1QL error said something about FTS index scan error(s).

9

If Index is not 100% built, it is not consider (i.e. as of index not exist) online/ready to use (because it result in wrong results). N1QL is query and can’t return wrong results, so it validate the index with query. If validation fails it will not use that index.
It will try to use GSI index or other indexes. As none of them present it gives the error saying index is not present.

1 Like