jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Castagna (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JENA-9) LARQ as a separate module from ARQ
Date Tue, 21 Dec 2010 17:16:00 GMT

    [ https://issues.apache.org/jira/browse/JENA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973772#action_12973772
] 

Paolo Castagna commented on JENA-9:
-----------------------------------

If you want to give it a try and double check that removals/unindex work as expected, you
can use SNAPSHOTs here:
http://oss.talisplatform.com/content/repositories/talis-snapshots/com/hp/hpl/jena/larq/

<dependency>
  <groupId>com.hp.hpl.jena</groupId>
  <artifactId>larq</artifactId>
  <version>0.1.3-SNAPSHOT</version>
</dependency>

Make sure to add the repository as well:

  <repositories>
    <repository>
      <id>oss-talis-snapshots</id>
      <url>http://oss.talisplatform.com/content/repositories/talis-snapshots/</url>
    </repository>
  </repositories>


> LARQ as a separate module from ARQ
> ----------------------------------
>
>                 Key: JENA-9
>                 URL: https://issues.apache.org/jira/browse/JENA-9
>             Project: Jena
>          Issue Type: Task
>          Components: LARQ
>            Reporter: Paolo Castagna
>            Assignee: Paolo Castagna
>
> LARQ can be extracted from ARQ as a separate module depending on ARQ.
> ARQ should not depend on LARQ (to avoid dependency cycles) and it could check if LARQ
is available in the classpath and wire the property function in dynamically.
> LARQ can have a different release cycle from ARQ and people who do not need free text
search will not need to include Lucene in their classpath.
> A separate (experimental) module is available here: https://jena.svn.sourceforge.net/svnroot/jena/LARQ/trunk/
> List of things to do/decide includes:
>  - Merge JENA-5 fix 
>  - Upgrade Lucene version to 2.9.3 and fix tests (if there are failures).
>  - Remove code using deprecated Lucene APIs and upgrade to Lucene 3.0.x.
>  - Decide how many results to return when the user does not specify it, 1000? More?
>  - Should we use the index to suppress duplicates instead of in-memory data structures?
>  - How do we implement removals/unindex?
>     - We could use the Model to decide when there are no more triples with a specified
literal and therefore it's ok to remove it from Lucene.
>  - See how the new NRT capabilities of Lucene can be used from LARQ.
>  - Review package names (currently c.h.h.j.sparql.larq and c.h.h.j.query.larq). Should
we move to c.h.h.j.larq.*?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message