lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SOLR-676) DataImportHandler should use UpdateRequestProcessor API
Date Sat, 09 Aug 2008 17:54:44 GMT

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

Shalin Shekhar Mangar resolved SOLR-676.
----------------------------------------

    Resolution: Fixed

Committed revision 684307.

> DataImportHandler should use UpdateRequestProcessor API
> -------------------------------------------------------
>
>                 Key: SOLR-676
>                 URL: https://issues.apache.org/jira/browse/SOLR-676
>             Project: Solr
>          Issue Type: Bug
>          Components: contrib - DataImportHandler
>    Affects Versions: 1.3
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 1.3
>
>         Attachments: SOLR-676.patch
>
>
> Refer to Patrick's comment on SOLR-469 at https://issues.apache.org/jira/browse/SOLR-469?focusedCommentId=12604276#action_12604276
and report by Tom at http://www.nabble.com/localsolr-and-dataimport-problems-tp18849983p18849983.html
> DataImportHandler directly uses the core.getUpdateHandler (DirectUpdateHandler2) instead
of going through the UpdateRequestProcessor API. This makes it impossible to utilize update
processors with DataImportHandler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message