Finally I dropped N1QL and used Views instead. I have now a really much better performances (~15s to get everything).
I’m disappointed because I wanted to push for the use of N1QL in our project, but this is a failure…
Thank you for your help.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Indexes for n1QL queries using UNNEST and how to make it covered | 1 | 1291 | June 6, 2018 | |
| Covering index for nested array | 10 | 2222 | June 15, 2019 | |
| Covering array index not avoiding FETCH | 8 | 885 | December 15, 2022 | |
| Covering Indexes in JOIN query using UNNEST | 4 | 1252 | March 22, 2019 | |
| Covering array index with arbitrary predicates | 4 | 1898 | July 5, 2019 |