done

Andy Seaborne <[email protected]> wrote on 21-11-2014 12:27:37:

> Please suggest improvements, and contribute new text.  It's always trick 

> to write documentation when you are on the "inside" of the 
> implementation :-)
> 
> (You can edit them online with Apache CMS and the project will receive a 

> patch for the website).
> 
> >
> > As long as I use Fuseki to update , remove and insert data the index 
stays
> > in sync, thats all I needed.
> 
> Yes - that's the way to do it.  Lucene is runnig same_JVM so you can 
> only mess it up by updating directly while Fuseki is running.
> 
> It is possible to have more complex setups with Solr as the text index, 
> then update solr or query solr separately from Fuseki/TDB.  Solr is an 
> external service in this example.
> 
>    Andy
> 
> >
> > Bart
> >
> >> On 18/11/2014 16:21, "Bart van Leeuwen" <[email protected]>
> > wrote:
> >>
> >>> Hi,
> >>>
> >>> I've played around with Fuseki  1.1.1
> >>> I created a TDB store which I filled with data through the Fuseki
> > control
> >>> panel
> >>>
> >>> I followed the instruction for full text queries at:
> >>> http://jena.apache.org/documentation/query/text-query.html
> >>>
> >>> Everything is up and running and works like expected.
> >>>
> >>> Now the data in the TDB store will be updated now and then is it
> > possible
> >>> to run the index updater while fuseki is still up and running ?
> >>> or do I need to bring fuseki down during that process ? ( I know TDB 
is
> >>> not thread safe but afaik the indexer is not touching TDB for 
writing )
> >>>
> >>> What would be the best practice for online index updating ?
> >>>
> >>> Met Vriendelijke Groet / With Kind Regards
> >>> Bart van Leeuwen
> >>>
> >>> ##############################################################
> >>> # twitter: @semanticfire
> >>> # netage.nl
> >>> # http://netage.nl
> >>> # Enschedepad 76
> >>> # 1324 GJ Almere
> >>> # The Netherlands
> >>> # tel. +31(0)36-5347479
> >>> ##############################################################
> >>
> >>
> >>
> >>
> >
> 

Reply via email to