Refactor mlayer

[Kranthi-Guribilli]

• Currently the mlayer service delegates all the data manipulation logic to the database service which is not the ideal way to do things.

• Moving data manipulation logic from dbservice to mlayer service:

  • So, inorder to achieve this we have to shift the data manipulation logic to MlayerServiceImpl from the following
  • database/mlayer/
  • • MlayerDomain - No changes
  • • MlayerInstance - No changes
  • • MlayerProvider - Done

      • Data Manipulation Logic: Moved the data manipulation logic, which includes processing the result from the database service call i.e., elastic search result, from the database service to the Mlayer service. This ensures that the Mlayer service is responsible for preparing the query and processing the results.
      • Handler Callback: The handler callback now delegates the result handling to the processProviderData method if the request contains an instance parameter. Otherwise, it directly handles the result from the database service call.

  • • MlayerGeoQuery - Done

      Previously, the logic to manipulate the request data to create a query was done inside the database service. Now, moved this logic to the getMlayerGeoQuery method within the Mlayer service. This includes extracting instance and id from the request, constructing a query string, and passing it to the database service.

  • • MlayerPopularDatasets - Done
  • • MlayerDataset - Done

[jenkins-datakaveri]

Can one of the admins verify this patch?

[pranavrd]

ok to test

[tanvi029]

This line will give error when the elastic index will be empty. It can be handled using 204 error if output from elastic is empty with no results. Reference: #364