[
https://issues.apache.org/jira/browse/NUTCH-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18131872#comment-18131872
]
ASF GitHub Bot commented on NUTCH-2455:
---------------------------------------
github-actions[bot] commented on PR #888:
URL: https://github.com/apache/nutch/pull/888#issuecomment-6398812914
<table><tr><th></th><th>Tests</th><th>Passed
✅</th><th>Skipped</th><th>Failed</th><th>Time ⏱</th></tr><tr><td>JUnit Test
Report</td><td>222 ran</td><td>222 passed</td><td>0 skipped</td><td>0
failed</td><td>2m 39s 849ms</td></tr></table>
<table><tr><th>Test</th><th>Result</th><th>Time ⏱</th></tr><tr><td
colspan="3">No test annotations available</td></tr></table><ul><li><a
href="https://github.com/apache/nutch/runs/121194675705";>View JUnit Test
Report</a></li></ul>
<!
> Use secondary sorting for memory-efficient HostDb integration in Generator
> --------------------------------------------------------------------------
>
> Key: NUTCH-2455
> URL: https://issues.apache.org/jira/browse/NUTCH-2455
> Project: Nutch
> Issue Type: Improvement
> Components: generator
> Affects Versions: 1.13
> Reporter: Markus Jelsma
> Assignee: Lewis John McGibbney
> Priority: Major
> Fix For: 1.24
>
> Attachments: NUTCH-2455.patch
>
>
> Citing Sebastian at NUTCH-2420:
> ??The correct solution would be to use <host,score> pairs as keys in the
> Selector job, with a partitioner and secondary sorting so that all keys with
> same host end up in the same call of the reducer. If values can also hold a
> HostDb entry and the sort comparator guarantees that the HostDb entry
> (entries if partitioned by domain or IP) comes in front of all CrawlDb
> entries. But that would be a substantial improvement...??
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
