Hi Ivan I am currently planning to implement solution, which will insert new documents each minute. Question1: does the optimize recreate complete index, or it only does some small update? Question2: if the index becomes invalid after insertion of new document, how does it affect query performance? A bit? or possibly a lot? There are scenarios, like bulk updates, when it is established practice even in SQL world to switch off indices, import/update data and then rebuild the index. However, rebuilding index once a minute seems as something, what I would like not to do, if it would take too much time. Jan On Tue, Oct 26, 2010 at 3:46 PM, Christian Grün <christian.gruen@gmail.com>wrote:
Dear Ivan,
Is it the correct behavior that indexes are automatically removed when I remove a document from a collection (version 6.3)? I mean text and attribute indexes, I haven't tried full-text index.
Yes, that was one more deliberate design decision to make updates as fast as possible in BaseX. The indexes are rebuilt whenever the "optimize" command is called; even so, tests with different systems have shown that our solution is often superior to implementations that refresh the index after each update operation. Still, one of our team members is currently integrating incremental index updates, which will be offered as an optional feature.
Christian
On Mon, Oct 25, 2010 at 4:26 PM, Ivan Lagunov <ilagunov@evelopers.com> wrote:
Hello,
Best regards, Ivan Lagunov
_______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
_______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
-- *Ing. Jan Vlčinský* CAD programy Slunečnicová 338/3, 734 01 Karviná Ráj, Czech Republic tel: +420-597 602 024; mob: +420-608 979 040 skype: janvlcinsky; GoogleTalk: jan.vlcinsky@gmail.com http://cz.linkedin.com/in/vlcinsky