You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Ahmet Arslan <io...@yahoo.com> on 2012/08/31 20:53:13 UTC

LineEntityProcessor process only one file

LineEntityProcessor processes only one document when combined with FileListEntityProcessor. Is this by design?



Re: LineEntityProcessor process only one file

Posted by Lance Norskog <go...@gmail.com>.
Ahmet, please post your dih script in a message (not as an attachment).

----- Original Message -----
| From: "James Dyer" <Ja...@ingramcontent.com>
| To: solr-user@lucene.apache.org
| Sent: Friday, August 31, 2012 12:53:50 PM
| Subject: RE: LineEntityProcessor process only one file
| 
| No, it should process all of the files that get listed.  I'm taking a
| look at the issue you opened, SOLR-3779.  This is also similar to
| SOLR-3307, although that was reported as a bug with "threads" in
| 3.6, which is no longer a feature in 4.0.
| 
| James Dyer
| E-Commerce Systems
| Ingram Content Group
| (615) 213-4311
| 
| 
| -----Original Message-----
| From: Ahmet Arslan [mailto:iorixxx@yahoo.com]
| Sent: Friday, August 31, 2012 1:53 PM
| To: solr-user@lucene.apache.org
| Subject: LineEntityProcessor process only one file
| 
| LineEntityProcessor processes only one document when combined with
| FileListEntityProcessor. Is this by design?
| 
| 
| 
| 
| 

RE: LineEntityProcessor process only one file

Posted by "Dyer, James" <Ja...@ingramcontent.com>.
No, it should process all of the files that get listed.  I'm taking a look at the issue you opened, SOLR-3779.  This is also similar to SOLR-3307, although that was reported as a bug with "threads" in 3.6, which is no longer a feature in 4.0.

James Dyer
E-Commerce Systems
Ingram Content Group
(615) 213-4311


-----Original Message-----
From: Ahmet Arslan [mailto:iorixxx@yahoo.com] 
Sent: Friday, August 31, 2012 1:53 PM
To: solr-user@lucene.apache.org
Subject: LineEntityProcessor process only one file

LineEntityProcessor processes only one document when combined with FileListEntityProcessor. Is this by design?