Hello,
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.
Best regards, Ivan Lagunov
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
Dear Christian,
Ok. However, it doesn't seem comfortable to me that I'll have to execute optimize now after every update/delete operation. Is there any estimated date when incremental index updates will be ready?
Best regards, Ivan Lagunov
On 10/26/2010 05:46 PM, Christian Grün 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 Lagunovilagunov@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
Ok. However, it doesn't seem comfortable to me that I'll have to execute optimize now after every update/delete operation. Is there any estimated date when incremental index updates will be ready?
Sorry – not really, as our resources are limited. We'll soon offer the priorized (but paid) integration of new features, if that helps.
Christian
On 10/26/2010 05:46 PM, Christian Grün 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 Lagunovilagunov@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
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.comwrote:
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
Hi Jan,
Ok, I've checked what you ask about.
Question1 - the optimize function recreates complete index (takes the same 7 seconds every time via GUI and 5 seconds via terminal client). Question2 - it affects query performance a lot as if index isn't used any more at all.
I completely agree with your remark. And it'd be great to have optional setting of automatic incremental index.
Best regards, Ivan
On 10/26/2010 06:06 PM, Jan Vlčinský (CAD) wrote:
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 mailto: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 <mailto:ilagunov@evelopers.com>> wrote: > Hello, > > > Best regards, > Ivan Lagunov > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk@mailman.uni-konstanz.de <mailto: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 <mailto: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 mailto:jan.vlcinsky@gmail.com http://cz.linkedin.com/in/vlcinsky
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Ivan Lagunov -
Jan Vlčinský (CAD)