Just a guess, I haven't investigated them fully yet, but I wonder if block joins could serve you here, as they involve creating docs in a parent child relationship.
Or, you could easily fake it: <delete> <id>abcd</id> <query>parent:abcd</query> </delete> Not sure if that syntax is completely right, but using that sort of thing would get you there, For deletes, think. There isn't yet an update by query (batch update) feature, one that would be very useful. Upayavira On Wed, Nov 27, 2013, at 08:13 AM, Thomas Scheffler wrote: > Hi, > > I am relatively new to SOLR and I am looking for a neat way to implement > weak documents with SOLR. > > Whenever a document is updated or deleted all it's dependent documents > should be removed from the index. In other words they exist as long as > the document exist they refer to when they were indexed - in that > specific version. On "update" they will be indexed after their master > document. > > I could like to have some kind of "dependsOn" field that carries the > uniqueKey value of the master document. > > Can this be done efficiently with SOLR? > > I need this technique because on update and on delete I don't know how > many dependent documents exists in the SOLR index. Especially for batch > index processes, I need a more efficient way than query before every > update or delete. > > kind regards, > > Thomas
