Index Not Found - cause: queryport.indexNotFound (12016)

Hi @frasdav

On the N1QL side, you will need to re-prepare the statement. Once you drop the index, even if you recreate it, the prepared statement has an old plan so it will not pick up the new index. Im not sure if the SDK’s re-prepare. I think they do that for some errors and not all but I’m not sure. @ingenthr might be able to help.

Thanks
Isha

1 Like