Skip to content

Fix Fuzzy Match algorithm dropdown and distance measure type - #7842

Merged
hansva merged 2 commits into
apache:mainfrom
leehaut:hotfix/lance-common-112
Aug 7, 2026
Merged

Fix Fuzzy Match algorithm dropdown and distance measure type#7842
hansva merged 2 commits into
apache:mainfrom
leehaut:hotfix/lance-common-112

Conversation

@leehaut

@leehaut leehaut commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Exclude the empty NONE option from the Fuzzy Match algorithm dropdown so the first selectable row is a real algorithm.
  • Declare the measure value field as Integer for Damerau-Levenshtein and Needleman-Wunsch (same as Levenshtein), matching the Long distance written at runtime and avoiding the Long vs String type error when storing execution data.
2026/08/07 22:25:14 - demo_fuzzymatch - measure value String : There was a data type error: the data type of java.lang.Long object [5] does not correspond to value meta [String] (through reference chain: org.apache.hop.execution.ExecutionData["rowsBinaryGzipBase64Encoded"])
  • Simplify FuzzyMatchMeta (including Algorithm and FMLookupValue) with Lombok @Getter / @Setter.
  • Add a unit test asserting distance algorithms expose an Integer measure field.

@hansva
hansva merged commit 9cecdfd into apache:main Aug 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants