Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of Erik.W.Mattheis@espn.com
 designates 192.234.2.145 as permitted sender)
From: "Mattheis, Erik W." <Erik.W.Mattheis@espn.com>
To: "users@jackrabbit.apache.org" <users@jackrabbit.apache.org>
Date: Wed, 7 Jan 2009 13:15:34 -0500
Subject: Re: Temp File Semantics
Thread-Topic: Temp File Semantics
Thread-Index: Aclw53mOQeIi13EHSqWVq+m9a+3XKAADHUbc
Message-ID: <C58A5B77.30A5%erik.w.mattheis@espn.com>
In-Reply-To: <91f3b2650901070845i1e87ac34xda3a4d9517d9cd2d@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_C58A5B7730A5erikwmattheisespncom_"
MIME-Version: 1.0

--_000_C58A5B7730A5erikwmattheisespncom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> The temp file prefix dbRecord is used in the DbDataStore in the following
> cases:
>
> - When reading, if the DbDataStore property copyWhenReading is enabled. D=
id
> you do that? Do you need it? Those files should be deleted if the file is
> read fully.

We didn't have this property set in our configuration. Looks like the defau=
lt is true. I set it to false, and everything looks good! In our scenario t=
he file comes from Jackrabbit and goes immediately to the client via HTTP, =
so we can stream directly without copying to disk.

> - When adding a record, if the database does not support adding streams o=
f
> unknown size (currently only the H2 database supports that). Those files =
are
> deleted after adding.

This shouldn't be a problem since the volume of uploaded media is quite low=
.

Thanks for your help!

--
Erik

--_000_C58A5B7730A5erikwmattheisespncom_--