Doğacan Güney wrote: >> >> I actually think that the endless adding of configuration options does >> not do any good to anyone, we should instead start to write reusable >> pieces of code and/or bring the number of different options down >> (<imo>The massive number of already available configuration/runtime >> options and the fact that most of nutch is not designed to be extended >> by coding is harmful for advanced users. In the other hand I think that >> things are already too complicated for novice users</imo>) > > OK, adding new configuration options all the time is probably not a > great idea. But I strongly believe that indexing to different targets > should be done in Indexer.OutputFormat (OutputFormat outputs to > different targets, makes sense to me :). For example, I would love the > ability to index to solr but I would also need to store the original > lucene index in DFS (so that if solr machine dies, I don't lose my > index). I shouldn't have to run Indexer twice to achieve this.
In one application I added extension point for different indexing backends, that way by implementing a composite index backend you could achieve that same thing. The code shown in blog post was mainly done simplicity in mind, other motivation was doing it without touching Nutch source code. -- Sami Siren ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nutch-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-general
