4.6.0 - N1QL index [Covering index] is not returning all matching docs

[deepkaran.salooja]

@rakesh.madhavakurup, please refer to the below posts for details on the setting and how to calculate its value:

Encoded array key too long (> 30978). Skipped

I’m seeing an error in indexer.log that says the array that I’m indexing is too long, but there’s only 31 items (with a total char count of 1078). This is the array: "members": [ "IDaaS_ESTAB-392DEMO_PL-8936", "IDaaS_ESTAB-392DEMO_PL-8998", "IDaaS_ESTAB-392DEMO_PL-9007", "IDaaS_ESTAB-392DEMO_PL-9046", "IDaaS_ESTAB-392DEMO_PL-9103", "IDaaS_ESTAB-392DEMO_PL-9109", "IDaaS_ESTAB-392DEMO_PL-9124", "IDaaS_ESTAB-392DEMO_PL-9133", "IDaaS_ESTAB-392DEMO_PL-9151", "IDaaS_ESTAB-392DEMO…

Different result set when using the 'Use Index' hint

I had created an index as follow. CREATE INDEX namedindex ON namedbucket((kvp.token),(kvp.expiryepoch),((kvp.resources).resources),(distinct (array [((k.keys).base), ((k.keys).term), ((k.keys).source), ((k.keys).type)] for k in ((kvp.resources).resources) end))) With 1, I am able to retrieve the record as expected, while 2 gives me no record. I also note that 2 will return result IF the key size of that specific document is smaller (it might be due the maximal size of the index key) select …