Adding/deleting an edge doesn't update the index of the object

[fredpook]

Use case:
A query with: hasobject=1234
shows all rsc's with keyword 1234
When adding a new rsc with keyword 1234 it won't show in the query until a complete re-index.

[ddeboer]

I thought this too for a moment, but actually it works perfectly fine: zotonic/zotonic#1698.

Where/when do you see this behaviour?

[fredpook]

Editors of Amsterdam Museum seen it happen several times.
Just now I solved 1 issue for them by calling the refresh API explicitly
https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-refresh.html

I didn't find code for refreshing in this module. Should we refresh after each operation?

[ddeboer]

No, we don’t need to. There can be a normal delay of ~1 sec between updating some document in Elasticsearch and its being available in the index.

That delay is normal behaviour, usually not an issue for our use-cases. The problem that some customers are seeing must be caused by some different cause. We should investigate why the normal behaviour doesn’t work here. Perhaps the Elasticsearch server is having performance issues, causing the PUTs to time out? We need to replicate the problem first to know for sure.

[fredpook]

"some different cause" in this module since they didn't experience the issues before ...

[ddeboer]

Or on the server.

[fredpook]

A solution for this kind of erratic "out of sync" behaviour could be to have the "simple" hassubject/hasobject queries handled by postgres like before.
These perform very fast in zotonic and don't need ES for improved fulltext search.
Just the combinations of text plus edge queries can be handled by ES

[fredpook]

And this zotonic/zotonic#1722 will help too