Searching on diacritics change?

52 views
Skip to first unread message

paulb...@gmail.com

unread,
Mar 16, 2017, 7:38:12 AM3/16/17
to RavenDB - 2nd generation document database
In our application we can search for products in a database by using an index.
I have for example a document with a property "Name", where "Name" is filled with "Others OB QDC 2000 drönare"

If I look into "Terms" for my index on the analyzed field "Name" in the raven studio, I get:
Name
- 2000
- drönare
- ob
- others
- qdc


When I do manual query in the Raven Studio with Raven version 3.0.30166 I get some unexpected results:

Name:others
returns the correct document

Name:dr*
returns the correct document

Name:drönare
returns nothing

Name:drö*
returns nothing

When I use RavenDB version 3.0.30037 it returns the document in all the above queries.

It looks like it has something to do with the special character ö.

Did something change between the 2 ravendb versions?

Paul

Oren Eini (Ayende Rahien)

unread,
Mar 16, 2017, 8:11:15 AM3/16/17
to ravendb
This should just work. What versions  are you working with?

Hibernating Rhinos Ltd  

Oren Eini l CEO Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 


--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

paulb...@gmail.com

unread,
Mar 16, 2017, 8:19:15 AM3/16/17
to RavenDB - 2nd generation document database
In 3.0.30166 we have the issue.
In 3.0.30037 the issue does not occur.

I do have to say that the database has been created by a .NET client with version 2.5.2991.0. But that goes for both server versions.

I could create an export of the database, to see if the result is the same on your end. There is just one document in there, so it is not very large.


Op donderdag 16 maart 2017 13:11:15 UTC+1 schreef Oren Eini:
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

Oren Eini (Ayende Rahien)

unread,
Mar 16, 2017, 8:20:28 AM3/16/17
to ravendb
Yes, that would be great
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

paulb...@gmail.com

unread,
Mar 16, 2017, 8:25:03 AM3/16/17
to RavenDB - 2nd generation document database
Here it is.

The index I use is ProductsAll.
A query to reproduce is: Name:drönare



Op donderdag 16 maart 2017 13:20:28 UTC+1 schreef Oren Eini:
RavenDB Diacritics.ravendump

Oren Eini (Ayende Rahien)

unread,
Mar 16, 2017, 8:48:08 AM3/16/17
to ravendb
You are forcibly setting the analyzer to use lower case, and that might be related
It worked when I tried it on my end
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

paulb...@gmail.com

unread,
Mar 16, 2017, 11:12:50 AM3/16/17
to RavenDB - 2nd generation document database
After some code debugging, it looks like this is an issue which is fixed in RavenDB 3.5
RavenDB-6247 issue when querying unicode from the browser fixed partially since we can't do anything when we have both url encoding and unicode chars


Can you tell me if this fix will be done in 3.0. That would really help us a lot.


Op donderdag 16 maart 2017 13:48:08 UTC+1 schreef Oren Eini:

Oren Eini (Ayende Rahien)

unread,
Mar 17, 2017, 8:01:39 AM3/17/17
to ravendb
We aren't servicing any non critical fixes to 3.0 at the moment. Since this impacts only the studio, you can either ignore it or use the workaround.
Set: Raven/Indexing/UseLuceneASTParser to true in the configuration
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

paulb...@gmail.com

unread,
Mar 17, 2017, 11:25:00 AM3/17/17
to RavenDB - 2nd generation document database
The problem is not just in the studio. That was just a way to reproduce the issue.
For us the issue occurs when using a .NET client older than 3.0.
Unfortunately we are using a client older than 3.0 because we also need support for 2.5 databases.

I would like a workaround if possible, but it looks like the Raven/Indexing/UseLuceneASTParser is only available starting from the 3.5 code.




Op vrijdag 17 maart 2017 13:01:39 UTC+1 schreef Oren Eini:

Tal Weiss

unread,
Mar 19, 2017, 4:30:46 AM3/19/17
to RavenDB - 2nd generation document database
I think i know what is causing this problem, it is an issue due to the v2.5 client been identified as the studio.
you can keep tack of the issue here http://issues.hibernatingrhinos.com/issue/RavenDB-6578

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Hibernating Rhinos Ltd  cid:image001.png@01CF95E2.8ED1B7D0

Tal Weiss l Core Team Developer Mobile:+972-54-802-4849

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811l Skype: talweiss1982

RavenDB paving the way to "Data Made Simplehttp://ravendb.net/ 

Tal Weiss

unread,
Mar 19, 2017, 5:44:15 AM3/19/17
to RavenDB - 2nd generation document database
just to be clear, are you seen the wrong query results from the 2.x client or just from the studio?

paulb...@gmail.com

unread,
Mar 20, 2017, 3:50:03 AM3/20/17
to RavenDB - 2nd generation document database
We are seeing the issue in both of them. (2.5 client and Raven studio)

Op zondag 19 maart 2017 10:44:15 UTC+1 schreef Tal Weiss:
--

Hibernating Rhinos Ltd  cid:image001.png@01CF95E2.8ED1B7D0

Tal Weiss l Core Team Developer Mobile:+972-54-802-4849

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811l Skype: talweiss1982

RavenDB paving the way to "Data Made Simplehttp://ravendb.net/ 

Oren Eini (Ayende Rahien)

unread,
Mar 20, 2017, 10:33:55 AM3/20/17
to ravendb
This issue has been fixed
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages