@riccardolederj2 I've added batch processing capabilities to haystack-nclient.
The first application of this is for eval (automatically batching to evalAll. I've added a new read method to the extension ops that uses eval for the batching you require.
@rracariu we need to add a new HTTP op for batching of read request to our new FIN project. Then it's easy for me to add batch processing.
I did look into combining haystack filters into one super filter and then rerunning the filters client side. However this won't always work under certain conditions (i.e. pathing to records that aren't in the client result set). Therefore it's all restricted to eval and Axon to start with. The good news is we have BatchProcessor which makes this easy to apply elsewhere.
EliteScientist
commented
2 years ago
@riccardolederj2 I've added batch processing capabilities to
haystack-nclient.The first application of this is for eval (automatically batching to
evalAll. I've added a newreadmethod to the extension ops that uses eval for the batching you require.@rracariu we need to add a new HTTP op for batching of read request to our new FIN project. Then it's easy for me to add batch processing.
I did look into combining haystack filters into one super filter and then rerunning the filters client side. However this won't always work under certain conditions (i.e. pathing to records that aren't in the client result set). Therefore it's all restricted to eval and Axon to start with. The good news is we have
BatchProcessorwhich makes this easy to apply elsewhere.