While training a Gazetteer on data with a person field and no other name field, I noticed that predicates like PartialIndexLevenshteinSearchPredicate: (3, best_looking_name, CorporationName) were wrongly generated as well as the expected PartialIndexLevenshteinSearchPredicate: (3, best_looking_name, Surname).
This happens because block_parts were not properly set when initialization of the WesternNameType depending on the WesternNameType.name_type
Changes
Fixed
when initializing WesternNameType, appropriately set the block_parts depending on the WesternNameType.name_type before calling the parent ParseratorType.__init__
Bug description
While training a
Gazetteeron data with apersonfield and no other name field, I noticed that predicates likePartialIndexLevenshteinSearchPredicate: (3, best_looking_name, CorporationName)were wrongly generated as well as the expectedPartialIndexLevenshteinSearchPredicate: (3, best_looking_name, Surname).This happens because
block_partswere not properly set when initialization of theWesternNameTypedepending on theWesternNameType.name_typeChanges
Fixed
WesternNameType, appropriately set theblock_partsdepending on theWesternNameType.name_typebefore calling the parentParseratorType.__init__