Hello Andy,
Mea culpa!! I finally tracked down my problem. The testbed was running a
slightly older version than I had thought. Now that I’m using up-to-date I’m
seeing the debug info that was added 19 Aug.
Sorry for wasting b/w,
Chris
> On Oct 23, 2017, at 4:58 PM, Chris Tomlinson
Hi Andy,
The "Lucene query: {} ({})” message is not coming out at all. I try a variety
of queries, and other parameter settings and since the cache key is such that
any change in query, limit, language snd such leads to another key I should see
many such log statements.
In any event, I’ll
That all looks right.
Is the message not coming out at all or coming out once only? I ask
because it is in a "getOrFill" so the Callable is only called when there
is a cache miss.
Andy
On 22/10/17 18:22, Chris Tomlinson wrote:
Hello Andy,
Thank you for the reply. I’m apparently not
Hello Andy,
Thank you for the reply. I’m apparently not facile with log4j.properties. I've
tried several configurations and I'm only able to get the TextQueryPF
log.debug() to fire:
> [2017-10-22 16:47:52] Fuseki INFO [1] POST
> http://localhost:13180/fuseki/bdrcrw/query
> [2017-10-22
On 20/10/17 20:00, Chris Tomlinson wrote:
Hi,
I’m interested in looking into whether and how it might be possible to
incorporate Lucene highlighting into jena-text. I don’t see any other work, but
perhaps others have dealt with the topic already. I was thinking of some sort
of a 4th return