Change warc importer to use defaultsurrogate-crawl profile, as reported

by LA_FORGE http://forum.yacy-websuche.de/viewtopic.php?f=5&t=5990 and
analysed by @luccioman (see comment 510f11d374)
it creates conflict using a other crawlprofile without setting originator.
pull/122/head
reger 8 years ago
parent 3b1d640a3c
commit 039162fbf0

@ -150,15 +150,15 @@ public class WarcImporter extends Thread implements Importer {
requestHeader.referer() == null ? null : requestHeader.referer().hash(),
"warc",
responseHeader.lastModified(),
Switchboard.getSwitchboard().crawler.defaultRemoteProfile.handle(), // use remote profile (to index text & media, without writing to cache
Switchboard.getSwitchboard().crawler.defaultSurrogateProfile.handle(),
0,
Switchboard.getSwitchboard().crawler.defaultRemoteProfile.timezoneOffset());
Switchboard.getSwitchboard().crawler.defaultSurrogateProfile.timezoneOffset());
final Response response = new Response(
request,
requestHeader,
responseHeader,
Switchboard.getSwitchboard().crawler.defaultRemoteProfile,
Switchboard.getSwitchboard().crawler.defaultSurrogateProfile,
false,
content
);

Loading…
Cancel
Save