Hi all,

I would like to partition my data (by date for example) into Solr Cores by 
implement some sort of *pluggable component* for Solr.
In other words, I want Solr to handle distribution to partitions (rather than 
implementing an external "solr proxy" for sending requests to the right Solr 
Core).

Initially I thought that DistributedUpdateProcessor may help here but, as I 
understood, it is not intended for partitioning into Cores but rather into 
shard across several machines. In addition, one cannot control the logic by 
which distribution is done.
I thought about implementing an UpdateRequestProcessor that forwards document 
updates to the right Cores (DistributedUpdateProcessor), yet I want to check 
with you (all Solr users out there) if this can be avoided by doing it 
differently.

In other words, is there any other way of implementing a pluggable component 
for Solr that can forward/route updates (using predefined logic) to Cores?
Is there, for instance, a way to catch an update request before it enters the 
update-request processor-chain?

Thanks,

Shahar.

Reply via email to