SVN Property Value Size Limit
In our subversion repositories we have merged many many times. Now we have very large svn:mergeinfo property values (>8k). The problem is now, that if we make a svn checkout, the property values will be truncated in the working copy by approximately 8k. The svn propget command at the working copy folder returns a truncated value. This occurs only for working copies there are created with the http protocol over the svn apache. With the file protocol the property values are complete. My question: Is this a known behavior? Is this limited by a setting in the Apache/WebDAV/SVN configuration? regards, Matthias
RE: SVN Property Value Size Limit
yes, this returns the full correct value. The svn checkout via http makes the problem, tested with server 1.6.9 and client 1.6.x and 1.8.0. regards Matthias -Original Message- From: Philip Martin [mailto:philip.mar...@wandisco.com] Sent: Donnerstag, 27. Juni 2013 12:00 To: Matthias Legeler Cc: 'users@subversion.apache.org' Subject: Re: SVN Property Value Size Limit Matthias Legeler writes: > In our subversion repositories we have merged many many times. > Now we have very large svn:mergeinfo property values (>8k). > The problem is now, that if we make a svn checkout, the property values will > be truncated in the working copy by approximately 8k. > The svn propget command at the working copy folder returns a truncated value. > This occurs only for working copies there are created with the http protocol > over the svn apache. > With the file protocol the property values are complete. > > My question: > Is this a known behavior? > Is this limited by a setting in the Apache/WebDAV/SVN configuration? No there is no limit. Run the propget on the http URL rather than the working copy: svn propget svn:mergeinfo URL Does that return the full value? -- Philip Martin | Subversion Committer WANdisco | Non-Stop Data www.wandisco.com
RE: SVN Property Value Size Limit
'svn propget --strict svn:mergeinfo ./ ' gets the first 7895 characters 'svn propget --strict svn:mergeinfo URL' gets all 7959 characters yes, 64 characters difference Matthias -Original Message- From: Daniel Shahaf [mailto:danie...@elego.de] Sent: Donnerstag, 27. Juni 2013 12:18 To: Matthias Legeler Cc: 'users@subversion.apache.org' Subject: Re: SVN Property Value Size Limit Matthias Legeler wrote on Thu, Jun 27, 2013 at 07:02:50 +: > In our subversion repositories we have merged many many times. > Now we have very large svn:mergeinfo property values (>8k). > The problem is now, that if we make a svn checkout, the property values will > be truncated in the working copy by approximately 8k. > The svn propget command at the working copy folder returns a truncated value. Where does the truncation happen? Do you get only the first 8KB of the property? Do you get everything except the last 8KB? What is the offset from the point of truncation to the start and to the (true) end of the property? (Is that offset a power of 2?) You can determine all that with 'svn propget --strict svn:mergeinfo ./' and 'svn propget --strict svn:mergeinfo URL'. Daniel > This occurs only for working copies there are created with the http protocol > over the svn apache. > With the file protocol the property values are complete. > > My question: > Is this a known behavior? > Is this limited by a setting in the Apache/WebDAV/SVN configuration? > > regards, > Matthias >
RE: SVN Property Value Size Limit
Checkout with neon: property value truncated Checkout with serf (svn co --config-option servers:global:http-library=serf URL): property value complete Matthias -Original Message- From: 'Daniel Shahaf' [mailto:danie...@elego.de] Sent: Freitag, 28. Juni 2013 02:35 To: Matthias Legeler Cc: users@subversion.apache.org Subject: Re: SVN Property Value Size Limit Matthias Legeler wrote on Thu, Jun 27, 2013 at 10:30:32 +: > 'svn propget --strict svn:mergeinfo ./ ' gets the first 7895 > characters 'svn propget --strict svn:mergeinfo URL' gets all 7959 > characters > > yes, 64 characters difference > Interesting, thanks. I guess the next step is to look at the response headers. (You can use neon-debug-mask if you use neon, or wireshark/tcpdump if you don't use SSL.) In particular, whether the response includes the whole property, and whether metadata (eg: Content-Length response header) matches the response. BTW: does it happen under both serf and neon? (check 'svn --version' to see which you have; use --config-option to switch the active library) Daniel > Matthias > > -Original Message- > From: Daniel Shahaf [mailto:danie...@elego.de] > Sent: Donnerstag, 27. Juni 2013 12:18 > To: Matthias Legeler > Cc: 'users@subversion.apache.org' > Subject: Re: SVN Property Value Size Limit > > Matthias Legeler wrote on Thu, Jun 27, 2013 at 07:02:50 +: > > In our subversion repositories we have merged many many times. > > Now we have very large svn:mergeinfo property values (>8k). > > The problem is now, that if we make a svn checkout, the property values > > will be truncated in the working copy by approximately 8k. > > The svn propget command at the working copy folder returns a truncated > > value. > > Where does the truncation happen? Do you get only the first 8KB of > the property? Do you get everything except the last 8KB? What is the > offset from the point of truncation to the start and to the (true) end > of the property? (Is that offset a power of 2?) > > You can determine all that with 'svn propget --strict svn:mergeinfo ./' > and 'svn propget --strict svn:mergeinfo URL'. > > Daniel > > > This occurs only for working copies there are created with the http > > protocol over the svn apache. > > With the file protocol the property values are complete. > > > > My question: > > Is this a known behavior? > > Is this limited by a setting in the Apache/WebDAV/SVN configuration? > > > > regards, > > Matthias > >
