Hi,
I am looking for an easy (~preferred) way of implementing customized search
with Lucene. What I mean by this is changing order of returned hits
according to user profile. In simple words I would like to be able to tweak
order of documents in Hits collection before it is presented to the client
But as fare as i see (in the API DOC), the GermanAnalyzer is attached
to the IndexWriter, i can't find an way to attach an analyzer it to a
single field... Or do i miss something? (There are tons of other
fields in the index where GermanAnalyzer fits perfect).
Am 12.10.2007 um 19:01 schrieb
Mark, That's working right out of the box. Thanks again.
-Original Message-
From: Mark Miller [mailto:[EMAIL PROTECTED]
Sent: Friday, October 12, 2007 2:06 PM
To: java-user@lucene.apache.org
Subject: Re: Wildcard & filters
No probwas a bit hasty though:
replace
= new BitSet();
wit
No probwas a bit hasty though:
replace
= new BitSet();
with
= new BitSet(reader.maxDocs());
Beard, Brian wrote:
Mark,
Thanks so much.
-Original Message-
From: Mark Miller [mailto:[EMAIL PROTECTED]
Sent: Friday, October 12, 2007 1:54 PM
To: java-user@lucene.apache.org
Subject
Mark,
Thanks so much.
-Original Message-
From: Mark Miller [mailto:[EMAIL PROTECTED]
Sent: Friday, October 12, 2007 1:54 PM
To: java-user@lucene.apache.org
Subject: Re: Wildcard & filters
Something along these lines:
public class WildcardFilter extends Filter {
private Term term;
Something along these lines:
public class WildcardFilter extends Filter {
private Term term;
public WildcardFilter(Term term) {
this.term = term;
}
@Override
public BitSet bits(IndexReader reader) throws IOException {
BitSet bits = new BitSet();
WildcardTermE
I'm trying to over-ride QueryParser.getWildcardQuery to use filtering.
I'm missing something, because the following still gets the
maxBooleanClauses limit.
I guess the terms are still expanded even though the query is wrapped in
a filter. How do I avoid the term expansion altogether? Is there a
b
On Friday 12 October 2007 15:48, Christian Aschoff wrote:
> indexWriter = new IndexWriter(MiscConstants.luceneDir,
> new GermanAnalyzer(), create);
> [...]
Not NO_NORMS is the problem but GermanAnalyzer. Try StandardAnalyzer on the
field you get the suggestions from.
Regards
Daniel
--
htt
Thank you Doron & Kyle,
You both pointed me in the right direction. For anyone finding this
thread in the email archive, here is what I've learned.
You can boost field weights either at indexing time or at query time.
For indexing time you call .setBoost(float) on the field before it has
been add
The Scorer.explain() method worked.
Thanks for the replies. I may be able to use MemoryIndex in a different
situation.
Paul Elschot wrote:
>
> On Wednesday 10 October 2007 18:44, lucene_user wrote:
>> I would like to score a single document from a corpus based on a given
>> query. The formula
Hi,
i tried to implement a 'did you mean'-function (and successed in some
way). But the hints from the SpellChecker are the stemmed versions of
the keywords.
For example, the search for the wrong word 'wasseraalfingen' results
in the hint 'wasseralfing' but should be 'wasseralfingen'. My
12 okt 2007 kl. 03.09 skrev Chris Hostetter:
: No, sorry, I'm still confused. It ought to be a term queries?
: > > System.out.println(new QueryParser("f", new Analyzer() {
: > > public TokenStream tokenStream(String string, Reader reader) {
: > > return new NGramTokenFilter(new Standard
Chris,
On Thu, October 11, 2007, Chris Hostetter wrote:
> ... are you talking about preventing people from including field
> specific queries in their query string? i'm guessing that you mean
> something like this is okay...
>
> solr title:bobby body:boy
>
> ...but this isn't...
>
>
13 matches
Mail list logo
