We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DATE element type allows user to override the NeighborhoodRange , but a value of greater than 0.91 causes poor matches to show up.
This is a test case to trigger it in MatchServiceTest.java that can show the failure
MatchServiceTest.java
@Test public void itShouldApplyMatchWithDate() { List<Object> dates = Arrays.asList(getDate("01/01/2020"), getDate("01/02/2020"), getDate("07/15/2019")); List<Document> documentList = getTestDocuments(dates, DATE, 0.91); Map<Document, List<Match<Document>>> result = matchService.applyMatch(documentList); result.entrySet().forEach(entry -> { entry.getValue().forEach(match -> { System.out.println("Data: " + match.getData() + " Matched With: " + match.getMatchedWith() + " Score: " + match.getScore().getResult()); }); }); Assert.assertEquals(2, result.size()); }
As we increate the value greater than 0.91, dates that are not in the neighborhood shows up in results.
The issue is primarily in the incorrect usage of this
fuzzy-matcher/src/main/java/com/intuit/fuzzymatcher/component/TokenRepo.java
Line 89 in d2ce6f6
It is increasing the TokenRanges lower and higher bounds to broader values, causing incorrect matches to show up.
The text was updated successfully, but these errors were encountered:
Hi! I would like to take on this bug! Please assign.
Thank you!
Sorry, something went wrong.
intuit#35 fix DateMatch with NeighborhoodRange greater than 0.91 failing
5439fae
0b35c27
Merge pull request #39 from aavaas/master
8c026c1
#35 fix DateMatch with NeighborhoodRange greater than 0.91 failing
No branches or pull requests
DATE element type allows user to override the NeighborhoodRange , but a value of greater than 0.91 causes poor matches to show up.
This is a test case to trigger it in
MatchServiceTest.java
that can show the failureAs we increate the value greater than 0.91, dates that are not in the neighborhood shows up in results.
The issue is primarily in the incorrect usage of this
fuzzy-matcher/src/main/java/com/intuit/fuzzymatcher/component/TokenRepo.java
Line 89 in d2ce6f6
It is increasing the TokenRanges lower and higher bounds to broader values, causing incorrect matches to show up.
The text was updated successfully, but these errors were encountered: