Hi, As far as I know, this is a limitation of MySQL: http://bugs.mysql.com/bug.php?id=10859 http://forums.mysql.com/read.php?10,258333,260405#msg-260405
It looks like you can only fix part of this MySQL problem (the reading part, but not the writing part). That means up to now, you can not stream very large binaries from the MySQL client to the MySQL server; you can only stream very large binaries from the MySQL server to the MySQL client. I'm afraid there is not much we can do in Jackrabbit, except document this problem - I have updated the wiki at http://wiki.apache.org/jackrabbit/DataStore . Well, there would be one solution: creating a new data store that stores data in blocks (of let's say 1 MB), but that would be quite a lot of work. Regards, Thomas On Tue, May 12, 2009 at 11:03 AM, Torgeir Veimo <[email protected]> wrote: > 2009/5/12 daveg0 <[email protected]> > >> >> Hi, >> >> We are building a multi-media repository which will include some fairly >> large videos. We have tried storing the blobs internally in MySQL, but are >> running across issues (max_packet_size, connections failing randomly etc)., >> so we thought we'd try external blobs, but I can't seem to get it to work. >> > > Try using a file system data store, not a db data store; > > <DataStore class="org.apache.jackrabbit.core.data.FileDataStore"> > <param name="path" value="${rep.home}/repository/datastore"/> > <param name="minRecordLength" value="100"/> > </DataStore> > > -- > -Tor >
