Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of yseeley@gmail.com designates
 74.125.78.25 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=IqXSizUoXHfsEuUGenziGTwrzPQk2arKtEHPeSd2MvBP7dfNoqASykBB/luw4+n4Rh
         Z6hgK3Ytt9bw6tp7z2m+CiUQIcZ4yb+GV/PCJz1RKij5xY1FKmUgUqk2UEUzfNaVvEFN
         m1VKKMBkRLI6RgkDB5PzAnABMZGar+VHxllOY=
MIME-Version: 1.0
In-Reply-To: <4A1AD456.6060402@gmail.com>
References: <2c138bed0905250935y503a7b84me7c16f22d29c8077@mail.gmail.com>
	 <c68e39170905250957v16a6d5e5l77a185b60963e8dd@mail.gmail.com>
	 <4A1AD456.6060402@gmail.com>
Date: Mon, 25 May 2009 13:59:16 -0400
Message-ID: <c68e39170905251059l276cb004u7ee8b111401cd3f8@mail.gmail.com>
Subject: Re: issue on trunk?
From: Yonik Seeley <yseeley@gmail.com>
To: solr-dev@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Perhaps we should use a factory method on SolrIndexSearcher (that way
we can wrap the reader and pass that to the SolrIndexSearcher
constructor?)

-Yonik

On Mon, May 25, 2009 at 1:24 PM, Mark Miller <markrmiller@gmail.com> wrote:
> Yonik Seeley wrote:
>>
>> On Mon, May 25, 2009 at 12:35 PM, Peter Wolanin
>> <peter.wolanin@acquia.com> wrote:
>>
>>>
>>> Playing with this last night, the error seems to occur for me only
>>> with an index created using a solr build from a couple weeks ago
>>> that's opened with a new solr build. =A0The error goes away if I issue =
a
>>> delete query for *:* and re-index the content.
>>>
>>
>> That's really strange... that really shouldn't be the case. =A0Perhaps
>> reopen() is acting a little different with the older index?
>> Please keep that index around if possible so we can get to the bottom of
>> this!
>>
>> Mark - could it be the changes from delegation to inheritance for
>> SolrIndexSearcher?
>> super(reader) is called before we get a chance to to wrap the reader
>> and make it a SolrIndexReader...
>>
>> -Yonik
>> http://www.lucidimagination.com
>>
>
> It could be. Good point - SolrIndexSearcher gets the plain reader and it
> used to get SolrIndexReader. My fault, because I did most of the thinking=
 on
> that pre SolrIndexReader patch. So I guess, Lucene would feed the Solr
> DocSet a regular reader instead of SolrIndexReader - no good. But, what I
> still don't understand is how that plays into Peter's comment above and m=
y
> inability to easily replicate the problem. I'll keep digging, but it soun=
ds
> like I may just revert back to delegation or override getIndexReader to
> return the SolrIndexReader - if thats done, we should prob deprecate
> getReader. We'd obviously like to fully understand whats happening in any
> case though. Until I can tickle the error, I can only guess myself.
>
> - Mark
>
>
> --
> - Mark
>
> http://www.lucidimagination.com
>
>
>
>