Right. Delete by query "id:foo OR dependsOn:foo". --wunder On Nov 27, 2013, at 6:23 AM, "Jack Krupansky" <j...@basetechnology.com> wrote:
> Just bite the bullet and do the query at your application level. I mean, > Solr/Lucene would have to do the same amount of work internally anyway. If > the perceived performance overhead is too great, get beefier hardware. > > -- Jack Krupansky > > -----Original Message----- From: Thomas Scheffler > Sent: Wednesday, November 27, 2013 3:13 AM > To: SOLR User > Subject: weak documents > > 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 -- Walter Underwood wun...@wunderwood.org
