Skip to content

LUNA PLATFORM v.5.6.0#

Changes

  • SDK was updated to version 5.2.0.

  • The support for the 59 neural network version for the face descriptors extraction was added.

    Starting from build 5.6.0, the 59 version is used by default for new LP installations.

    If LP is already installed, the default neural network version will not be updated to 59 automatically. The currently used neural network version will remain in the Configurator service. In this case, it is required to perform re-extraction of the already existing face descriptors to update to the new neural network. The process description is given in the "Switch neural network version" section of the administrator's manual.

    Note that re-extraction of events descriptors is not available. When switching to a new neural network, existing events cannot be used for matching operations.

    The distribution of Index building and searching by index does not support the 59 neural network version. The neural network of version 56 is used by default for these services.

  • The support for 102, 103, and 104 neural networks for the body descriptors extraction was added. The 104 version is now used by default.

    The neural network of version 101 that was used in the previous releases is not supplied and is not supported anymore. The already existing body descriptors cannot be re-extracted using the 104 neural network version when switching to LP build 5.6.0, and they cannot be used for matching operations.

  • The "user_data" and "external_id" parameters values are now set to " " by default for all the services and cannot be set to null.

  • The "event_id__gte" and "event_id__lt" filters were added to the "Cross-match", "Clustering", and "Linker tasks". The filters enable you to set the upper and lower bounds for the "event_id" parameter values. The subsequent processing will be performed only for the events whose IDs are included in the range specified by the filter. They can be used, for example, to divide events processing into several tasks and perform them in parallel.

  • The configuration reload mechanics have changed in Image Store, Tasks, Events, Admin, and Backport 3 services. Now, it's done mostly by restarting appropriate processes. The mechanism provides a more reliable update of service settings.

    Please note that requests made at the time of changing the settings may end with an error. The service may be unavailable for some time.

Fixed errors

  • An error with an incomplete log was fixed in the API service. The record about the request processing was not written to the log in case of client disconnect. Now the service will write a message about the request end with status code 499 if the client disconnected before the response.

  • New possible status codes were added to services responses:

    • The service will return status code 408 if the service did not receive a complete request message within the specified period (60 seconds by default).

    • The service will return status code 503 if the service did not process a request within the specified period (600 seconds by default).

    • The service will return status code 413 if the request payload is higher than the service can process.

    The error with the SDK descriptor type was fixed in the OpenAPI specification for the API service. Previously, the SDK descriptor was displayed as an Object type with "descriptor" and "version" fields. Now the type of object is set as string <byte>.