Open line-o opened 1 year ago
I can see why Monex would be affected by this, but the problem isn't fundamentally Monex's, is it? The problem is eXist - as described in the issue you linked to. Monex just conveys the data it receives from eXist via the built-in functions. Or is Monex responsible in some way here?
I did open the issue here to
Describe the bug
Under certain circumstances the function
util:index-keys#5
can return stale data.https://github.com/eXist-db/exist/issues/4805
Monex is also affected by this as this will show incorrect term frequencies in the index value view.
Changing the number of results per page shows the correct values but changing back to the original value for results per page will still the old values. Only reindexing the collection with this index will update all views to show correct term frequencies.
Expected behavior
The index values view to always show the current term frequencies.
To Reproduce
update insert into
nodes with the same keys again to the same documentContext (please always complete the following information):
The same issue is also on 7.0.0-SNAPSHOT with monex 4.0.0 on macOSX and Java 17
Additional context
conf.xml
? none