This improves the way Nutch is erroring out, at least for local mode.#830
This improves the way Nutch is erroring out, at least for local mode.#830HiranChaudhuri wants to merge 1 commit intoapache:masterfrom
Conversation
| curTime = conf.getLong("injector.current.time", | ||
| System.currentTimeMillis()); | ||
| url404Purging = conf.getBoolean(CrawlDb.CRAWLDB_PURGE_404, false); | ||
| } catch (Exception e) { |
There was a problem hiding this comment.
Exception is very vague. I would suggest we figure out what types of Exception's are thrown then catch and raise them instead. What do you think @HiranChaudhuri ?
There was a problem hiding this comment.
I would not know how to define what types of Exceptions can be thrown. Be aware that logging needs to happen for checked and unchecked exceptions. And be aware you cannot see all the code: It loads plugins. Your catch method needs to be compatible to all existing and future code.
So I do not know how to make the catch block any more concise than it is right now. If you can, please show me.
|
This issue is stale and has a conflict. I'm going to close it. If you are interested in updating it please let us know. Thank you @HiranChaudhuri |
2 participants
Nutch will print more information to the logfile - which in local mode ends up on the terminal.
Not sure what will happen in distributed mode though.