On 2/12/13 3:58 AM, Erick Erickson wrote:
It'd make it interest ing to put things in the transaction log I
suspect, but I also suspect that's a solvable problem.
So the idea would be that the doc gets analyzed on the node that
receives it? Otherwise all the analysis would go on on the
It'd make it interest ing to put things in the transaction log I suspect,
but I also suspect that's a solvable problem.
So the idea would be that the doc gets analyzed on the node that receives
it? Otherwise all the analysis would go on on the leader
On Mon, Feb 11, 2013 at 2:14 AM, Otis
Otis,
It reminds me https://issues.apache.org/jira/browse/SOLR-1535 How do they
match?
On Mon, Feb 11, 2013 at 8:23 AM, Otis Gospodnetic
otis.gospodne...@gmail.com wrote:
Hi,
When a doc is pushed into SolrCloud it is sent to all shard's replicas for
analysis and indexing, right?
Yeah, something like that :)
Is that used in SolrCloud when sending docs to replicas to avoid all
replicas having to do the exact same analysis?
Otis
--
http://sematext.com/
On Feb 11, 2013 1:51 AM, Mikhail Khludnev mkhlud...@griddynamics.com
wrote:
Otis,
It reminds me
Nope, as far as I know.
Even that field type work itself, I suppose it's not a piece of cake to
marry it with SolrCloud.
How much an additional software complexity and development efforts you'd
spend for that CPU gain? Is it really sensible for you? How big your
replication factor (or quantor) ?
I don't have a problem looking to fix with that. It just occurred to me
that avoiding double/triple work might be nice.
Otis
--
http://sematext.com/
On Feb 11, 2013 2:12 AM, Mikhail Khludnev mkhlud...@griddynamics.com
wrote:
Nope, as far as I know.
Even that field type work itself, I suppose
