Le 11/10/11 11:06, Paolo Castagna a écrit :

Jérôme wrote:
Le 10/10/11 18:01, Paolo Castagna a écrit :
Hi Jérôme,
first of all, thanks for helping out testing the LARQ
0.2.2-incubating-SNAPSHOT
and for your patience. ;-)
You're welcome! LARQ is usefull for my current project.
This hopefully will help to spot problems early one and reduce
problems once ARQ
and LARQ are released within Apache.

Jérôme wrote:
Hi,

i've recently made an svn up on my LARQ directory.

Now, my LARQ queries return 0 solution (they returned before).

I'm using:
- fuseki 0.2.1-SNAPSHOT
-arq 2.8.9-SNAPSHOT
-larq 0.2.2-incubating-SNAPSHOT
According to the LARQ's pom.xml file [1], LARQ
0.2.2-incubating-SNAPSHOT now
depends on the new ARQ SNAPSHOTs.
Precisely, it depends on
org.apache.jena:jena-arq:2.8.9-incubating-SNAPSHOT
Please note the new groupId and artifactId for ARQ.

New ARQ SNAPSHOTs are available here [2].

   [1]
https://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk/pom.xml
   [2]
https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-arq/2.8.9-incubating-SNAPSHOT/

I've updated my Fuseki's pom.xml with the new groupId and artifactId for
ARQ.
<ver.arq>2.8.9-incubating-SNAPSHOT</ver.arq>
<ver.tdb>0.8.11-SNAPSHOT</ver.tdb>
<ver.larq>0.2.2-incubating-SNAPSHOT</ver.larq>
     [...]
</properties>

<dependencies>
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>jena-arq</artifactId>
<version>${ver.arq}</version>
<!-- This is temporary and necessary, until Lucene and LARQ are removed
from ARQ -->
<exclusions>
             [...]
</exclusions>
</dependency>

<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>jena-arq</artifactId>
     [ ...]

Why don't you change it on the svn repository?
-lucene 3.1.0

My config.ttl file has not changed:

[...]
<#books>      rdf:type ja:RDFDataset ;
      rdfs:label "Books" ;
      ja:defaultGraph
        [ rdfs:label "discours_de_la_methode.rdf" ;
          a ja:MemoryModel ;
          ja:content [ja:externalContent<file:Data/file.rdf>   ] ;
        ] ;
      .

<#dataset>   rdf:type      tdb:DatasetTDB ;
      tdb:location "/tmp/tdb" ;
      ja:textIndex "/tmp/lucene" ;
      # Query timeout on this dataset (milliseconds)
      ja:context [ ja:cxtName "arq:queryTimeout" ;  ja:cxtValue "1000"
] ;
##      tdb:unionDefaultGraph true ;


Before running the fuseki server, i build my triple store with the
command-line:
java -cp target/fuseki-0.2.1-SNAPSHOT-sys.jar tdb.tdbloader
--loc=/tmp/tdb Data/file.rdf
Can you please try:

   - stop Fuseki
   - delete /tmp/lucence
   - restart Fuseki
Before running fuseki, i always clean up /tmp/tdb and /tmp/lucene:
----------------
#!/bin/bash
rm -rf /tmp/lucene
rm -rf /tmp/tdb
java -cp target/fuseki-0.2.1-SNAPSHOT-sys.jar tdb.tdbloader
--loc=/tmp/tdb Data/file.rdf
./fuseki-server --config=config.ttl
----------------

LARQ will now behave like this:

   - if the directory exists with a Lucene index, it will leave it
untouched
   - if the directory does not exists it will create it and index your
data

What do you have in your /tmp/lucene directory?

You're right - there is something wrong around the lucene index building
process: i have only a write.lock file is
this directory (which is empty).

Is this part correct in my configuration file?
Yes, it is.

But, if you have a /tmp/lucene directory already (perhaps with some
corrupted index/empty in it, LARQ will not touch it. This is because
we do not want to touch existing Lucene indexes).

So, please, try exactly this:

  1. stop Fuseki, make sure Fuseki and your app are not running
  2. rm -rf /tmp/lucene
  3. restart Fuseki or your app (make sure your app does not create an
     empty /tmp/lucene directory before LARQ get the chance to index
     your data

What do you have in the /tmp/lucene directory if you do that?

The same empty write.lock file...
I'll try the solution you proposed in the next mail !!!

Paolo


<#dataset>   rdf:type      tdb:DatasetTDB ;
     tdb:location "/tmp/tdb" ;
     ja:textIndex "/tmp/lucene" ;
     # Query timeout on this dataset (milliseconds)
     ja:context [ ja:cxtName "arq:queryTimeout" ;  ja:cxtValue "1000" ] ;
##      tdb:unionDefaultGraph true ;

Thank you.
Jérôme


So, i've no error - juste 0 result...

Any ideas?

Thank you.

Let us know how it goes,
Paolo

Reply via email to