From dev-return-27655-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Fri Mar 12 10:30:50 2010 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 30259 invoked from network); 12 Mar 2010 10:30:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 Mar 2010 10:30:50 -0000 Received: (qmail 39841 invoked by uid 500); 12 Mar 2010 10:30:13 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 39718 invoked by uid 500); 12 Mar 2010 10:30:13 -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 39711 invoked by uid 99); 12 Mar 2010 10:30:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Mar 2010 10:30:12 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tmueller@day.com designates 207.126.148.87 as permitted sender) Received: from [207.126.148.87] (HELO eu3sys201aog101.obsmtp.com) (207.126.148.87) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 12 Mar 2010 10:30:04 +0000 Received: from source ([74.125.82.52]) by eu3sys201aob101.postini.com ([207.126.154.11]) with SMTP ID DSNKS5oXlzJOmEZbuFba57gD4OVU4iILd6vl@postini.com; Fri, 12 Mar 2010 10:29:43 UTC Received: by wwb22 with SMTP id 22so625906wwb.39 for ; Fri, 12 Mar 2010 02:29:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.88.16 with SMTP id z16mr583801wee.126.1268389783103; Fri, 12 Mar 2010 02:29:43 -0800 (PST) In-Reply-To: <4B9A108B.4060109@gmail.com> References: <91f3b2651003120122k3ef335b6x1e8d60505b49c16@mail.gmail.com> <4B9A108B.4060109@gmail.com> Date: Fri, 12 Mar 2010 11:29:43 +0100 Message-ID: <91f3b2651003120229j702fa413ke0511bb1b5c2a1a3@mail.gmail.com> Subject: Re: [jr3] Store journal as nodes From: =?ISO-8859-1?Q?Thomas_M=FCller?= To: dev@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, > (except logging Yes, I think SLF4J is fine > and configuration, probably Some information need to be available when the repository is constructed, or at the latest when logging in: What storage backend to use, and how to connect to the storage backend. The rest of the configuration (fulltext index configuration for example, workspace names, security, data store configuration, cluster configuration, node type registry) should be in the repository (as system nodes) in the normal case. This is to simplify the system and to make configuration changes transactional. There may be a ways to override that (for example when constructing the repository object), but that should be the exception. I think it doesn't make sense to keep the xml configuration files. > What do you mean by "'normal' storage mechanism" ? I mean the data should be stored in the same place as the node data. Unless we find it is a performance problem, I would try to store the events as "node bundles" of some kind (possibly multiple events plus regular nodes in the same bundle). For the "micro kernel" it could look exactly like a normal node. > Is it nodes and properties, in which case I fear further performance issues in this area. If it does turn out to be a performance problem, we will change it of course. Regards, Thomas