One option of course would be to store all document content as triples
to Jena, but that might lead to other trouble since Jena is not meant to
be used that way.
On 26/02/2019 20:29, ajs6f wrote:
I'm not sure there are any widely-known best practices for that pattern, but I
defer to Osma a
I'm not sure there are any widely-known best practices for that pattern, but I
defer to Osma and Chris.
My limited understanding of Lucene implies that only one JVM at a time can lock
an index, but the last time I looked at that question was years ago, so take
that with a bucket of salt.
ajs6
Reason I'm asking this is that now, with external doxument index, we
can't do any paging which results very slow and heavy queries on
document index. We have to read all results from external Lucene,
because we need to apply filtering to result by metadata fields which
are store in Jena.
F
Not sure. Reading Jena text documentation, it states that external
document contents can be added into Jena text index.
Just not sure how this should be done in practice. How to handle
concurrency, and how exactly add documents so that we could make sparql
queries that target content and me
Are you asking how to use an extant Lucene index with your text documents in it
for Jena's text index as well?
ajs6f
> On Feb 14, 2019, at 6:23 AM, Mikael Pesonen
> wrote:
>
>
> Hi,
>
> Our system stores documents with separate rest API and document id's are
> stored, along with document m
Hi,
Our system stores documents with separate rest API and document id's are
stored, along with document metadata, to Jena db. we would like to make
text queries that target both the document contents and meta data.
Is there a recommended/supported way to make this happen on Jena and Lucene
