On Thu, Nov 29, 2012 at 4:57 PM, Trejkaz wrote:
> doubt we're not
Rats. Accidentally double-negatived that. I doubt we are the only ones. *
TX
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional com
On Wed, Nov 28, 2012 at 6:28 PM, Robert Muir wrote:
> My point is really that lucene (especially clear in 4.0) assumes
> indexreaders are immutable points in time. I don't think it makes sense for
> us to provide any e.g. filtercaching or similar otherwise, because this is
> a key simplification t
I revise the code to
SortField sortField[] = {new SortField("id", new
CustomComparatorSource(bitSet)),SortField.FIELD_SCORE};
Sort sort = new Sort(sortField);
TopFieldCollector topFieldCollector =
TopFieldCollector.create(sort, 1000, true, true, true, true);
index
Be aware that StandardAnalyzer changed slightly. This is particularly important
if you use it to analyze email addresses and certain text-numeral combinations.
My understanding is that the newer version of StandardAnalyzer is more
consistent with what it should be doing but if you relied on its
That sure looks like a bug! Could you open a Jira issue (
https://issues.apache.org/jira/browse/LUCENE ) and post a patch / test
case? Thanks!
Mike McCandless
http://blog.mikemccandless.com
On Wed, Nov 28, 2012 at 7:53 AM, d...@neusoft.com wrote:
> Is this a bug?
>
> when using group function
Is this a bug?
when using group function, I set "groupingSearch.setAllGroups(true);", but it
return groupCount = 0
I saw the source , I found that :
if (allGroupHeads) {
collectors.add(allGroupsCollector);
}
if (allGroupHeads) {
Scott Smith mainstreamdata.com> writes:
>
> I'm migrating code from Lucene 3.5 to 4.0. I have the following code which is
supposed to highlight text. I
> get the exception InvalidTokenOffsetsException. I have no idea what that
means. I am using a custom
> analyzer which seems to work for sea