Hi Aleksandra
sorry, forgot to get back to you after the 20.0 release...
> On 2. Aug 2021, at 12:32,
alek...@gmail.com wrote:
>
> Do you think that the number of documents in our project could cause the problem with indexing? The problematic project currently has almost 11k documents. The whole inception database contains about 27k documents. After the search failed due to indexing again I started rebuilding the index, then waited for 40 minutes and tried unsuccessfully to search again (the indexing is still in progress). How long should it take?
>
> Or could the indexing problem be caused by adding more features to existing layers? That does not make sense to me, but it is the only recent modification I can think of besides adding a very few more documents. No recommenders or knowledge bases are currently used.
>
> Maybe you do have any more idea what could cause the problem?
I cannot really say how long the indexing will take in your case, but I expect it could indeed take a very long time.
That said, in order to get some insight on your case, I added a functionality in INCEpTION 20.0 which gives you
feedback about the indexing process. When you try a search and it is cancelled because indexing is in progress,
the message will now say how many documents have already been indexed and how many are to be indexed in total.
While it doesn't make an estimate how much time indexing will take in total, it will at least give you a progress
indication. I hope that will help you a bit further in this case.
So please try INCEpTION 20.0. Mind that the new version makes changes to the database scheme so that you cannot switch
back to 0.19.7 after you have started 20.0. It is always a good idea to keep disk/DB backups and/or regularly export
projects in order to have backups of them.
Best,
-- Richard