Even if it's not strictly needed anymore, could it improve performance? Right now I need to use commit() right after this dual operation to make sure no reader is ever going to miss it, but if it was atomic I could have avoided the commit and just trust that "at some time later" it will be auto-committed: exact moment would be out of my control, but even so the view on index wouldn't have a chance to miss some documents.
Regards, Sanne On Sun, Jan 10, 2010 at 10:04 PM, Michael McCandless <[email protected]> wrote: > I think there no particular demand... > > But: why not just separately delete by query, then add? > > Back when IW had autoCommit=true, it was compelling to have an atomic > update, but now with only autoCommit=false, the app has full control > over visibility to readers, so do we even need update-by-term anymore? > > Mike > > On Sun, Jan 10, 2010 at 2:13 PM, Sanne Grinovero > <[email protected]> wrote: >> If the demand is the problem: >> I would really love that: in most scenarios a single term is not >> enough to identify a Document: I need at least two so I use usually >> remove-by-query first and then add again. >> This sometimes needs some application level lock to make the changes >> consistent. >> >> Sanne >> >> 2010/1/10 Mark Miller <[email protected]>: >>> Any reason we don't offer update doc by query along with term? >>> >>> Its easy enough to implement in the same manner - is there some sort of >>> gotchya with this, or is it just because there has been no demand yet? >>> >>> -- >>> - Mark >>> >>> http://www.lucidimagination.com >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sanne Grinovero http://in.relation.to/Bloggers/Sanne Sourcesense - making sense of Open Source: http://www.sourcesense.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
