Hello,
I have added the issue:
https://issues.apache.org/jira/browse/LUCENENET-486 A testproject is
attached.
Björn
Am 17.04.2012 20:40, schrieb Christopher Currens:
I should also add, that directly reading the token stream, will produce
bjor (no wildcard) from björ*.
Björn,
It would be
wouldn't be
what you want.
DIGY
-Original Message-
From: Björn Kremer [mailto:b...@patorg.de]
Sent: Tuesday, April 17, 2012 12:59 PM
To: lucene-net-...@lucene.apache.org
Subject: Wildcard queries are not analyzed
Hello,
maybe I have found a little lucene problem: Wildcard queries
Hello,
maybe I have found a little lucene problem: Wildcard queries are not
analyzed correctly. I'm using the german analyzer with the
'GermanDIN2Stemmer'.
In the lucene-index my name('Björn') is stored as 'bjorn'. If I performe
a wildcard query like 'björ*' the function 'GetPrefixQuery'
of my
ideas. Maybe it is useful
to implement a better detection later.
Björn
Am 16.01.2012 13:27, schrieb Robert Jordan:
Hi Björn,
On 16.01.2012 11:28, Björn Kremer wrote:
Hello,
of course you are right. They should have the same root. But on the over
hand, most of my customers are very
Hello,
I have a little optimisation for the GermanStemmer.vb (in
Contrib.Analyzers) class. At the moment the function Substitute
converts the german Umlaute ä in a, ö ino and ü in u. This
is not the correct german translation. They must be converted to ae,
oe and ue. So I can write the name
Hello,
I can't build the Contrib.FastVectorHighlighter project from the
current lucene 2.9.4 package. My main project is a Visual Basic .NET
Winforms application. This application has a direct project reference
to the Contrib.FastVectorHighlighter project. Unfortunaly the
Hello,
here is a little optimization for the autocomplete function(see
attachment or http://pastebin.de/20088). The autocomplete function
compares the string distance for better matches now.
Björn
Am 02.11.2011 18:17, schrieb startrekfan75:
Hi,
I'd like to suggest a new feature for the
Hello,
there is a little bug in the SpellChecker.cs class. The finalizer of
this class calls the close method even if the SpellChecker is already
closed. This causes an unhandled exception.
This should work better:
~SpellChecker()
{
if (closed == false)
{
Hello,
i have just read that google has optimised its ranking. Now google shows
more relevant results on the first pagen as before. Is there a chance to
get advantage of this ranking algorithm with Lucene?
Thank You
Björn
Herndon:
Hi Björn Kremer!,
There is currently not a release date set for Lucene.Net 3.0. A
roadmap that covers a Lucene.Net release will most likely be developed
when we've made progress on the 2.9.x releases and infrastructure
changes that are currently be discussed on the mailing list.
I could
Hi,
ist there a releasedate for Lucene.NET 3.0 or a roadmap? When is
Lucene.NET released official?(Without incubator state)
Thank You
Björn
11 matches
Mail list logo
