Swedish character search does not work from 2.5 client to 3.5 server

73 views
Skip to first unread message

ZNS

unread,
Apr 10, 2017, 10:21:56 AM4/10/17
to RavenDB - 2nd generation document database
Hi,

We've updated our ravendb to 3.5 but still have some 2.5 client applications running. It seems doing text query containing swedish characters like "å, ä, ö" does not work against the ravendb 3.5 server. The query doesn't yield any results. Switch to a 2.5 server and the query works. I understand if this is not supposed to be supported, just wanted to check if it makes any sense to you?

Oren Eini (Ayende Rahien)

unread,
Apr 12, 2017, 3:51:36 AM4/12/17
to ravendb
Can you enable the classic parser and see if this changes anything?

Hibernating Rhinos Ltd  

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

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

 


On Mon, Apr 10, 2017 at 5:21 PM, ZNS <ulrik.a...@gmail.com> wrote:
Hi,

We've updated our ravendb to 3.5 but still have some 2.5 client applications running. It seems doing text query containing swedish characters like "å, ä, ö" does not work against the ravendb 3.5 server. The query doesn't yield any results. Switch to a 2.5 server and the query works. I understand if this is not supposed to be supported, just wanted to check if it makes any sense to you?

--
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.

ZNS

unread,
Apr 12, 2017, 6:40:22 AM4/12/17
to RavenDB - 2nd generation document database

Sorry to have to ask, but I don't know how to do that. Tried to google but with little success.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

Grisha Kotler

unread,
Apr 12, 2017, 6:48:46 AM4/12/17
to rav...@googlegroups.com
This is a server side configuration key: Raven/Indexing/UseLuceneASTParser.
You'll need to set it to false.

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

Grisha Kotler l RavenDB Core Team Developer Mobile: +972-54-586-8647

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


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

Tal Weiss

unread,
Apr 16, 2017, 2:15:13 AM4/16/17
to RavenDB - 2nd generation document database
I believe this has to do with the double escaping support for legacy clients. A related issue was already addressed, what version of the server are you using (exact version not just 3.5)?

ZNS

unread,
Apr 21, 2017, 8:54:32 AM4/21/17
to RavenDB - 2nd generation document database

This was on 35183. We found another workaround which involved an existing custom analyzer so haven't tested the classic parser solution. Thanks though.

Leslie Bayne

unread,
Nov 7, 2017, 5:17:19 AM11/7/17
to RavenDB - 2nd generation document database
I have the same problem, running Server Build #35187.
I tried to set Raven/Indexing/UseLuceneASTParser = false
it did not help....

Oren Eini (Ayende Rahien)

unread,
Nov 7, 2017, 5:37:54 AM11/7/17
to ravendb
Can you create a failing test case?
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