[
https://issues.apache.org/jira/browse/NUTCH-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582163#comment-13582163
]
Tejas Patil commented on NUTCH-1047:
------------------------------------
Hey Julien,
While running the solrclean command, I followed the old usage given here [0].
It gave an exception. Then I saw the usage and it gave
{noformat}$ bin/nutch solrclean
Usage: CleaningJob <crawldb> [-noCommit]{noformat}
That did not work too. It just prints the usage if only the crawldb is passed
as an argument. I went through the patch and realized that the bin/nutch script
considers the first argument as the solr url and then the left over ie. the
crawldb is passed to the java code. This is what worked for me:
{noformat}bin/nutch solrclean <solrurl> <crawldb>{noformat}
This is different from the old usage given at [0]. We can prevent from changing
the ordering of the arguments and preserve the old usage. This can be used in
bin/nutch script:
{noformat}CLASS="org.apache.nutch.indexer.CleaningJob -D
solr.server.url=$2"{noformat} and not perform a "shift" after that.
Corresponding usage must be modified in the java code too.
[0] : http://wiki.apache.org/nutch/bin/nutch%20solrclean
> 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
