lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wettin (JIRA)" <>
Subject [jira] Commented: (LUCENE-580) Pre-analyzed fields
Date Thu, 18 Jan 2007 17:04:30 GMT


Karl Wettin commented on LUCENE-580:

Nadav Har'El [18/Jan/07 08:21 AM]

> The description above suggests that it might not work if the same
> field name is used for two Field's, one stored and the other preanalyzed. 
> I think it is important that this combination (as well as all other 
> combinations) are supported. I actually use all these combinations in my
> code, and I don't see why it should cause problems.

Actually, I can't remember why I thought there could be a problem, nor can I think of one
now.  This code is from my pre-tests era, and it should could need some.

If you like this  strategy, I think it would be more elegant passing a factory rather than
the actual token stream.

> The patch has some strange changes in the comments, changing the word
>  "Index" to "NotificationService". I bet this wasn't intentional :-)

Hehe, that must be an old refactoring search and replace incident.

> Pre-analyzed fields
> -------------------
>                 Key: LUCENE-580
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Analysis
>    Affects Versions: 1.9
>            Reporter: Karl Wettin
>            Priority: Minor
>         Attachments: preanalyze.tar
> Adds the possibility to set a TokenStream at Field constrution time, available as tokenStreamValue
in addition to stringValue, readerValue and binaryValue.
> There might be some problems with mixing stored fields with the same name as a field
with tokenStreamValue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message