Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Sun, 20 Feb 2011 23:52:38 +0000 (UTC)
From: "Mark Miller (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1675389520.4947.1298245958525.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <24536533.87981295551483648.JavaMail.jira@thor>
Subject: [jira] Resolved: (LUCENE-2877) BUG in the
 org.apache.lucene.analysis.br.BrazilianAnalyzer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LUCENE-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller resolved LUCENE-2877.
---------------------------------

    Resolution: Invalid
      Assignee: Mark Miller

Let's try not to be too scary to users trying to report bugs eh? Concerned committers should properly update fix/affects versions as they can, but I don't know we need to lock them down to committers.

Thank's for the report Renan. It seems your code might be off. Often times, it's best to email the user list before creating JIRA issues - unless you are fairly confident in your find.

It seems this was not a bug, but user error. If you find that our analysis is off, please comment on this issue.

Thanks!

> BUG in the org.apache.lucene.analysis.br.BrazilianAnalyzer
> ----------------------------------------------------------
>
>                 Key: LUCENE-2877
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2877
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: contrib/analyzers
>    Affects Versions: 3.0.2
>         Environment: Windows 7 64bits, Eclipse Helios
>            Reporter: Renan Pedro Terra de Oliveira
>            Assignee: Mark Miller
>            Priority: Critical
>
> One weird bug with this field is that instead of "false", you have to search for "falsee" to get the correct results.
> The same behavior happen with other fields that stored in the index and not analyzed.
> Example of create fields to indexing:
> Field field = new Field("situacaoDocumento", "ATIVO", Field.Store.YES, Field.Index.NOT_ANALYZED);
> or
> Field field = new Field("copia", "false", Field.Store.YES, Field.Index.NOT_ANALYZED);
> Example search i need to do, but nothing get correct result:
> 			IndexSearcher searcher = ...;
> 			TopScoreDocCollector collector = ....;
>                         Query query = MultiFieldQueryParser.parse(VERSION, "copia:false", "copia", flags, getAnalyzer());
> 			searcher.search(query, collector);
> 			ScoreDoc[] hits = collector.topDocs().scoreDocs;
> 			if (hits.length > 0) {
> 				return searcher.doc(0);
> 			}
> 			return null;
> Example search i do to work:
> 			IndexSearcher searcher = ...;
> 			TopScoreDocCollector collector = ....;
>                         Query query = MultiFieldQueryParser.parse(VERSION, "copia:falsee", "copia", flags, getAnalyzer());
> 			searcher.search(query, collector);
> 			ScoreDoc[] hits = collector.topDocs().scoreDocs;
> 			if (hits.length > 0) {
> 				return searcher.doc(0);
> 			}
> 			return null;
> I tested on the Luke (Lucene Index Toolbox) and he prove the bug.

-- 
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