Hi Jukka,
news about 1.3.2 version release date?
Thanks a lot indeed.
Andrea -
--
View this message in context:
http://www.nabble.com/Apache-Jackrabbit-1.3.2-release-plan-tf4489927.html#a12896041
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
Bien,
thanks again for your work.
Could I expect to have this patch included in an interim release like JR
1.3.2?
BR,
Andrea -
Marcel Reutegger wrote:
>
> Andrea K. wrote:
>> Do you think it is a safe patch to use in a production environment?
>
> yes, I think it is safe
Hi,
some reindexing on a test cluster say that the patch seems to work
correctly.
I can't see any error, but I didn't tested it so deeply, just patched the
code and
reindexed whole repository on servers and a test client. Anyway, apparently
no double records.
First patch proposed worked also for
Hi Marcel,
I'm just trying your proposed patch on a cluster.
If you want I can send you the resulting JR debug log and personal
impressions.
Thanks.
Andrea -
Marcel Reutegger wrote:
>
> Andrea K. wrote:
>> Hi all,
>> i'm testing the "2 line
Hi all,
what do you think about patch proposed by Marcel Reutegger?
Please report your comment. I'll test the patch asap.
Extract:
"Here's an alternative patch, which handles the possible duplicates earlier
in the index process, where it is also possible to detect an external
update. This avoids
Does anyone is interested to collaborate in solving this bug?
To use cluster in a production environment is very important to solve that,
'cause duplicated nodes aren't a good behaviour.
Any suggestion or help is very pleased.
Thanks in advance to all.
--
View this message in context:
http://
Hi all,
i'm testing the "2 line patch" as suggested in
(https://issues.apache.org/jira/browse/JCR-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel).
As I can see, no duplicated nodes exists with cluster configuration.
What do you think aboout the patch proposed? Should i
