Elasticsearch (UXPROD-2591)

[UXPROD-2807] Create FOLIO internal Elasticsearch APIs Created: 10/Nov/20  Updated: 10/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R1 2021
Parent: Elasticsearch

Type: New Feature Priority: P2
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Done Votes: 0
Labels: r1-2021-at-risk
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODINVSTOR-620 Domain events sending in inventory-st... Closed
is defined by MODINVSTOR-639 Domain events sending in inventory-st... Closed
is defined by MODINVSTOR-647 Refactor ItemStorageAPI and HoldingsS... Closed
is defined by MODINVSTOR-649 Populate instanceId for new/old item ... Closed
is defined by MSEARCH-10 Indexing of instances Closed
is defined by MSEARCH-11 Rancher env setup Closed
Epic Link: Elasticsearch
Development Team: Falcon
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R2
Rank: Lehigh (MVP Summer 2020): R2
Score: 17
Showstopper for Summer 2021 Implementers?: No
Showstopper Comments from Summer 2021 Implementers: [Steven from Five Colleges: Five Colleges Showstopper based on complexity of locations in the consortium] [Tod from Chicago: The issue for us is around needed improvements to search and search results in Inventory, many of which have become tied to Elasticsearch implementation. The problem with search in Inventory is that there are many cases where the available identifying text is not enough distinguish between the results. Without those needed improvements, we will be having some difficult conversations about whether we can support our workflows.]
Showstopper December 11 Meeting Summary: UPDATE: This feature was changed to NOT be a showstopper given a thin-thread version of UXPROD-2712 is the actual showstopper.
Same as UXPROD-2806.

 Description   

Current situation or problem:
The currently existing inventory search does not perform as expected on large data sets due to the PostgreSQL limitation.
In scope:

1. Build Inventory model:

  • Utility classes and Spring components
  • JSON module structure
  • REST Controller for index endpoints

2. Index mappings and settings:

  • Utility classes and Spring components
  • EsIndexClient EsIndex/Repository

3. Inventory indexing:

  • Kafka event listener
  • REST Controller for saving resource endpoint

4.Search:

  • CQL query parser (EsSearchClient, Query builder for ElasticSearch)
  • RESTController - search endpoints


 Comments   
Comment by Steve Bischof [ 09/Dec/20 ]

Five Colleges Showstopper based on complexity of locations in the consortium

Comment by Tod Olson [ 10/Dec/20 ]

Chicago - The issue for us is around needed improvements to search and search results in Inventory, many of which have become tied to Elasticsearch implementation. The problem with search in Inventory is that there are many cases where the available identifying text is not enough distinguish between the results. Without those needed improvements, we will be having some difficult conversations about whether we can support our workflows.

Generated at Fri Feb 09 00:27:01 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.