se the SnowballAnalyzer, and SpanishStemmer donĀ“t have a default
stopword set.
SnowballAnalyzer constructor:
/** Builds the named analyzer with no stop words. */
public SnowballAnalyzer(String name) {
this.name = name;
}
Note the comment.
Bye,
Ernesto.
- Original Message -
Fro
"sabeis", "saben",
"ultimo", "largo", "bastante", "haces", "muchos", "aquellos", "aquellas",
"sus", "entonces", "tiempo",
"verdad", "verdadero", "verda
Do you mind sharing how you implemented your SpanishAnalyzer using Snowball?
Sorry I can't help with your question. I am trying to implement Snowball Spanish or a
Spanish Analyzer in Lucene.
thanks,
chad.
-Original Message-
From: Ernesto De Santis [mailto:[EMAIL PROTECTED]
Sent: Monday
Thanks for the info Grant.
<<
As for indexes, do you anticipate adding more fields later in Spanish?
Is the content just a translation of the English, or do you have
separate conetent in Spanish? Are your users querying in only one
language (cross-lingual) or are the Spanish speakers only query
Hello,
I'm interested in any feedback from anyone who has worked through implementing
Internationalization (I18N) search with Lucene or has ideas for this requirement.
Currently, we're using Lucene with straight English and are looking to add Spanish to
the mix (with maybe more languages to fo
Hello,
I'm interested in any feedback from anyone who has worked through implementing
Internationalization (I18N) search with Lucene or has ideas for this requirement.
Currently, we're using Lucene with straight English and are looking to add Spanish to
the mix (with maybe more languages to fo
We have a requirement to return documents with a "title" field that starts with a
certain letter. Is there a way to do something like this? We're using the
StandardAnalyzer
Example title fields:
This is the title of a document.
And this is a title of a different document.
This query doesn
See MultiFieldQueryParser, like this:
String[] fields = getFieldsArray();
Query multiFieldQuery = MultiFieldQueryParser.parse(this.queryString,
fields,
new StandardAnalyzer())
]
Sent: Fri 3/26/2004 1:25 PM
To: Lucene Users List
Cc:
Subject: Re: too many files open error
On Mar 26, 2004, at 1:33 PM, Chad Small wrote:
> Is this :) serious?
This is open-source. I'm only as serious as
Is this :) serious?
Because we have a need/interest in the new field sorting capabilities and QueryParser
keyword handling of dashes ("-") that would be in 1.4, I believe. It's so much easier
to explain that we'll use a "final" release of Lucene instead of a "dev build" Lucene.
If so, w
Was there any conclusion to message:
http://issues.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=6762
Regarding "Ordering by a Field"? I have a similar need and didn't see the resolusion
in that thread. Is it a current patch to the 1.3-final, I could see one?
My other option, I guess, is
Ahh, without the bin on the javacc.home - 3.2 seems to work for me to.
-Original Message-
From: Chad Small
Sent: Wed 3/24/2004 8:34 AM
To: Lucene Users List
Cc:
Subject: RE: Query syntax on Keyword field question
Otis
--- Chad Small <[EMAIL PROTECTED]> wrote:
> thanks. I was in the process of getting javacc3.2 setup. I'll have
> to hunt for 2.x.
>
> chad.
>
> -Original Message-
>
For others reference - here is the old version url:
https://javacc.dev.java.net/servlets/ProjectDocumentList?folderID=212
-Original Message-
From: Chad Small
Sent: Wed 3/24/2004 8:07 AM
To: Lucene Users List
Cc:
Subject: RE: Query
thanks. I was in the process of getting javacc3.2 setup. I'll have to hunt for 2.x.
chad.
-Original Message-
From: Morus Walter [mailto:[EMAIL PROTECTED]
Sent: Wed 3/24/2004 8:00 AM
To: Lucene Users List
Cc:
Subject: RE: Query syntax
l Message-
From: Morus Walter [mailto:[EMAIL PROTECTED]
Sent: Wed 3/24/2004 1:43 AM
To: Lucene Users List
Cc:
Subject: RE: Query syntax on Keyword field question
Chad Small writes:
> Here i
org.apache.lucene.analysis.StopAnalyzer:
[hw] [nci] [topics]
org.apache.lucene.analysis.standard.StandardAnalyzer:
[hw] [nci] [topics]
healthecare.domain.lucenesearch.KeywordAnalyzer:
[HW-NCI_TOPICS]
query.ToString = category:HW -"nci topics" +space
junit.framework.ComparisonFailure: HW-NCI
Thanks-you Erik and Incze. I now understand the issue and I'm trying to create a
"KeywordAnalyzer" as suggested from you book excerpt, Erik:
http://issues.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=6727
However, not being all that familiar with the Analyzer framework, I'm not sure how to
i
a match.
I found a message that talked about having to use the the Query API when searching
Keyword fields in the index. Is this true?
Is there not a way to get the MultiFieldQueryParser to find a match on this keyword?
thanks,
chad.
-Original Message-
From: Chad Small
Hello,
How can I format a query to get a hit?
I'm using the StandardAnalyzer() at both index and search time.
If I'm indexing a field like this:
luceneDocument.add(Field.Keyword("category","HW-NCI_TOPICS"));
I've tried the following with no success:
// String searchArgs = "HW\\-NCI_
20 matches
Mail list logo