You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Paolo Castagna (Closed) (JIRA)" <ji...@apache.org> on 2012/01/30 14:48:10 UTC
[jira] [Closed] (JENA-9) LARQ as a separate module from ARQ
[ https://issues.apache.org/jira/browse/JENA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paolo Castagna closed JENA-9.
-----------------------------
Resolution: Fixed
> 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
> Attachments: larq-files.zip
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira