<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Your analysis is correct. The restriction is applied to the search results. Same with ~.<div><br></div><div>I'm not sure it is a bug, but if it is confusing to end users then it ought to be improved.</div><div><br></div><div>One way to do this is to change how the index is created by also indexing the cardinal value of the verse w/in the av11n and then converting the [gen-exo] to proper lucene search request fragment.</div><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div><br><div><div>On Sep 4, 2012, at 8:14 AM, Chris Burrell <<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">My presumption was wrong. This only affects ranked searches, because "non-ranked" searches do no use the TopScoreCollector and thereby completely ignore the searchModifier (possibly a bug? since maxResults is ignored?)<div>
<br>Chris</div><div><br><div><br></div><div><br><br><div class="gmail_quote">On 4 September 2012 11:05, Chris Burrell <span dir="ltr"><<a href="mailto:chris@burrell.me.uk" target="_blank">chris@burrell.me.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This only seems to affect ranked searches. Presumably because JSword restricts the Lucene range if it ordered by Passage.<div class="HOEnZb">
<div class="h5"><div><br><br><div class="gmail_quote">On 4 September 2012 11:01, Chris Burrell <span dir="ltr"><<a href="mailto:chris@burrell.me.uk" target="_blank">chris@burrell.me.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<div><br></div><div>Not sure if this is a bug, but thought it worth mentioning here. The restrictions to passages in searches don't play well with the MaxResults on the DefaultSearchModifier. In my case, I'm looking at +[John 4] with and my user interface shows the first 50 results on each page.</div>
<div><br></div><div> final DefaultSearchModifier modifier = new DefaultSearchModifier();</div><div>modifier.setMaxResults(50);</div><div>modifier.setRanked(true);</div><div><br></div><div>bible.find("water +[John 4]");</div>
<div><br></div><div>Unfortunately, that only gives me back 2 results, because the other 48 are not the in the first 50 retrieved by Lucene.</div><span><font color="#888888"><div><br></div><div>Chris</div><div>
<br></div>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>
_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>http://www.crosswire.org/mailman/listinfo/jsword-devel<br></blockquote></div><br></div></body></html>