Return-Path: X-Original-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A6F7710D4C for ; Mon, 20 Jan 2014 13:00:32 +0000 (UTC) Received: (qmail 48368 invoked by uid 500); 20 Jan 2014 13:00:30 -0000 Delivered-To: apmail-jackrabbit-oak-dev-archive@jackrabbit.apache.org Received: (qmail 47747 invoked by uid 500); 20 Jan 2014 13:00:24 -0000 Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-dev@jackrabbit.apache.org Received: (qmail 47733 invoked by uid 99); 20 Jan 2014 13:00:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jan 2014 13:00:21 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: unknown (athena.apache.org: error in processing during lookup of mueller@adobe.com) Received: from [207.46.163.238] (HELO na01-by2-obe.outbound.protection.outlook.com) (207.46.163.238) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jan 2014 13:00:16 +0000 Received: from BLUPR02MB342.namprd02.prod.outlook.com (10.141.77.149) by BLUPR02MB344.namprd02.prod.outlook.com (10.141.77.156) with Microsoft SMTP Server (TLS) id 15.0.851.15; Mon, 20 Jan 2014 12:59:54 +0000 Received: from BLUPR02MB342.namprd02.prod.outlook.com ([10.141.77.149]) by BLUPR02MB342.namprd02.prod.outlook.com ([10.141.77.149]) with mapi id 15.00.0851.011; Mon, 20 Jan 2014 12:59:54 +0000 From: Thomas Mueller To: "oak-dev@jackrabbit.apache.org" Subject: Re: AW: writing a new DocumentStore implementation Thread-Topic: AW: writing a new DocumentStore implementation Thread-Index: AQHPFd+D1JJPJOa7tUmCslPc3hl2jg== Date: Mon, 20 Jan 2014 12:59:54 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-originating-ip: [192.147.117.11] x-forefront-prvs: 00979FCB3A x-forefront-antispam-report: SFV:NSPM;SFS:(10019001)(189002)(199002)(24454002)(51704005)(479174003)(83506001)(81686001)(81816001)(74876001)(74706001)(19580395003)(83322001)(19580405001)(85852003)(83072002)(63696002)(80976001)(90146001)(56816005)(85306002)(80022001)(87266001)(87936001)(2656002)(65816001)(66066001)(76786001)(76796001)(47446002)(74502001)(31966008)(74662001)(36756003)(74366001)(76176001)(92566001)(92726001)(93136001)(93516002)(86362001)(50986001)(47976001)(47736001)(49866001)(4396001)(59766001)(77982001)(76482001)(54356001)(69226001)(54316002)(79102001)(51856001)(53806001)(81342001)(81542001)(46102001)(56776001);DIR:OUT;SFP:1102;SCL:1;SRVR:BLUPR02MB344;H:BLUPR02MB342.namprd02.prod.outlook.com;CLIP:192.147.117.11;FPR:;RD:InfoNoRecords;MX:1;A:1;LANG:en; Content-Type: text/plain; charset="iso-8859-1" Content-ID: <806115F4F0570C4F8E43F57D39323293@namprd02.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: adobe.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I think it should be relatively easy to extend the Segment storage to store to a read from a database. However, I'm not sur if that's currently planned.=20 The philosophy of the Segment storage is quite different from the Mongo storage (which should probably be renamed to Document storage): the Segment storage combinies many nodes into a segment and stores larger blocks, while the Mongo storage keeps each node separately. If you have multiple cluster nodes, the behavior of the two is quite different: the Mongo storage detects conflicts very early, but the Segment storage doesn't. So, in my view, the Segment storage is ideal for standalone repositories (where you have one process accessing the repository), and for clusters where the network latency between cluster nodes is high. But currently not so much for clusters where the latency between cluster nodes is low, because conflicts are not immediately detected and changes are not guaranteed to be visible within fixed time bounds. Regards, Thomas On 20/01/14 11:06, "K=D6LL Claus" wrote: >Hi Thomas, > >Sounds good to me !! > >One question based on that topic. >As jukka described with the big-picture the BlobStore we are talking is >only used with >mongo-mk as I can see, but what's about the segment-mk.. is it planned to >have a SQL based=20 >Segment Store ? > >greets >claus