You can also use $deleteDocById . If you also use $skipDoc, you can sometimes get the deletes on the same entity with a "command=full-import&clean=false" delta. This may or may not be more convienent that what you're doing already. See http://wiki.apache.org/solr/DataImportHandler#Special_Commands .
James Dyer E-Commerce Systems Ingram Content Group (615) 213-4311 -----Original Message----- From: janne mattila [mailto:jannepostilis...@gmail.com] Sent: Thursday, March 29, 2012 12:45 AM To: solr-user@lucene.apache.org Subject: Re: dataImportHandler: delta query fetching data, not just ids? > I'm not sure why deltas were implemented this way. Possibly it was designed > to behave like some of our object-to-relational libraries? In any case, > there are 2 ways to do deltas and you just have to take your pick based on > what will work best for your situation. I wouldn't consider the > "command=full-import&clean=false" method a workaround but just a different > way to tackle the same problem. Yeah, I find the delta-update strategy a little strange as well. Problem with command=full-import&clean=false is that you can't handle removes nicely using that. If you use the actual delta-import and deletedPkQuery for that, you run into problems with last_index_time and miss either modifications or deletes. I'm handling that by creating a different entity config for updates (using command=full-import&clean=false) and deletes (using command=delta-import) but it ends up being much dirtier than it should be.
