You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Otis Gospodnetic (JIRA)" <ji...@apache.org> on 2007/01/19 16:43:30 UTC
[jira] Resolved: (LUCENE-779) behaviour of Lucene in tokenizing -
causes query problems
[ https://issues.apache.org/jira/browse/LUCENE-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Otis Gospodnetic resolved LUCENE-779.
-------------------------------------
Resolution: Invalid
This is not a Lucene limitation/bug. Atlassian guys could/should change how they handle numbers and solve the problem.
> behaviour of Lucene in tokenizing - causes query problems
> ---------------------------------------------------------
>
> Key: LUCENE-779
> URL: https://issues.apache.org/jira/browse/LUCENE-779
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Environment: SLES9.3, JIRA 3.6.3 (Standalone)
> Reporter: Suresh Chandran
> Attachments: query error.doc
>
>
> I recently submitted a problem with queries to Atlassian Support team and they have pointed out that it is an issue with Lucene. I'm copying the contents from my support request to Atlassian. Please help.
> Question to Atlassian:
> When I use "text search" to query an item from summary it gives me zero match. But when I use query through custom field, I get results displayed properly.
> In the attachment, I did a query for no: 10012363 using text search and I know this entry is part of the summary for several issues. But the result says "no matching issues found".
> But when I selected, Vendor name and number, I get proper results. I tried re-indexing, still no help
> Response from Atlassian:
> The reason why you couldn't receive any results from the query is due to the behaviour of Lucene (an Apache-developed search and index library being used in JIRA) in tokenizing.
> For example, *Invoice Number-123456-API ASSOCIATES-10012363* is tokenized to:
> {noformat}Invoice
> Number-123456-API
> ASSOCIATES-10012363{noformat}
> In this case, {{Number-123456-API}} and {{ASSOCIATES-10012363}} are recognized as {{NUM}} (e.g. floating point, serial, model numbers, ip addresses, etc.).
> ~(Hope this doesn't sound too technical to you.)~
> You can somehow call this a limitation of the third party library. If you are keen to have it improved, feel free to raise a support request at [our issue tracker|http://jira.atlassian.com] or perhaps try asking it at [Lucene's issue tracker|http://issues.apache.org/jira/browse/LUCENE].
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org