I'd separate the splitting of the binary documents from the sharding in Solr - they're different things and the split may be required at different levels, due to different numbers of documents.
Splitting the dependency means that you can store the path in the document and not need to infer anything, and you can re-organise the Solr shards without having to worry about moving the binary documents around. Also, if you think you're going to need to change Jan to Jan2011, then maybe you should just start with Jan2011. Alternatively, considering that you think change is likely in the future, why not name the directories in such a way that you don't need to make the change earlier ones as the requirement to change the structures arises? Does that make sense? Rob On Tue, Mar 22, 2011 at 3:20 PM, JohnRodey <timothydd...@yahoo.com> wrote: > I have an issue and I'm wondering if there is an easy way around it > with just SOLR. > > I have multiple SOLR servers and a field in my schema is a relative > path to a binary file. Each SOLR server is responsible for a > different subset of data that belongs to a different base path. > > For Example... > > My directory structure may look like this: > /someDir/Jan/binaryfiles/... > /someDir/Feb/binaryfiles/... > /someDir/Mar/binaryfiles/... > /someDir/Apr/binaryfiles/... > > Server1 is responsible for Jan, Server2 for Feb, etc... > > And a response document may have a field like this my entry > binaryfiles/12345.bin > > How can I tell from my main search server which server returned a result? > I cannot put the full path in the index because my path structure > might change in the future. Using this example it may go to > '/someDir/Jan2011/'. > > I basically need to find a way to say 'Ah! server01 returned this > result, so it must be in /someDir/Jan' > > Thanks! > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Architecture-question-about-solr-sh > arding-tp2716417p2716417.html Sent from the Solr - User mailing list > archive at Nabble.com. > This email transmission is confidential and intended solely for the addressee. If you are not the intended addressee, you must not disclose, copy or distribute the contents of this transmission. If you have received this transmission in error, please notify the sender immediately. http://www.sthree.com
