analyzer that treats special characters just like
any
other. The index works fine all the time even when the query includes
special characters, except when the special characters come to the
begining
of the query.
I'm using spanTermQuery and wildCardQuery, and they both seem to suffer
characters just like
any
other. The index works fine all the time even when the query includes
special characters, except when the special characters come to the
begining
of the query.
I'm using spanTermQuery and wildCardQuery, and they both seem to suffer
the
same issue with queries
works fine all the time even when the query includes
special characters, except when the special characters come to the
begining
of the query.
I'm using spanTermQuery and wildCardQuery, and they both seem to
suffer
the
same issue with queries begining with special characters
a custom analyzer that treats special characters just
like
any
other. The index works fine all the time even when the query
includes
special characters, except when the special characters come to the
begining
of the query.
I'm using spanTermQuery and wildCardQuery, and they both
version has to be the prime suspect for any problems.
--
Ian.
On Thu, Jan 10, 2013 at 12:08 PM, Hankyu Kim gksr...@gmail.com
wrote:
Hi.
I've created a custom analyzer that treats special characters just
like
any
other. The index works fine all the time even when the query
even when the query includes
special characters, except when the special characters come to the
begining
of the query.
I'm using spanTermQuery and wildCardQuery, and they both seem to suffer
the
same issue with queries begining with special characters. Is it a
limitation of Lucene or am I
the query includes
special characters, except when the special characters come to the begining
of the query.
I'm using spanTermQuery and wildCardQuery, and they both seem to suffer the
same issue with queries begining with special characters. Is it a
limitation of Lucene or am I missing something
h...@all
I'd like to do a fuzzy search with german special characters. For instance I
want to query for müller, but also terms like mueller should be respected,
as ü can also be written as ue. How could this be done? At index creation time,
I could convert ü to ue, and just use the ue
As for suggestions on how to do this, I have no other than
to make sure that you can create the queries necessary to obtain
the required output.
Regards,
Paul Elschot
On Sunday 30 September 2007 09:20, Mohammad Norouzi wrote:
Hi Paul,
thanks, I dot your idea, now I am planing to implement
Hi Paul,
thanks, I dot your idea, now I am planing to implement this,
de-normalization, now I just need your suggestion on this issue and tell
me which one is the best
I am considering to put a Field as follows:
my_de_normalized_field
service_name : service_value
if there are more than one
On Thursday 20 September 2007 07:29, Mohammad Norouzi wrote:
Sorry Paul I just hurried in replying ;)
I read the documents of Lucene about query syntax and I figured out the what
is the difference
but my problem is different, this is preoccupied my mind and I am under
pressure to solve this
well, you mean we should separate documents just like relational tables in
databases ?
if yes, how to make the relationship between those documents
thank you so much Paul
On 9/20/07, Paul Elschot [EMAIL PROTECTED] wrote:
On Thursday 20 September 2007 07:29, Mohammad Norouzi wrote:
Sorry Paul
On Thursday 20 September 2007 09:19, Mohammad Norouzi wrote:
well, you mean we should separate documents just like relational tables in
databases ?
Quite the contrary, it's called _de_normalization. This means that the
documents in lucene normally contain more information than is present
in a
Hi Paul,
would you tell me what is the difference between AND and + ?
I tried both but get different result
with AND I get 1777 documents and with + I get nearly 25000 ?
On 9/17/07, Paul Elschot [EMAIL PROTECTED] wrote:
On Monday 17 September 2007 11:40, Mohammad Norouzi wrote:
Hi
I have a
Sorry Paul I just hurried in replying ;)
I read the documents of Lucene about query syntax and I figured out the what
is the difference
but my problem is different, this is preoccupied my mind and I am under
pressure to solve this problem, after analyzing the results I get, now I
think we need a
Hi
I have a problem in getting correct result from Lucene, consider we have an
index containing documents with fields field1 and field2 etc. now I want
to have documents in which their field1 are equal one by one and their
field2 with two different value
to clarify consider I have this query:
On Monday 17 September 2007 11:40, Mohammad Norouzi wrote:
Hi
I have a problem in getting correct result from Lucene, consider we have an
index containing documents with fields field1 and field2 etc. now I want
to have documents in which their field1 are equal one by one and their
field2 with
17 matches
Mail list logo
