Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5BC349FFF for ; Sat, 9 Jun 2012 01:51:12 +0000 (UTC) Received: (qmail 79466 invoked by uid 500); 9 Jun 2012 01:51:12 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 79392 invoked by uid 500); 9 Jun 2012 01:51:12 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 79383 invoked by uid 99); 9 Jun 2012 01:51:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jun 2012 01:51:12 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 74.125.149.147 is neither permitted nor denied by domain of hlin@consumer.org) Received: from [74.125.149.147] (HELO na3sys009aog122.obsmtp.com) (74.125.149.147) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jun 2012 01:51:05 +0000 Received: from mail-ob0-f172.google.com ([209.85.214.172]) (using TLSv1) by na3sys009aob122.postini.com ([74.125.148.12]) with SMTP ID DSNKT9Kr9Gt7C1B1J7lJCxMwgk1bP/BmZNBv@postini.com; Fri, 08 Jun 2012 18:50:45 PDT Received: by obbeh20 with SMTP id eh20so4629201obb.17 for ; Fri, 08 Jun 2012 18:50:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=G6C2bZ5YrQASnBex5d/4PABp0lquWgs9tSC+j0niFdo=; b=SV2KfyjQ24guueyT8RjKGLF1guDcOWOWL/EgCX4Qy286HAJOVyuP2dzUhCjkd/ns7A PRpNoIyPCef4EM/++zp787MuvXlqu7x5SXOjicCy+pfPS0lpczL7UFE36IlEWl9IjRg/ 5r158LToyODyW6Z2U3oDPoH+F82BqL1VQeV6EqZfMvtwVB0dRjlmS7W/DAxqhVNpucO3 y7h35z6gy/fHhwuSRYRNnFRKrrYQKEJ+VFmHm/Fx8ELA9u7plMVFrUSrxIFsBb9TYUjT KB7MgfsfIw03IbKw80etC7YCrPp25IeZJAqL8KifC32gIEHfIjvu4Kq29w/ssdmApNkq Gf1A== MIME-Version: 1.0 Received: by 10.50.157.194 with SMTP id wo2mr3501222igb.72.1339206643788; Fri, 08 Jun 2012 18:50:43 -0700 (PDT) Received: by 10.231.8.71 with HTTP; Fri, 8 Jun 2012 18:50:43 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 Jun 2012 21:50:43 -0400 Message-ID: Subject: Re: Mongodb bundle persistence manager From: Hui Lin To: dev@jackrabbit.apache.org Content-Type: multipart/alternative; boundary=e89a8f3b9e1f48aa1e04c2005887 X-Gm-Message-State: ALoCoQk1eT7RbdrGshj0SMPRRkJ6tGXHsBQZcs2tLi8JW/r+r/eItHHc4xo7o6sMIq3Hb/w0mIK1 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f3b9e1f48aa1e04c2005887 Content-Type: text/plain; charset=ISO-8859-1 i can certainly make a patch for you to test if you can give me some lead how to do it. i never involved with open source development before. thanks - Steven On Fri, Jun 8, 2012 at 8:59 AM, Jukka Zitting wrote: > Hi, > > On Thu, Jun 7, 2012 at 11:45 PM, Hui Lin wrote: > > anybody get a change to test the code? it would be something nice to > have in > > additional to the persistence managers out there already. > > Can you test the code against plain Jackrabbit instead of CRX/CQ? > > Also, it would be easier for us to help if you had a simple test case > that illustrates the problem. Having the MongoDB PM code you included > earlier and the test case as a patch that I can apply against > Jackrabbit trunk would be ideal. > > Note that there's been other efforts to implement the Jackrabbit PM > interface based on NoSQL databases, but such efforts commonly > encounter the issue that Jackrabbit 2.x expects the operation of > saving transient changes to be atomic. Do you have a way to ensure > that with MongoDB? > > BR, > > Jukka Zitting > ***** This e-mail message is intended only for the designated recipient(s) named above. The information contained in this e-mail and any attachments may be confidential or legally privileged. If you are not the intended recipient, you may not review, retain, copy, redistribute or use this e-mail or any attachment for any purpose, or disclose all or any part of its contents. If you have received this e-mail in error, please immediately notify the sender by reply e-mail and permanently delete this e-mail and any attachments from your computer system. ***** --e89a8f3b9e1f48aa1e04c2005887 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable i can certainly make a patch for you to test if you can give me some lead h= ow to do it. i never involved with open source development before.

=
thanks
- Steven

On F= ri, Jun 8, 2012 at 8:59 AM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
Hi,

On Thu, Jun 7, 2012 at 11:45 PM, Hui Lin <
hlin@consumer.org> wrote:
> anybody get a change to test the code? it would be something nice to h= ave in
> additional to the persistence managers out there already.

Can you test the code against plain Jackrabbit instead of CRX/CQ?

Also, it would be easier for us to help if you had a simple test case
that illustrates the problem. Having the MongoDB PM code you included
earlier and the test case as a patch that I can apply against
Jackrabbit trunk would be ideal.

Note that there's been other efforts to implement the Jackrabbit PM
interface based on NoSQL databases, but such efforts commonly
encounter the issue that Jackrabbit 2.x expects the operation of
saving transient changes to be atomic. Do you have a way to ensure
that with MongoDB?

BR,

Jukka Zitting


*****
This e-mail message is intended only for the designated recipient(s) name=
d above. The information contained in this e-mail and any attachments may=
 be confidential or legally privileged. If you are not the intended recip=
ient, you may not review, retain, copy, redistribute or use this e-mail o=
r any attachment for any purpose, or disclose all or any part of its cont=
ents. If you have received this e-mail in error, please immediately notif=
y the sender by reply e-mail and permanently delete this e-mail and any a=
ttachments from your computer system.
*****
=0D
--e89a8f3b9e1f48aa1e04c2005887--