[UXPROD-2807] Create FOLIO internal Elasticsearch APIs - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: New Feature
Status: Closed (View Workflow)
Priority: P2
Resolution: Done
Affects Version/s: None
Fix Version/s: R1 2021
Component/s: None
Labels:
- r1-2021-at-risk

Template:

UXPROD features
Epic Link:
Elasticsearch
Development Team:
Falcon
Calculated Total Rank:
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:

Hide
[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.]

Show
[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:

Hide
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~~.

Show
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 .
Showstopper Capacity Planning Team Recommendation:

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

TestRail: Results

Attachments

Issue Links

is defined by

MODINVSTOR-620 Domain events sending in inventory-storage for instance

Closed

MODINVSTOR-639 Domain events sending in inventory-storage for item

Closed

MODINVSTOR-647 Refactor ItemStorageAPI and HoldingsStorageAPI before implementing domain events

Closed

MODINVSTOR-649 Populate instanceId for new/old item when publishing domain event

Closed

MSEARCH-10 Indexing of instances

Closed

MSEARCH-11 Rancher env setup

Closed

mentioned in: Page Loading...

(1 is defined by , 1 mentioned in)

Activity

People

Assignee:: Magda Zacharska

Reporter:: Magda Zacharska

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 10/Nov/20 4:27 PM

Updated:: 10/Mar/21 11:16 PM

Resolved:: 10/Mar/21 11:16 PM

Create FOLIO internal Elasticsearch APIs