UsingSynonyms

Vote:
 

Is Synonyms only working for UnifiedSearch?

I have tried using it for Search(), but that always gives me 0 hits.

#132729
Aug 18, 2015 12:11
Vote:
 

No, it should work for standard queries as well. If you are using an older version of Find, make sure that you are invoking the correct extensions method(as there are two), found in EPiServer.Find.ClientExtensions. 

#132748
Aug 18, 2015 19:49
Vote:
 

Update: I have reported this as an issue to EPiServer support:  #25199 : UsingSynonyms results in 0 hits

Note: "MyType" is a standard .NET class added to the index by us. If I try the same on cms pages, UsingSynonyms() works as expected.
We are running Find as on premise solution (Virtual Applicance Raw).

#133280
Sep 01, 2015 8:23
Vote:
 

We're experiencing this exact same thing with VA Raw. Issue #25040.

UsingSynonyms returns 4-6 results, while the same search with an identical index (developer index) returns 40-50 hits. Turning off UsingSynonyms gives me all the results I want.

Only IContent-data in the index, just indexed with the default indexing job.

Support team couldn't reproduce after sending them a DB and copy of the source code, so I'm kinda lost. I even added a property to my search page to be able to turn synonyms quickly on and off, just to verify the difference...

#133286
Sep 01, 2015 10:06
Vote:
 

@Arve, just a shot in the dark here, but could you see if there is any difference in the indexed data for the two indexes? Use the explore view and do a diff on the same content for the two indexes. 

#133376
Sep 03, 2015 9:23
Vote:
 

It seems to contain the same stuff, but the order is different between the two. Could this be the result of different versions of the index or search engine, or is this not important?

The VA Raw-server we're running against gives me the following if i go to the root; (ip:9200/):

{

  "ok" : true,
  "status" : 200,
  "name" : "mysecretindexname",
  "version" : {
    "number" : "0.90.12",
    "build_hash" : "${buildNumber}",
    "build_timestamp" : "NA",
    "build_snapshot" : false,
    "lucene_version" : "4.6"
  },
  "tagline" : "You Know, for Search"
}


Does this seem right or wrong? We initially had another version, but got an upgrade script of some kind a while back. It was just passed on to the operations guys, so I have not neither seen nor executed it myself... :-\

#133395
Edited, Sep 03, 2015 12:27
Vote:
 

We're running the same version. Aparently, 0.90.12 is Elastic search version, not Find.

#133396
Sep 03, 2015 12:33
Vote:
 

Yup. I haven't found anywhere Find reports about its own version.

Client version: "Find .NET API Version: 9.5.0.2999" on all our environments

#133398
Sep 03, 2015 12:46
Vote:
 

Another shot in the dark: @Arve, could you specify fields in your query? Using InField(s). Unless you're already doing that... 

#133400
Sep 03, 2015 13:38
Vote:
 

Explicitly saying InField(...) makes no difference.. :-\

#133403
Sep 03, 2015 13:58
Vote:
 

...soooeh..anything new here? We're going live soon, and I'm supposed to teach people about this in a few days. Which won't be all that fun if one of the only "extra fancy features" they really want to use doesn't work. :-\

#133827
Sep 11, 2015 10:06
Vote:
 

I'm using Find 9.6.0.3185 and also experiencing this issue.

Have reported details to EPiServer Support (Request: #26740)

Is there any news or a bug report that I can vote for?

#139389
Oct 01, 2015 11:38
Vote:
 

The solution seems to be:

- Make sure the index does not have a default language. Include your languages, but leave the Default Languages-field empty.

- Make sure you're searching specific in fields (or SearchText() etc) - the all-field does not support synonyms.

#139390
Edited, Oct 01, 2015 11:55
Vote:
 

@Arve: Shouldn't it be "Make sure you're searching on specific fields..."? :)

#139391
Oct 01, 2015 11:57
Vote:
 

I have no idea what you're talking about.

(Never write forum answers and talk to people at the same time :) )

#139392
Oct 01, 2015 11:59
Vote:
 

Thanks @Arve, that's some useful info no doubt.

#139394
Oct 01, 2015 12:25
Vote:
 

Turned out the that, at the moment, developer indexes created at find.episerver.com doesn't support synonyms (at least not for my scenario, not using UnifiedSearch)

Tried creating a few of them thinking that there was something wrong with the index. 

I finally got it working after trying .UsingSynonyms() using a licensed production index (setup by EPiServer Operations)

Some details about my scenario:

- Find Client 9.6.0.3185

- Not using UnifiedSearch

- Searching in specific fields

#139424
Oct 02, 2015 7:59
Vote:
 

@Peter: UsingSynonyms is supported when using a developer index.

I have the following working:

 - AlloyDemoKit from github

 - Find Client 9.6.0.3185

 - Using UnifiedSearch 

 - Developer index

However, it's seems like there exists a bug or two connected to the feature.

#139426
Oct 02, 2015 8:23
Vote:
 

@Mari OK, so it's working when using UnifiedSearch, that's nice to know.

#139428
Oct 02, 2015 8:30