Page Comparison

Requirements: Image ModifiedMODORDERS-488 Investigate transition of Orders search to cross-index subqueries

API with views:

/orders-storage/receiving-history  → receiving_history_view

Receiving view totally differs from other views. Data for this enpoint totaly builds on the fly and don't has any own tables for persisting data. It could be switched to the cross index approach, but in this case instead of single database request there will be 3 requests which will return a large amount of data (collections of pieces, order lines and purchase orders). Making multiple requests and processing such large amount of data (which might be containing hundreds of elements withing each collection) wil not give any perfomance improvement and  will consume a much more amount of memory.

For now we have to leave it as is.

/orders-storage/orders  → orders_view

View and API implementation can be removed at all. All requests for retrieving collections of orders should be routed to the endpoint "/order-storage/purchase-orders" where cross index approach already implemented.

Will require backend story in buisness module for this purpose. [TO DO] 

Will require UI story for support cross index queries upon calling

/orders-storage/po-lines  → po_lines_view

Will require backend story in buisness module for this purpose. [TO DO]

Will require UI story for support cross index queries

Prepared a POC with migration of this endpoint from searching accross the views to the searching via cross-indexes. This POC contains migration to the cross index approach and will signifcantly reduce amount of work in storage modules.

/orders-storage/order-lines  →  order_lines_view

View and API implementation can be removed as well. All requests for retrieving collections of PO lines should be routed to the endpoint "/order-storage/po-lines"

...