Andy, I finally got to building and testing your update. I still get the same error and stack trace. It looks like the change you made needs to also be applied to TextIndexLucene.get$(IndexReader indexReader, String uri) as that is executed in the my sparql query I have.
On Fri, Jun 13, 2014 at 10:52 AM, Willie Milnor <[email protected]> wrote: > Thanks, Andy. > > We are already using a regex in a FILTER, and we're hoping/expecting free > text search to improve the performance. > > > On Thu, Jun 12, 2014 at 5:55 PM, Andy Seaborne <[email protected]> wrote: > >> On Thu, Jun 12, 2014 at 4:25 PM, Willie <[email protected]> wrote: >>> >>> 2 things here: >>>> >>>> 1. Below is the comment on >>>> org.apache.lucene.queryparser.flexible.standard. >>>> CommonQueryParserConfiguration.setLowercaseExpandedTerms. >>>> It does seem that what I want to do is possible. So I'm just curious >>>> I >>>> there is a way to access this functionality via Jena and it's free text >>>> search feature. >>>> >>>> voidsetLowercaseExpandedTerms(boolean lowercaseExpandedTerms) >>>> Set to true to allow leading wildcard characters. >>>> When set, * or ? are allowed as the first character of a PrefixQuery and >>>> WildcardQuery. Note that this can produce very slow queries on big >>>> indexes. >>>> >>>> Default: false. >>>> >>> >> I've just added that to jena-text in svn. >> >> >> >> >>>> >>> I can't say. I also would not try to, in this case. I expect performance >>> would be better using the filter. >>> >> >> >> A regex may well be better depending on the size and composition of the >> lucene index. >> >> Andy >> >> > > > -- > Cheers, > Willie > -- Cheers, Willie
