You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by "Jackson, Douglas" <do...@siemens.com> on 2010/05/11 17:38:36 UTC
Transaction table cleanup
Hi!
Is there someway that Ode can clean up the database tables after transactions are completed?
We are seeing several hundred MB of data created in the tables per hour with Ode 2 beta 2.
There appears to be no attempt to remove the entries.
Is there some sort of configuration switch we are missing?
Is there something that a third party could use to remove the older entries or some sort of SQL statement?
We were using OpenJPA but more recently have switched to Hibernate as it is more reliable.
With OpenJPA transactions were getting lost.
-Doug.
Re: Transaction table cleanup
Posted by David Carver <dc...@intalio.com>.
This could be one of those things that is not working correctly in the beta.
Dave
On 05/11/2010 10:06 AM, Jackson, Douglas wrote:
> Hi!
> Thanks.
> We currently have<cleanup on="always" /> in our deploy.xml files. If I read that web page correctly it says that should remove the data, but that does not reflect our experience. Is it possible that was not present in Ode 2 beta 2? I don't know if Ode 2 beta 2 is considered a later release than Ode 1.3.
> -Doug
>
> -----Original Message-----
> From: antoine.toulme@gmail.com [mailto:antoine.toulme@gmail.com] On Behalf Of Antoine Toulme
> Sent: Tuesday, May 11, 2010 11:32 AM
> To: user@ode.apache.org
> Subject: Re: Transaction table cleanup
>
> This is what you want:
> http://ode.apache.org/instance-data-cleanup.html
>
> On Tue, May 11, 2010 at 08:38, Jackson, Douglas<
> douglas.s.jackson@siemens.com> wrote:
>
>
>> Hi!
>> Is there someway that Ode can clean up the database tables after
>> transactions are completed?
>> We are seeing several hundred MB of data created in the tables per hour
>> with Ode 2 beta 2.
>> There appears to be no attempt to remove the entries.
>> Is there some sort of configuration switch we are missing?
>> Is there something that a third party could use to remove the older entries
>> or some sort of SQL statement?
>> We were using OpenJPA but more recently have switched to Hibernate as it is
>> more reliable.
>> With OpenJPA transactions were getting lost.
>> -Doug.
>>
>>
>>
>
RE: Transaction table cleanup
Posted by "Jackson, Douglas" <do...@siemens.com>.
Hi!
Thanks.
We currently have <cleanup on="always" /> in our deploy.xml files. If I read that web page correctly it says that should remove the data, but that does not reflect our experience. Is it possible that was not present in Ode 2 beta 2? I don't know if Ode 2 beta 2 is considered a later release than Ode 1.3.
-Doug
-----Original Message-----
From: antoine.toulme@gmail.com [mailto:antoine.toulme@gmail.com] On Behalf Of Antoine Toulme
Sent: Tuesday, May 11, 2010 11:32 AM
To: user@ode.apache.org
Subject: Re: Transaction table cleanup
This is what you want:
http://ode.apache.org/instance-data-cleanup.html
On Tue, May 11, 2010 at 08:38, Jackson, Douglas <
douglas.s.jackson@siemens.com> wrote:
> Hi!
> Is there someway that Ode can clean up the database tables after
> transactions are completed?
> We are seeing several hundred MB of data created in the tables per hour
> with Ode 2 beta 2.
> There appears to be no attempt to remove the entries.
> Is there some sort of configuration switch we are missing?
> Is there something that a third party could use to remove the older entries
> or some sort of SQL statement?
> We were using OpenJPA but more recently have switched to Hibernate as it is
> more reliable.
> With OpenJPA transactions were getting lost.
> -Doug.
>
>
Re: Transaction table cleanup
Posted by Antoine Toulme <an...@toulme.name>.
This is what you want:
http://ode.apache.org/instance-data-cleanup.html
On Tue, May 11, 2010 at 08:38, Jackson, Douglas <
douglas.s.jackson@siemens.com> wrote:
> Hi!
> Is there someway that Ode can clean up the database tables after
> transactions are completed?
> We are seeing several hundred MB of data created in the tables per hour
> with Ode 2 beta 2.
> There appears to be no attempt to remove the entries.
> Is there some sort of configuration switch we are missing?
> Is there something that a third party could use to remove the older entries
> or some sort of SQL statement?
> We were using OpenJPA but more recently have switched to Hibernate as it is
> more reliable.
> With OpenJPA transactions were getting lost.
> -Doug.
>
>