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:
-
Template:
-
Epic Link:
-
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:
-
Showstopper December 11 Meeting Summary:
-
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...