Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Tue, 17 May 2011 12:54:48 +0000 (UTC)
From: "Michael McCandless (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <990995862.18991.1305636888823.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-2119) IndexSchema should log warning if
 <analyzer> is declared with charfilter/tokenizer/tokenfiler out of order
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034740#comment-13034740 ] 

Michael McCandless commented on SOLR-2119:
------------------------------------------

+1 for hard error.

In general for problems we can detect at startup we should not start the server.  Users rarely see/do something about the warnings.

I think this would be a good service to those users who trip the hard error on upgrade: it means Solr is not doing what they thought they asked it to do.

> IndexSchema should log warning if <analyzer> is declared with charfilter/tokenizer/tokenfiler out of order
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-2119
>                 URL: https://issues.apache.org/jira/browse/SOLR-2119
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Hoss Man
>             Fix For: 3.2, 4.0
>
>
> There seems to be a segment of hte user population that has a hard time understanding the distinction between a charfilter, a tokenizer, and a tokenfilter -- while we can certianly try to improve the documentation about what exactly each does, and when they take affect in the analysis chain, one other thing we should do is try to educate people when they constuct their <analyzer> in a way that doesn't make any sense.
> at the moment, some people are attempting to do things like "move the Foo <tokenFilter/> before the <tokenizer/>" to try and get certain behavior ... at a minimum we should log a warning in this case that doing that doesn't have the desired effect
> (we could easily make such a situation fail to initialize, but i'm not convinced that would be the best course of action, since some people may have schema's where they have declared a charFilter or tokenizer out of order relative to their tokenFilters, but are still getting "correct" results that work for them, and breaking their instance on upgrade doens't seem like it would be productive)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org