Skip to content

Releases: intuit/fuzzy-matcher

Security fixes and minor updates

03 Aug 23:43
Compare
Choose a tag to compare
  • Security fix for cve vulnerabilities
  • Minor fixes for error logging and slf4j logging
  • improved test coverage for custom tokenizers

Java 11 support

18 Oct 20:30
Compare
Choose a tag to compare
  • Support for Java 11
  • Significant improvement in memory footprint

Support to Chain multiple tokens

18 Oct 19:39
Compare
Choose a tag to compare
  • Support for chaining multiple Tokenizers using chainTokenizers function #54

Date Range Fixes

12 Oct 21:02
Compare
Choose a tag to compare
  • DateMatch with NeighborhoodRange greater than 0.9 #35
  • Security fixes and updates on dependent libraries

Support for AGE ElementType

09 Nov 19:52
Compare
Choose a tag to compare
  • Support for AGE ElementType
  • Security fixes and updates on dependent libraries

Support for Grouping Matches

14 Apr 20:04
Compare
Choose a tag to compare
  • New service method to return groups of Matches E.g. A matches with B and B with C, all of them appear in the same group (set of matches)
  • Generic support for Tokens
  • Enhanced support for jnbridge proxies
  • NEAREST_NEIGHBORS match type miscellaneous fixes

1.0 Release

25 Mar 18:07
81d7b61
Compare
Choose a tag to compare
  • Significant Performance increase from 0.x version. Provides a linear cost for most types of data
  • From earlier version we can see at least 4X improvements in response times for match
  • Reduces memory usage to more than 1/2 from earlier version
  • Replaces configuration of SimilarityMatchFunction and MatchOptimizerFunction in Element to a more simplified MatchType and provides performance guarantees
  • NUMBER and DATE types are now matched using Nearest Neighbor algorithm
  • Element is now a Generic, to allow support for wider range of Data Types in the future

Memory Optimization

26 Dec 17:22
Compare
Choose a tag to compare
  • Improved memory utilization by processing all elements by it's type or classification. This allows jvm to run gc to free heap space after each element type is processed
  • Ability to configure scoring function in Element #19

Reducing memory usage

09 Aug 21:37
Compare
Choose a tag to compare
  • ScoringFunction changed to BiFunction from Function. It takes a List of childScores as the second input. This allows childScores to be stored in function stack when score is evaluated instead of the heap, and reduces the overall memory footprint of the library
  • Element.Builder.setValue overridden to accept Object Type
  • Match.childScores is dropped to reduce memory footprint.

Memory management

03 Jul 17:53
Compare
Choose a tag to compare

Reduced memory footprint by removing tokens not meeting match threshold