RE: Term no longer matches if PositionLengthAttr is set to two

2017-05-04 Thread Markus Jelsma
ent: Monday 1st May 2017 12:33 > To: java-user@lucene.apache.org; solr-user > Subject: RE: Term no longer matches if PositionLengthAttr is set to two > > Hello again, apologies for cross-posting and having to get back to this > unsolved problem. > > Initially i thought this

RE: Term no longer matches if PositionLengthAttr is set to two

2017-05-01 Thread Markus Jelsma
- > From:Markus Jelsma > Sent: Tuesday 25th April 2017 13:40 > To: java-user@lucene.apache.org > Subject: Term no longer matches if PositionLengthAttr is set to two > > Hello, > > We have a decompounder and recently implemented the PositionLengthAttribute > in it and

Term no longer matches if PositionLengthAttr is set to two

2017-04-25 Thread Markus Jelsma
Hello, We have a decompounder and recently implemented the PositionLengthAttribute in it and set it to 2 for a two-word compound such as drinkwater (drinking water in dutch). The decompounder runs both at index- and query-time on Solr 6.5.0. The problem is, q=content_nl:drinkwater no longer ret