[
https://issues.apache.org/jira/browse/JENA-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248836#comment-16248836
]
Andy Seaborne commented on JENA-1388:
-------------------------------------
On the query side, lucene-doc per triple vs lucene-doc per subject (per
concept, per entity) isn't a big change. The index is a map "lucene-query" to
URI (actually, RDF term). I can't see a use case for lucene-doc per graph.
On the index building side, it is a big change. What is especially different is
updating documents as triples, which may be partial change. What might be more
practical is develop a separate indexer for the "per subject" case, which may
even only work for a complete index rebuild, offline, in the first instance.
Some of the assembler parts may also not apply - details need to be worked out.
> Lucene text search across multiple fields ("AND") yields no results
> -------------------------------------------------------------------
>
> Key: JENA-1388
> URL: https://issues.apache.org/jira/browse/JENA-1388
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
> Affects Versions: Jena 3.4.0
> Environment: CentOS 7.3, OpenJDK 64-Bit, v1.8.0_141-b16
> Reporter: Vilnis Termanis (Iotic Labs)
> Assignee: Osma Suominen
> Labels: index, lucene, search
> Attachments: config-fields.ttl, multi_field.ttl, multi_index.sparql
>
>
> Searching across two Lucene text indexed fields produces potentially
> unexpected results. (The following assumes that the string supplied to each
> field does match and is tied to the same uid/subject.)
> # A query across two fields with *OR* produces two equal rows
> # The same query but with *AND* produces no rows
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
