Currently, we are saving documents in a single index with a nested field. This nested field represents prices and looks like the following:
'prices' => [ 'type' => 'nested', 'properties' => [ 'date' => [ 'type' => 'date' ], 'price' => [ 'type' => 'integer' ], 'persons' => [ 'type' => 'integer' ] ] ]
These kind of nested objects are expected to change frequently. Per document there can be up to 100,000 nested price objects.
Currently we have concerns about index rate/time and computing time. Is there any better approach to save this kind of data structure? We must keep the ability to filter efficiently over the prices.
Thanks in advance