From users-return-19662-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Tue May 7 07:47:30 2013
Return-Path:
X-Original-To: apmail-jackrabbit-users-archive@minotaur.apache.org
Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by minotaur.apache.org (Postfix) with SMTP id 8F14F10C3E
for ; Tue, 7 May 2013 07:47:30 +0000 (UTC)
Received: (qmail 10337 invoked by uid 500); 7 May 2013 07:47:30 -0000
Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org
Received: (qmail 9006 invoked by uid 500); 7 May 2013 07:47:23 -0000
Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: users@jackrabbit.apache.org
Delivered-To: mailing list users@jackrabbit.apache.org
Received: (qmail 8946 invoked by uid 99); 7 May 2013 07:47:21 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 07:47:21 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com designates 209.85.214.179 as permitted sender)
Received: from [209.85.214.179] (HELO mail-ob0-f179.google.com) (209.85.214.179)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 07:47:15 +0000
Received: by mail-ob0-f179.google.com with SMTP id xn12so231282obc.10
for ; Tue, 07 May 2013 00:46:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=x-received:mime-version:in-reply-to:references:from:date:message-id
:subject:to:content-type;
bh=5nFpLB/6OBc+O2hBGFOvEzcZgoHTqYZvVGrOX3j27ag=;
b=YKRmSRZ1LtYoiuK4G2grdYheo9FA28PJiWIrLzyaxEk2YORfH1OjZ4aIeVANkGQXXl
73sIJNgOBQBwU+ClddiSgC2HEX6debtsrJGDZMrslB+03buuEOXN5J3D6O7JCkogFcRC
BGiMAwPEyUcpV4ftODS1Q9wEw8hR2jnR8eHiPaFa0mFhLtM9T+lVvR+R9DWl38/zf6Iu
oLZMy9Uy0ArGvLZL0zFScTpLNCXDxH9DWmfhl95NIMJapTLQiACUG3KYBf85Ub5FShbX
6tybBHzh7Xdc02AZH9wMGT4fJ7yOLGB1BnmyPdoIw1SGQJcw7vUfXvNZe8XnuAsqdtLM
xNvg==
X-Received: by 10.60.96.105 with SMTP id dr9mr239393oeb.59.1367912814496; Tue,
07 May 2013 00:46:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.61.44 with HTTP; Tue, 7 May 2013 00:46:34 -0700 (PDT)
In-Reply-To:
References:
From: Jukka Zitting
Date: Tue, 7 May 2013 09:46:34 +0200
Message-ID:
Subject: Re: I am confused about where my repository actually is...
To: Jackrabbit Users
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org
Hi,
On Mon, May 6, 2013 at 11:01 PM, Jay McHugh wrote:
> We have it configured to store the data in a mySQL database - but for some
> reason, there appears to be a file system repository as well.
>
> When using mySQL for the repository - shouldn't everything end up in the
> database?
>
> So, to try to figure out where my data really is - what property (or
> properties) should I look for in the configuration XML files?
There are many entries in the repository.xml file (and the
workspace.xml files) that control where various bits of repository
content get stored. See
http://jackrabbit.apache.org/jackrabbit-configuration.html for an
overall description of the available configuration options.
The most notable of these are the entries that
controls where the normal content (i.e. nodes and properties) of your
repository gets stored. There's one PM entry for the shared version
store under and another, used as the *default* for all
workspaces, under . The one under is actually
not the active configuration, only a template. See the relevant
workspace.xml files for the active configuration of each of your
workspaces. In a MySQL deployment you'd have these
configuration entries pointing to your MySQL
database using the MySqlPersistenceManager class. See
http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ for more
details.
In addition there are various and entries
that are used for configuring the storage locations of different bits
of repository metadata (registered namespaces, etc.) and the Lucene
search indexes. These are typically *not* stored in a database even if
the raw repository content is there.
BR,
Jukka Zitting