This. And so much this. As much this as you can muster.
On Apr 7, 2014, at 1:49 PM, Michael Della Bitta
wrote:
> The speed of ingest via HTTP improves greatly once you do two things:
>
> 1. Batch multiple documents into a single request.
> 2. Index with multiple threads at once.
>
> Michael
The speed of ingest via HTTP improves greatly once you do two things:
1. Batch multiple documents into a single request.
2. Index with multiple threads at once.
Michael Della Bitta
Applications Developer
o: +1 646 532 3062
appinions inc.
"The Science of Influence Marketing"
18 East 41st Stre
I have to agree with Shawn. We have a SolrCloud setup with 256 shards,
~400M documents in total, with 4-way replication (so its quite a big
setup!) I had thought that HTTP would slow things down, so we recently
trialed a JNI approach (clients are C++) so we could call SolrJ and get the
benefits o
On 4/7/2014 5:52 AM, Jonathan Varsanik wrote:
Do you mean to tell me that the people on this list that are indexing 100s of
millions of documents are doing this over http? I have been using custom
Lucene code to index files, as I thought this would be faster for many
documents and I wanted so
[mailto:erik.hatc...@gmail.com]
Sent: Thursday, April 03, 2014 8:47 AM
To:solr-user@lucene.apache.org
Cc: Solr User
Subject: Re: Solr interface
Yes. But why?
DataImportHandler kinda does this (still use http to kick off an indexing job).
And there's EmbeddedSolrServer too.
Erik
On Apr 3,
On Mon, 2014-04-07 at 13:52 +0200, Jonathan Varsanik wrote:
> Do you mean to tell me that the people on this list that are indexing
> 100s of millions of documents are doing this over http?
Some of us do. Our net archive indexer runs a lot of Tika processes that
sends their analysed documents thro
a
better way?
To the OP: You can also use Lucene to locally index files for Solr.
-Original Message-
From: Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Thursday, April 03, 2014 8:47 AM
To: solr-user@lucene.apache.org
Cc: Solr User
Subject: Re: Solr interface
Yes. But why
This feels like premature optimization. Before going that route, I'd
be _very_ sure that my network speed was enough of a problem to
warrant the effort.
Now, you might have very slow networks or some other unusual setup
that justifies the effort, but it would have to be very special, there
are a _
Yes. But why?
DataImportHandler kinda does this (still use http to kick off an indexing job).
And there's EmbeddedSolrServer too.
Erik
> On Apr 3, 2014, at 8:39, Александр Вандышев wrote:
>
> Is it possible to index files not via HTTP interface?
OK, thanks for the suggestion. Why do you recommend using JSON over
simply using the built-in PHPSerializedResponseWriter?
I find using an interface that requires the data to be parsed to be
inefficient (this would include the aforementioned
PHPSerializedResponseWriter as well). Wouldn't it
If you wish to interface to Solr from PHP, and decide to go with Yonik's
suggestion to use JSON, I would suggest using
http://code.google.com/p/solr-php-client/
It has served my needs for the most part.
On Thu, Sep 16, 2010 at 1:33 PM, Yonik Seeley wrote:
> On Thu, Sep 16, 2010 at 2:30 PM, onlin
On Thu, Sep 16, 2010 at 2:30 PM, onlinespend...@gmail.com
wrote:
> I am planning on creating a website that has some SOLR search capabilities
> for the users, and was also planning on using PHP for the server-side
> scripting.
>
> My goal is to find the most efficient way to submit search queries
12 matches
Mail list logo
