nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Nioche (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NUTCH-1047) Pluggable indexing backends
Date Thu, 10 Jan 2013 16:46:13 GMT

     [ https://issues.apache.org/jira/browse/NUTCH-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Julien Nioche updated NUTCH-1047:
---------------------------------

    Attachment: NUTCH-1047-1.x-v1.patch

This is work in progress.
This patch creates a new endpoint (IndexWriter) that plugins can implement. Comes with one
such plugin (indexer-solr) and generic code for replacing the index and delete jobs. Haven't
tested very much. The main difference is that the SOLR URL must be passed as a Hadoop param
e.g. -D solr.server.url. It could also be put in the nutch-site.xml once and for all. 
There will be some cleaning to do once this is stable to remove the SOLR stuff in the core
code etc...
Please have a look and let me know your thoughts on this
                
> 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
>
>
> 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

Mime
View raw message