[
https://issues.apache.org/jira/browse/NUTCH-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063375#comment-13063375
]
Markus Jelsma edited comment on NUTCH-1037 at 7/11/11 2:53 PM:
---------------------------------------------------------------
mmmmm, yes.
It would require changing existing indices for something that is not yet being
fully supported out-of-the-box by Solr. A reason for not having used payloads
as of yet. If i'm not mistaken it'll encode a byte for each term in the field,
not for the group of terms that make up an anchor, so i think that would make
things difficult, wouldn't it?
was (Author: markus17):
mmmmm, yes.
It would require changing existing indices for something that is not yet being
fully supported out-of-the-box by Solr. A reason for not having used payloads
as of yet. If i'm not mistaken it'll encode a byte for each term in the field,
not for the whole field value so i think that would make things difficult,
wouldn't it?
> Deduplicate anchors before indexing
> -----------------------------------
>
> Key: NUTCH-1037
> URL: https://issues.apache.org/jira/browse/NUTCH-1037
> Project: Nutch
> Issue Type: Improvement
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.4, 2.0
>
> Attachments: NUTCH-1037-1.4-1.patch, NUTCH-1037-2.0-1.patch
>
>
> Anchors are not deduplicated before indexing. This can result in a very high
> number of similar and identical anchors being indexed. Before indexing,
> anchors must be deduplicated at least on case.
> Should this be implemented as a fix or as a new feature that needs to be
> configured?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
