Knn.derived_source=true causes query not to return _routing

Plugins k-NN
1

Hi all,

I noticed that knn.derived_source=true causes search requests to return without _routing! Is that an expected behaviour?

More specifically it happens after creating a semantic field and populating it with content.

I also noticed that it causes delete_by_query API to fail giving version conflict errors.

Thanks

2

Hey @asfoorial this seems like a bug… Can you create an issue in GitHub · Where software is built and include the version and repro steps?

3

For the delete by query, I noticed on both enabled and disabled, I could get version conflict:

curl -X POST "http://localhost:9200/test-index-dis/_delete_by_query" -H 'Content-Type: application/json' -d'
{
  "query": {
    "ids": {
      "values": ["0"]
    }
  }
}'
{"took":3,"timed_out":false,"total":1,"deleted":0,"batches":1,"version_conflicts":1,"noops":0,"retries":{"bulk":0,"search":0},"throttled_millis":0,"requests_per_second":-1.0,"throttled_until_millis":0,"failures":[{"index":"test-index-dis","id":"0","cause":{"type":"version_conflict_engine_exception","reason":"[0]: version conflict, required seqNo [0], primary term [1]. but no document was found","index":"test-index-dis","shard":"0","index_uuid":"uFbanrlJQ4qPmHGnVtVjww"},"status":409}]}

Refresh solved that one.

Still not sure on _routing. If youre able to create GH issue with repro, thatd be helpful

Thanks
Jack

4

Unfortunately, refresh works only when the index has no active indexing operations. In my case, documents get indexed as soon as they are detected in a data source. So delete_by_query will throw errors when there documents not yet refreshed!

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.