You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by hbetts <He...@greenskycredit.com> on 2013/09/23 18:16:03 UTC
ODE_EVENT table size
Right now our ODE_EVENT table is over 3 MILLION rows (no you're not reading
that wrong). How long should we keep events? Should we treat the ODE_EVENT
table like a log file and purge it regularly or must it be long lived?
Thanks,
Hendry
--
View this message in context: http://apache-ode.996305.n3.nabble.com/ODE-EVENT-table-size-tp16900.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: ODE_EVENT table size
Posted by Tammo van Lessen <tv...@gmail.com>.
Hi Hendry,
the event table is used for parts of the instance management API, so if you
use that API to inspect process instances, you may lose that functionality
if you delete all rows. Beyond that I don't see any impact. Could please
provide some more details about the upgrade issues you have between 1.2 and
1.3.x?
Thanks,
Tammo
On Tue, Sep 24, 2013 at 2:40 PM, hbetts <He...@greenskycredit.com>wrote:
> This only helps for v1.3 to which we have not upgraded and it does not deal
> with old data. I guess the question should be "will purging the ODE_EVENT"
> table have any negative impact on the rest of the system.
>
> Since an ERD of the ODE database does not show any foreign key constraints
> on the table, I am assuming that it would not.
>
> Hendry
>
>
>
> --
> View this message in context:
> http://apache-ode.996305.n3.nabble.com/ODE-EVENT-table-size-tp16900p16902.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
--
Tammo van Lessen - http://www.taval.de
Re: ODE_EVENT table size
Posted by Sathwik B P <sa...@gmail.com>.
Hi Hendry,
You can find out the process instances that have completed from
BPEL_INSTANCE and match the corresponding events in BPEL_EVENT
The joining column would be probably IID in BPEL_EVENT. Just verify the
joining column. You could then eliminate those events of completed process
instances.
regards,
sathwik
On Tue, Sep 24, 2013 at 6:10 PM, hbetts <He...@greenskycredit.com>wrote:
> This only helps for v1.3 to which we have not upgraded and it does not deal
> with old data. I guess the question should be "will purging the ODE_EVENT"
> table have any negative impact on the rest of the system.
>
> Since an ERD of the ODE database does not show any foreign key constraints
> on the table, I am assuming that it would not.
>
> Hendry
>
>
>
> --
> View this message in context:
> http://apache-ode.996305.n3.nabble.com/ODE-EVENT-table-size-tp16900p16902.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
Re: ODE_EVENT table size
Posted by hbetts <He...@greenskycredit.com>.
This only helps for v1.3 to which we have not upgraded and it does not deal
with old data. I guess the question should be "will purging the ODE_EVENT"
table have any negative impact on the rest of the system.
Since an ERD of the ODE database does not show any foreign key constraints
on the table, I am assuming that it would not.
Hendry
--
View this message in context: http://apache-ode.996305.n3.nabble.com/ODE-EVENT-table-size-tp16900p16902.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: ODE_EVENT table size
Posted by Sathwik B P <sa...@gmail.com>.
This should help you in cleaning up events,
http://ode.apache.org/instance-data-cleanup.html
On Mon, Sep 23, 2013 at 9:46 PM, hbetts <He...@greenskycredit.com>wrote:
> Right now our ODE_EVENT table is over 3 MILLION rows (no you're not reading
> that wrong). How long should we keep events? Should we treat the ODE_EVENT
> table like a log file and purge it regularly or must it be long lived?
>
> Thanks,
> Hendry
>
>
>
> --
> View this message in context:
> http://apache-ode.996305.n3.nabble.com/ODE-EVENT-table-size-tp16900.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>