Hi Tarrant, The FST linking engine [1] requires an embedded SolrCore (as it heavily uses low level Lucene APIs). However note - FST linking is all in-memory. Only for looking up the labels and types of linked entities (as required to write fise:TextAnnotation) the FST engine needs to retrieve documents from the Lucene index. However for that it does use a cache. So if you set the size to the cache >= the number of documents in the index this engine operates all in-memory.
The SolrYard (as used by the Entityhub Linking Engine [2]) can be configured with an external Solr Server. Just configure the HTTP URL to the Core in the SolrCore field. * Solr Index/Core (org.apache.stanbol.entityhub.yard.solr.solrUri): This can be either the URL of a SolrServer, the absolute Path to an index/core an the local file system or just the core name to use the EmbeddedSolrServer internally managed by the SolrYard best Rupert [1] http://stanbol.apache.org/docs/trunk/components/enhancer/engines/lucenefstlinking [2] http://stanbol.apache.org/docs/trunk/components/enhancer/engines/entitylinking On Thu, Jul 16, 2015 at 6:54 AM, Tarrant Marshall <tarrant.marsh...@sbs.com.au> wrote: > Hi > > Does anyone have any insight on if it's possible to configure Stanbol to use > an external Apache Solr core? If so, how? > > Scenario is to use a preferred SolrCloud cluster that has replication for > high availability and a load balancer end point. > > Thanks > Tarrant > > > [Go Back to Where You Came From, 3 night television event 28-30 July, 8.30pm > on SBS.]<www.sbs.com.au/goback> -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen | REDLINK.CO .......................................................................... | http://redlink.co/
