Dear Wiki user, You have subscribed to a wiki page or wiki category on "Nutch Wiki" for change notification.
The "ThirdReport" page has been changed by LewisJohnMcgibbney: https://wiki.apache.org/nutch/ThirdReport?action=diff&rev1=11&rev2=12 == Review of Previous Actions == + * Change entire build structure to Ant + Ivy as per existing 2.x codebase + * Implement seed information upload using REST API + * Create embedded database for storing crawls, user credentials, and so on + * Write tests and some documentation/javadoc == Objectives == - == Change build structure to Ant + Ivy== + === Change build structure to Ant + Ivy === + Project has been switched to Ant + Ivy build system and integrated into 2.x codebase. There were some issues concerning this move. One of them was library dependencies, for example nutch is tightly coupled with hbase and hadoop, and they are dependent from outdated jersey and jetty. So, I downgraded dependencies of my project and had rewritten relevant parts of application. === Add instances management === The main issue concerning this objective were implementation of connection status checks. I'd done it with a constant polling of nutch API servers. But what application should to do, if nutch server is going down? === Logs by REST API === + Ability to get logs is very important in order to understand exceptional situations. However, I would propose to implement additional API point, which can answer, if connection with hbase and indexing server is established, because for now, it is not that easy to understand, if something is going wrong and recover from exceptional situation. === Fix seed management UI layout === + UI of seed management component is not that good, we should decide how to improve it. For example, ability to add url regex filters would be nice. === Add some security support ===
