Shannon Deminick

Will be shipped with 3.2.1 today.

https://github.com/Shazwazza/Examine/releases/tag/v3.2.1

You cannot do document level boosting with the newer lucene version, in java this has been deprecated but in c# it has been removed  This describes all of the...

Hi, Examine will execute the Lucene query lazily one time when either TotalItemCount is resolved, or when the search results are enumerated. My gut feeling is that you are resolving...

Escape() has a particular nuance, it is meant to be an exact match, not specifically a phrase, however, here's a proposed change https://github.com/Shazwazza/Examine/issues/329#issuecomment-2168484838 I will close this and continue the...

@warrenbuckley So there's a few things that aren't the 'same': Firstly, in this test, neither of these queries returns any results :P The fluent query results in: `{ Category: content,...

Hi, you'll need to do some more investigating on this one to determine the underlying problem. * What happens when you only search non 'FullTextContent' fields? * What happens when...

You should also check if the fulltextsearch project specifies LuceneSearchOptions.AllowLeadingWildcard = true. If that is the case, this is most likely the cause for the performance degredation. Lucene specifically says...

I will close this issue since I don't think this is an issue with Examine but more the usage of Examine via the FullTextSearch package. As for what is an...

Hi all, I know this topic is old but will add some clarity: As @callumbwhyte notes, it creates a PhraseQuery, but this is not susceptible to the same tokenizing and...