You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (Jira)" <ji...@apache.org> on 2019/09/27 14:53:00 UTC
[jira] [Updated] (NUTCH-2381) In some situations the class
TextProfileSignature gives different signatures for the same text "profile"
page.
[ https://issues.apache.org/jira/browse/NUTCH-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Nagel updated NUTCH-2381:
-----------------------------------
Labels: patch-available signature (was: signature)
> In some situations the class TextProfileSignature gives different signatures for the same text "profile" page.
> --------------------------------------------------------------------------------------------------------------
>
> Key: NUTCH-2381
> URL: https://issues.apache.org/jira/browse/NUTCH-2381
> Project: Nutch
> Issue Type: Bug
> Components: crawldb
> Affects Versions: 1.13
> Reporter: Rodrigo Joni Sestari
> Assignee: Sebastian Nagel
> Priority: Major
> Labels: patch-available, signature
> Fix For: 1.16
>
>
> In some situations the class TextProfileSignature gives different signatures for the same text "profile" page.
> The method TextProfileSignature.calculate uses a HashMap to salve the tokens, after some process, the tokens come sorted by decreasing frequency.
> For some pages like "http://curia.europa.eu/jcms/" the text "profile" is the same but the signature come different for each fetch.
> Its happens because the tokens are sorted only by decreasing frequency. Tokens with the same frequency maybe not have the same order in different fetchs.
> The HashMap no guarantees as to the order of the map and not guarantee that the order will remain constant over time.
> My suggestion is change the methods TokenComparator.compare in order to sort by frequency and Name.
> Rodrigo
--
This message was sent by Atlassian Jira
(v8.3.4#803005)