[
https://issues.apache.org/jira/browse/NUTCH-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595252#comment-13595252
]
Sebastian Nagel commented on NUTCH-1047:
----------------------------------------
Hi Julien,
in overall, all looks good. A first version of the CSV indexer is ready
(NUTCH-1541) and works well with the last v5 patch.
One point we should improve is the command-line help. I agree with Tejas that
the help should list all required arguments. Of course, you are right the
index/cleaning jobs are "backend-neutral" but then it would be preferable to
have new commands "index" and "indexclean". They are also required if other
indexer back-ends are used. We can keep the "solr*" commands for legacy and
because they are handy. A few additional lines to generate the prior help text
are tolerable and could avoid unnecessary user requests on the mailing list.
The describe() method is a good idea. The new commands will then show
sufficient help but IndexingJob/CleaningJob should also call describe() when
help is shown!
Some trivialities to get the Java docs right:
* default.properties - need to add the new "plugins.indexer" group with
indexer-solr as member
* build.xml - add group referring to "plugins.indexer", add Java doc targets
for indexer-solr
> Pluggable indexing backends
> ---------------------------
>
> Key: NUTCH-1047
> URL: https://issues.apache.org/jira/browse/NUTCH-1047
> Project: Nutch
> Issue Type: New Feature
> Components: indexer
> Reporter: Julien Nioche
> Assignee: Julien Nioche
> Labels: indexing
> Fix For: 1.7
>
> Attachments: NUTCH-1047-1.x-v1.patch, NUTCH-1047-1.x-v2.patch,
> NUTCH-1047-1.x-v3.patch, NUTCH-1047-1.x-v4.patch, NUTCH-1047-1.x-v5.patch
>
>
> One possible feature would be to add a new endpoint for indexing-backends and
> make the indexing plugable. at the moment we are hardwired to SOLR - which is
> OK - but as other resources like ElasticSearch are becoming more popular it
> would be better to handle this as plugins. Not sure about the name of the
> endpoint though : we already have indexing-plugins (which are about
> generating fields sent to the backends) and moreover the backends are not
> necessarily for indexing / searching but could be just an external storage
> e.g. CouchDB. The term backend on its own would be confusing in 2.0 as this
> could be pertaining to the storage in GORA. 'indexing-backend' is the best
> name that came to my mind so far - please suggest better ones.
> We should come up with generic map/reduce jobs for indexing, deduplicating
> and cleaning and maybe add a Nutch extension point there so we can easily
> hook up indexing, cleaning and deduplicating for various backends.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
