Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <545282715.1252329300325.JavaMail.jira@brutus>
Date: Mon, 7 Sep 2009 06:15:00 -0700 (PDT)
From: "Shalin Shekhar Mangar (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Resolved: (SOLR-1406) Refactor FileDataSource and
 FileListEntityProcessor to be more extensible
In-Reply-To: <1763394013.1251931002877.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Shalin Shekhar Mangar resolved SOLR-1406.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4
         Assignee: Shalin Shekhar Mangar  (was: Noble Paul)

Committed revision 812122.

Thanks Luke!

> Refactor FileDataSource and FileListEntityProcessor to be more extensible
> -------------------------------------------------------------------------
>
>                 Key: SOLR-1406
>                 URL: https://issues.apache.org/jira/browse/SOLR-1406
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - DataImportHandler
>    Affects Versions: 1.4
>            Reporter: Luke Forehand
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 1.4
>
>         Attachments: SOLR-1406.patch, SOLR-1406.patch, SOLR-1406.patch
>
>
> FileDataSource should make openStream method protected so we can extend FileDataSource for other File types such as GZip, by controlling the underlying InputStreamReader implementation being returned.
> FileListEntityProcessor needs to aggregate a list of files that were processed and expose that list in an accessible way so that further processing on that file list can be done in the close method.  For example, deletion or archiving.
> Another improvement would be that in the event of an indexing rollback event, processing of the close method either does not occur, or the close method is allowed access to that event, to prevent processing within the close method if necessary.

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