Venkat Krishnamurthy wrote:
> Tao
> 
> The latter. This assemblerspec just tells it where to find an already
> created index.
> 
> Keeping it in sync with tdb is your responsibility at this stage. You have
> to figure out a way to trigger re-indexing or incremental indexing on
> updates/bulk-load.

Hi Venkat,
yes and not, it depends on where the updates come from.

If your updates are coming from SPARQL Update requests, then you are right: the
Lucene index is not kept in sync.

However, if updates are via Jena Model APIs, LARQ 1.0.0  do add/remove  data
from the Lucene index.

I'd like to make life as easy as possible for users, but at the moment I did not
find a way to be notified as RDF statements are added/removed which works well
for all the possible 'update code paths'.

For more details on this, please, look at:
https://issues.apache.org/jira/browse/JENA-164
... and if there is anyone who wants to help me on this, you are welcome. :-)

I also want to add support for Solr as well as Elastic Search (and refactor the
LARQ code to make it easy to plugin different indexes). An experimental
prototype for this (now old and not up-to-date) is here:
https://github.com/castagna/EARQ
If you have a look, let me know what you think.

Cheers,
Paolo

> 
> Venkat
> 
> 2012/4/25 Tao(陶信东) <taoxind...@myhexin.com>
> 
>> Hi Paolo,
>>
>> This is great! I've been waiting for it since several weeks ago.
>>
>> However, after I configured Fuseki for it by adding LARQ to my class path
>> and the following lines to the assembly file, pf:textMatch doesn't work
>> (the
>> usual sparql query works).
>>
>> <#dataset> rdf:type tdb:DatasetTDB ;
>>  tdb:location "/path/to/my/tdb/indexes/" ;
>>  ja:textIndex "/path/to/lucene/index/" ;
>>  .
>>
>> Is Fuseki supported by this LARQ release? Or should I build the lucene
>> index
>> by myself when Fuseki started?
>>
>> Thanks
>> Tao
>>
>> -----Original Message-----
>> From: Paolo Castagna [mailto:castagna.li...@googlemail.com]
>> Sent: Tuesday, April 24, 2012 5:43 AM
>> To: jena-users@incubator.apache.org
>> Subject: [ANN] Release of Apache Jena LARQ 1.0.0-incubating
>>
>> LARQ 1.0.0-incubating has been released, this is the first release of LARQ
>> as separate module and under the Apache License.
>>
>> LARQ is a combination of ARQ and Lucene aimed at providing developers with
>> the ability to perform free text searches within their SPARQL queries.
>>
>> Documentation for LARQ is available here:
>>
>>  - http://incubator.apache.org/jena/documentation/larq/
>>  - http://incubator.apache.org/jena/documentation/javadoc/larq/
>>
>>
>> == Mailing lists
>>
>> The user mailing list for Jena is  jena-users@incubator.apache.org Send
>> email to  jena-users-subscr...@incubator.apache.org  to subscribe.
>>
>> See also:
>> http://incubator.apache.org/jena/help_and_support/index.html
>>
>>
>> == About This Release
>>
>> The main new feature in this release is support for updating the Lucene
>> index as RDF statements are added/removed to the Jena Model via the Jena
>> APIs.
>> Moreover, LARQ now depends on Apache Lucene 3.5.0.
>>
>>
>> == Download
>>
>> Maven artifacts are here:
>> http://repo1.maven.org/maven2/org/apache/jena/jena-larq/1.0.0-incubating/
>>
>> Source release is here:
>>
>> http://www.apache.org/dyn/closer.cgi/incubator/jena/jena-larq-1.0.0-incubati
>> ng
>>
>>
>> == Status
>>
>> Apache Jena is an effort undergoing incubation at the Apache Software
>> Foundation (ASF), sponsored by the Apache Incubator PMC.
>>
>> Incubation is required of all newly accepted projects until a further
>> review
>> indicates that the infrastructure, communications, and decision making
>> process have stabilized in a manner consistent with other successful ASF
>> projects.
>>
>> While incubation status is not necessarily a reflection of the completeness
>> or stability of the code, it does indicate that the project has yet to be
>> fully endorsed by the ASF.
>>
>> For more information about the incubation status of the Jena project you
>> can
>> go to the following page:
>> http://incubator.apache.org/projects/jena.html
>>
>>
> 

Reply via email to