On Sat, Dec 4, 2010 at 6:05 PM, Teruhiko Kurosaka wrote:
> Thank you, Robert, substituting getAttribute with addAttribute worked!
>
> But I don't understand why. Could you help me to understand the mechanics?
>
> In my setting,
> hasAttribute(PayloadAttribute.class) returns false.
>
> So I though
rosaka [mailto:k...@basistech.com]
> Sent: Sunday, December 05, 2010 12:05 AM
> To: java-user@lucene.apache.org
> Subject: Re: PayloadAttribute behavior change between Lucene 2.9/3.0 and
> the trunk
>
> Thank you, Robert, substituting getAttribute with addAttribute worked!
>
> But
Thank you, Robert, substituting getAttribute with addAttribute worked!
But I don't understand why. Could you help me to understand the mechanics?
In my setting,
hasAttribute(PayloadAttribute.class) returns false.
So I thought addAttribute(PayloadAttribute.class) would just
create a new PayloadA
On Fri, Dec 3, 2010 at 10:15 PM, Teruhiko Kurosaka wrote:
> Hello,
> I have a Tokenizer that generates a Payload, and a TokenFilter that uses it.
> These work well with Solr 1.4.0 (therefore Lucene 2.9.1?), but when
> I switched to the trunk version (I rebuilt the Tokenizer and TokenFilter
> using
Hello,
I have a Tokenizer that generates a Payload, and a TokenFilter that uses it.
These work well with Solr 1.4.0 (therefore Lucene 2.9.1?), but when
I switched to the trunk version (I rebuilt the Tokenizer and TokenFilter
using the Lucene jar from the trunk and ran it), I encountered with
this
