Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [CDO] Compact Revision-History
[CDO] Compact Revision-History [message #998789] Thu, 10 January 2013 17:51 Go to next message
Per Sterner is currently offline Per SternerFriend
Messages: 91
Registered: October 2011
Member
We like to use the CDO OfflineClone and therefore we need branching and auditing. The problem is that our Database is growing quickly.

Is it possible to compact the revision-history in sync with multiple offlineclone nodes?

In 2008 there was a discussion about the topic http://www.eclipse.org/forums/index.php/m/426117/. But this was before there was a non-auditing mode. The ticket for this feature-idea still exists https://bugs.eclipse.org/bugs/show_bug.cgi?id=256490

Regards,

Per Sterner
Re: [CDO] Compact Revision-History [message #999013 is a reply to message #998789] Fri, 11 January 2013 06:36 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6682
Registered: July 2009
Senior Member
Am 10.01.2013 18:51, schrieb Per Sterner:
> We like to use the CDO OfflineClone and therefore we need branching and auditing. The problem is that our Database is
> growing quickly.
There have been thoughts about using a non-auditing master repository and it seems conceptually possible. Technically
it's probably non-trivial and a lot of work to develop.

Theoretically clones could drop the part of the history that covers the time before the last replication.

CDOWorkspaces, which also enable offline work, are internally based on a local, non-auditing repository and require at
least auditing mode in the remote (master) repository. The same conceptual thoughts about using non-auditing in the
master apply.

> Is it possible to compact the revision-history in sync with multiple offlineclone nodes?
The major challenge is that a master can not know if and when specific clones will come back to sync their history. But
I could imagine that we store some per-clone infos in the master to be able to calculate a point in time that the last
one all "known" clones have already incorporated into their replica.

In general CDO has no means to compact histories, neither manually nor automatically. In theory you could either send
some SQL queries to the DBStore or write your own IQueryHandler to do whatever you want on the server.

> In 2008 there was a discussion about the topic http://www.eclipse.org/forums/index.php/m/426117/. But this was before
> there was a non-auditing mode. The ticket for this feature-idea still exists
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=256490
I can imagine that compacting history is useful sometimes but there have been no contributions and noone has decided to
fund any development in this direction.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Re: [CDO] Compact Revision-History [message #1000736 is a reply to message #999013] Tue, 15 January 2013 10:59 Go to previous message
Per Sterner is currently offline Per SternerFriend
Messages: 91
Registered: October 2011
Member
Hello Eike,

thanks for your answer and comments!

Regards,

Per Sterner
Previous Topic:[CDO-Net4j]
Next Topic:Set the noNamespaceSchemaLocation for XMLResource
Goto Forum:
  


Current Time: Fri Apr 19 12:42:49 GMT 2024

Powered by FUDForum. Page generated in 0.01998 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top