LUNA Index Module v.5.64.0#
LIM changes
-
The ability to update an existing index instead of a complete rebuild has been added.
By default, a complete index rebuild is performed. If necessary, you can update the indexes instead of rebuilding them. To save time and resources, the Index Manager service can only take into account newly added or deleted descriptors. In this case, the Indexer service will not rebuild indexes from scratch. To prioritize upgrade over rebuild, you need to set the "rebuild_rules" > "default" setting to
false
, which means "do not rebuild, but update". By default, a rebuild is performed (valuetrue
).An update involves deleting old and/or adding new descriptors from/to the created index. Due to the indexing algorithm, removing a descriptor from the created index results in degradation of the index. The more descriptors that have been removed, the worse the quality of the index, resulting in lower search accuracy for that index. It is highly recommended that you rebuild your indexes if you remove a large number of individuals from the original dataset.
To specify the number of times descriptors can be removed from index creation before the index is rebuilt from scratch, you can set the "rebuild_rules" > "max_removal_for_rebuild" parameter to an appropriate value. For example, if this setting is set to 10, it means that up to 10 descriptors can be removed before the index is rebuilt from scratch to ensure it is effective. The default is "0", which means "never rebuild from scratch". The recommended guideline for rebuilding indexes is to remove no more than 10% of the total volume of descriptors.
-
The Python version has been updated to 3.12 in LIM service containers.
Support for older versions of Python has been discontinued.
LIM fixes
-
Now when setting the schedule of scheduling procedure execution in Cron-format, the day of the week starts from Sunday.
Previously, the day of the week started on Monday.
-
Indexer service logging responsible for indexing, index update and other similar tasks has been fixed.
Previously, when changing the logging level in Configurator, the "INFO" logging level was still used for the above tasks.