Grant Ingersoll wrote:
A bigger question is, should LCF be responsible for this stuff or should Solr,
etc. be responsible for it? For instance, perhaps all Solr needs is to
implement a DataImportHandler processor?
Doesn't Solr also handle document conversions, pipeline, etc.?
Karl
On Mar
A bigger question is, should LCF be responsible for this stuff or should Solr,
etc. be responsible for it? For instance, perhaps all Solr needs is to
implement a DataImportHandler processor?
On Mar 3, 2010, at 1:19 PM, Karl Wright wrote:
> Erik Hatcher wrote:
>> I'm curious why the LuceneConn
Erik Hatcher wrote:
I'm curious why the LuceneConnector doesn't use the SolrJ API? Instead,
there's a custom HttpPoster class that does a lot of work that SolrJ
already handles internally.
Also, this probably should be called a SolrConnector instead, eh? Since
it's writing to Solr, not to L
I'm curious why the LuceneConnector doesn't use the SolrJ API?
Instead, there's a custom HttpPoster class that does a lot of work
that SolrJ already handles internally.
Also, this probably should be called a SolrConnector instead, eh?
Since it's writing to Solr, not to Lucene directly.
