Re: 1.3.1 cut
On 2015-06-18 11:27, Davide Giannella wrote: Good morning Team, next monday around 10AM I will be cutting 1.3.1 as by plan. We still have 137 unresolved issues. Please take a look at them and act accordingly. In case I will bulk move them to 1.3.2 if not resolved. In case you need more time because you'd like to have an issue fixed by this cut, give a shout. Cheers Davide I have unscheduled or rescheduled everything that I was assigned to, except: https://issues.apache.org/jira/browse/OAK-2987 This is fixed in 1.3.1 but not yet closed as I still need to backport it. Should I resolve it? Best regards, Julian
Re: 1.3.1 cut
On 18/06/2015 12:32, Julian Reschke wrote: I have unscheduled or rescheduled everything that I was assigned to, except: https://issues.apache.org/jira/browse/OAK-2987 This is fixed in 1.3.1 but not yet closed as I still need to backport it. Should I resolve it? thank Julian, if you need more time for the backport it's not a problem. Let me know. Otherwise you can always resolve the issue, unschedule it from the stable branches and and file a separate issue for the actual backport. Let me know. If not resolved I will simply bump it to 1.3.2. Cheers Davide
[mongoNs] using bulk operation for backgroundupdate?
Hi, This might have been discussed before but just so I understand: The DocumentNodeStore.backgroundWrite goes through the heavy work of updating the lastRev for all pending changes and does so in a hierarchical-depth-first manner. Unfortunately, if the pending changes all come from separate commits (as does not sound so unlikely), the updates are sent in individual update calls to mongo (whenever the lastRev differs). Which, if there are many changes, results in many calls to mongo. What about replacing that mechanism using mongo's bulk functionality (eg initializeOrderedBulkOperation)? Is this for some reason not possible or already in the jira-queue (which ticket)? Cheers, Stefan -- http://api.mongodb.org/java/current/com/mongodb/DBCollection.html#initialize OrderedBulkOperation--
1.3.1 cut
Good morning Team, next monday around 10AM I will be cutting 1.3.1 as by plan. We still have 137 unresolved issues. Please take a look at them and act accordingly. In case I will bulk move them to 1.3.2 if not resolved. In case you need more time because you'd like to have an issue fixed by this cut, give a shout. Cheers Davide
