-
-
Notifications
You must be signed in to change notification settings - Fork 179
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] collection config not always applied as expected #5099
Comments
On both tested systems the results were:
|
That is expected behaviour and is by design. |
What's the idea behind this? |
I would still expect that reindexing would then apply the new index configuration. |
In my case it makes sense to do this: I did manage to find a workaround though by using It was just unexpected behaviour. the fact that it didn't let me reindex the |
In update 2 I can prove that storing an XConf will immediately trigger reindexing of the entire collection. |
From the feedback I gathered today: Whenever a collection configuration changes, wether by storing copying or moving the configuration to a configuration collection, both of following must be true:
Both statements above are not satisfied in exist-db 6.2.0 up until 7.0.0-SNAPSHOT |
Describe the bug
From the feedback I gathered from long-standing core developer colleagues:
The first statement is not satisfied - tested in exist-db versions 6.2.0 and 7.0.0-SNAPSHOT.
NOTE: I have not yet tested the second statement.
Expected behavior
As an application developer, I expect that indexes in a collection configuration files are applied in the same way regardless of the way those changes are made.
To Reproduce
initial testsuite
first attempt at a testsuite that would highlight both observed inconsistencies left in just for completeness--- UPDATE 1: test copied xconf ---
The following testsuite proves, that the indexes defined in a collection configuration resource copied to a configuration collection cannot be applied to existing data.
Better isolation of tests operating on a copied xconf resource. They all fail.
--- UPDATE 2: immediate application ---
The test suite below proves that when a xconf resource is stored the indexes in it will be applied immediately.
Screenshots
If applicable, add screenshots to help explain your problem.
Context (please always complete the following information)
Build: eXist-7.0.0-SNAPSHOT (b032a42)
Java: 17.0.6 (Azul Systems, Inc.)
OS: Mac OS X 13.5.2 (aarch64)
Additional context
conf.xml
? noneThe text was updated successfully, but these errors were encountered: