Scott Morrison wrote: > Inevitably, moments after asking for help I've found things to try.
:-) > In webapps/WEB-INF/longwell.properties there is a section > =========================== > longwell.store.dir = WEB-INF/database > > longwell.store.type = memory > #longwell.store.type = native > > #longwell.store.type = biggles > #longwell.store.db.url = ... > #longwell.store.db.user = ... > #longwell.store.db.passwd = ... > =========================== > and I'm now happily using a native store, simply by changing which > line is commented out above! It seems loading data works just fine > with -r: the data persists from session to session. Yup, that's the goal. > Two questions: > 1) What are the consequences of turning off > "longwell.index.regenerate"? With this on, longwell takes longer and > longer to start as I add more data. But I assume it is essential. Is > there some way to incrementally add data and regenerate the indices? > Or am I just going to have to load all my data, turn regeneration back > on, and hope for the best? regeneration destroys the lucene index for every new data input and rebuilds it from scratch. This is a very time-consuming process and not really required as lucene is perfectly capable of doing this incrementally. It should be used only if your index gets corrupted or out of synch with the triple store (for any reason), so you are safe in leaving it turn off and enjoy the incremental performance. > 2) Is there are preferred method of cleaning out a native store? Or is > it safe to simply delete the WEB-INF/database directory? no special method, no, I normally just rm -rf the WEB-INF/database and longwell creates a new one next time is invoked. > 3) Is there any explanation somewhere of setting up longwell with a > remote database? I assume this is possible using Sesame's > HTTPRepository mechanism, but the "biggles" section of > longwell.properties is a bit terse for me :-) Biggles is an experiment of one of the grad students gravitating around our group, but it's currently idle so don't expect much from that. Andrew is working on a sesame connector for MySQL which would allow you to hook longwell up to a local or remote mysql database, but he's not done yet. > And thanks for giving me such a fun toy to play with! Please let us know the good the bad and the ugly as feedback from the field is very valuable to use (you know, when you stare at something for too long you get a little blind so we are not as good at improving it at this point). > Scott Morrison > > On 6/28/07, Scott Morrison <[EMAIL PROTECTED]> wrote: >> I've finally got my rdf data (extracted from the arxiv and citebase) >> into a shape where Longwell can do useful things with it. So far I've >> only been loading small subsets of data. >> >> I'd now like to load, if possible, the entire dataset, ideally in some >> way that restarting Longwell and/or the server doesn't require redoing >> everything! >> >> I know that Longwell uses Sesame2 underneath, and I understand the >> basics of Sesame -- I can load my data into a Sesame repository, for >> example. >> >> Can someone tell me how to get Longwell to use a native sesame store, >> and then how to get Longwell to load data into it? I assume I can't >> load the date into the native store myself, because Longwell is doing >> extra indexing of some sort. I remember something about a tmp/ >> directory being relevant here, but google is failing me now. >> >> Any advice much appreciated! >> >> Thanks, Scott Morrison >> > _______________________________________________ > General mailing list > [email protected] > http://simile.mit.edu/mailman/listinfo/general -- Stefano. _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
