Related feature request and (hackish) solution until this feature is implemented:

I think these use cases are very reasonable so I'll optimistically schedule this to be done for version 5.1
Thanks for reminding of this old issue!

I need to be able to do this too...I have a process that runs and sometimes I do a bulk insert and I need the insert to run quickly and then do the mass indexing later but under normal circumstances I want the event indexing to take place. The Event based indexing is causing my bulk insert to take a lot longer so if I could turn it off programmatically and then reenable it later, it would be extremely useful.

I found this issue while searching for a way to temporarily disable the indexing. My use case is that the app can generate test data itself at startup when needed. Transparent indexing dramatically slows down this process as batch updates cannot be used during this process (hierarchies are being created). The app also does a partial, manual re-indexing of changed entities since the app was last stopped to catch external updates to the database while it was down.

I would really much like the ability to disable transparent indexing while my test dataset is being generated. Thereafter, the partial re-indexing will occur and batch index these new entities.

Thank you for this great piece of software.

You will need to give me good use cases for both per index indexing and programmatic indexing.
There are strong reasons why this is not the case today.