U4-4576 - 7.0.4 : InternalMemberSearcher config incorrectly uses 'enableLeadingWildcards', should be 'enableLeadingWildcard'

Created by John Masson 01 Apr 2014, 07:20:03 Updated by Sebastiaan Janssen 01 Apr 2014, 09:55:13

In the default config/ExamineSettings.config, the element for InternalMemberSearcher has 'enableLeadingWildcards="true"', but the attribute that BaseLuceneSearcher looks for is called 'enableLeadingWildcard' (singular).

1 Attachments


Sebastiaan Janssen 01 Apr 2014, 08:41:58

I don't think this is an actual problem as only the value (a boolean) is passed on to Lucene, not the actual attribute name. @Shandem will be able to confirm for sure.

Sebastiaan Janssen 01 Apr 2014, 08:42:46

Never mind, I was correct, found it, see attachment.

John Masson 01 Apr 2014, 08:54:14

If you test it in the backend, searches with leading wildcards fail with an error, and BaseLuceneSearcher.Initialize contains the lines:

		if (config["enableLeadingWildcard"] != null)
			this.EnableLeadingWildcards = bool.Parse(config["enableLeadingWildcard"]);

this.EnableLeadingWildcards is then passed to Lucene when the criteria is constructed, as you point out.

To be clear, the bug I am reporting is that the configuration files are wrong as shipped, not that the code is in error.

Unless you mean you've already fixed this in a later version, in which case, ignore me :-).

Sebastiaan Janssen 01 Apr 2014, 09:07:48

Aha! Absolutely correct. :-) Jumped to conclusions too quickly, thanks!

Sebastiaan Janssen 01 Apr 2014, 09:55:00

Fixed in 15aa6fc4b821861bdb364b85e016c499473d408a & 41e8a9ef2d03dd56fb196c6e086e6a14db000775

Priority: Normal

Type: Bug

State: Fixed


Difficulty: Normal


Backwards Compatible: True

Fix Submitted:

Affected versions: 7.0.4

Due in version: 7.1.0, 6.2.0


Story Points: