Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] monex index values view might contain stale data #234

Open
line-o opened this issue Mar 17, 2023 · 2 comments
Open

[BUG] monex index values view might contain stale data #234

line-o opened this issue Mar 17, 2023 · 2 comments

Comments

@line-o
Copy link
Member

line-o commented Mar 17, 2023

Describe the bug

Under certain circumstances the function util:index-keys#5 can return stale data.

eXist-db/exist#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

  • create test collection with a range index
  • insert 100 nodes each with a different key wich is then added to the index
  • check monex that 100 different keys with term frequency 1 is shown for that index
  • update insert into nodes with the same keys again to the same document
  • check monex to see that the term frequency stays 1
  • change the number of results per page to 10
  • now the correct term frequencies are shown
  • change back to 100 results per page
  • term frequencies are 1 again

Context (please always complete the following information):

  • Build: eXist-6.0.1
  • Java: 11.0.15 (Debian)
  • OS: Linux 5.10.104-linuxkit (aarch64)
  • App Version: 3.0.4

The same issue is also on 7.0.0-SNAPSHOT with monex 4.0.0 on macOSX and Java 17

Additional context

  • How is eXist-db installed? docker
  • Any custom changes in e.g. conf.xml? none
@joewiz
Copy link
Member

joewiz commented Mar 17, 2023

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?

@line-o
Copy link
Member Author

line-o commented Mar 18, 2023

I did open the issue here to

  1. Make users aware
  2. Inform how to verify it is this issue
  3. Link it to the root cause
  4. And not forget about it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants