>>>>> Of course introducing the idea of updates also introduces the notion of a >>>>> primary key and there's probably an entirely separate discussion to be had >>>>> around user-supplied vs Lucene-generated keys. >>>> Not sure I see that need. Can you explain your reasoning a bit more? >>> If you want to update a document you need a way of expressing *which* >>> document you are updating. >> This already works somehow for 'deleting' documents? > Yes, the convention being user-supplied keys. I can delete by lucene-generated docId. It's too volatile to be database-style PK, but nonetheless.
> The question posed is if we add another use case where keys are required do > we want to turn this existing informal convention > into more formalized support the way databases do eg duplicate key checks on > insert, auto-inc primary key generators. If someone needs this, it can be built over lucene, without introducing it as a core feature and needlessly complicating things. -- Kirill Zakharenko/Кирилл Захаренко (ear...@gmail.com) Home / Mobile: +7 (495) 683-567-4 / +7 (903) 5-888-423 ICQ: 104465785 --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
