You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Performance issue when finding changes by instanceId with ChildValueObject #1039
I use Javers (5.12.0) with MongoDB repository in a production environment for auditing one object with one child.
Currently the snapshots collection contains more than 1 millions documents and we meet performance issue when finding changes by instanceId with child value object :
As we can see the query do a filter on exact globalId_key ( very fast as there is an index for this property in Mongo DB ) but the second part with regex filter is very slow.
Have you already see this issue ?
Is there any solution to solve this ?
May be we could filter using globalID.ownerId property ?
I implemented a fix for this performance issue on a local branch. When I tried to push it, I received a permission denied. Miss I something ?
It is the first time I contribute to an open source project so I am not aware of all good practices.
Hi! Me and my team hit this problem too with a DocumentDB collection with around 4 million objects. I've tried to fix this with #1367@bartoszwalacik could you please take a look?
Activity
bartoszwalacik commentedon Dec 4, 2020
Hi, since you are close to the solution of this issue, please contribute a PR
gravity-57 commentedon Dec 8, 2020
Hi,
I implemented a fix for this performance issue on a local branch. When I tried to push it, I received a permission denied. Miss I something ?
It is the first time I contribute to an open source project so I am not aware of all good practices.
BR
bartoszwalacik commentedon Dec 8, 2020
Ok, so the standard flow on github looks like that :
you need to fork this repository and create a PR from your fork's branch to this master
for example #1021
vladimirmutafov commentedon Mar 11, 2024
Hi! Me and my team hit this problem too with a DocumentDB collection with around 4 million objects. I've tried to fix this with #1367 @bartoszwalacik could you please take a look?
https://github.com/javers/javers/issues/1039
bartoszwalacik commentedon Mar 14, 2024
Fixed in 7.4.1