[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Revprop caching plan

From: Stefan Fuhrmann <stefan.fuhrmann_at_wandisco.com>
Date: Fri, 22 Aug 2014 13:31:08 +0200

On Fri, Aug 22, 2014 at 12:57 PM, Stefan Sperling <stsp_at_elego.de> wrote:

> On Fri, Aug 22, 2014 at 12:50:40PM +0200, Stefan Fuhrmann wrote:
> > Remaining restrictions:
> >
> > * All processes modifying revprops must use 1.9 or later libraries
> > or revprop caching cannot be used.
> Does this mean that using file:// with 'svn' < 1.9, or using svnadmin
> or svnlook < 1.9, won't be allowed while a server is running 1.9 with
> revprop caching enabled? Ie. effectively only 1.9 binaries are allowed?

Just like any other r/o access, svnlook will not be affected. 'svnadmin
propset' and 'svn propset file://' (with old binaries) will leave the
caching server processes with stale revprop caches. Revprop change
atomicy through those servers will still be guaranteed.

> If so, did we ever impose a requirement like this?

I don't know. But we did have feature compatibility requirements
like the merge tracking requiring 1.5 servers and cooperating
clients. Not exactly the same thing but saying "enable this feature
only if" would not be out of the ordinary.

And what will happen if people try this? Will they get an error?

People will get an error if one of the currently released 1.8 server
with revprop caching enabled or svnadmin change a revprop. In
that case, a 1.9 process using revprop caching will error out upon
revprop access.

Local modifications via non-caching pre-1.9 applications may
remain invisible to revprop caching 1.9 applications until either
a 1.9 application performs a (any) revprop change or the respective
process respawns.

-- Stefan^2.
Received on 2014-08-22 13:31:36 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.