I have an elastic search endpoint that provides data. I want to render some selected columns from that data into a grid (like we render flat grid). I have been able to use captions but not able to render the grid (simple table) please guide me how to do that
Apart from this i also want to know if we can add pagination to this grid if data is beyond some specified size.
Thank you for reaching out to us.
Our team would like to explain that the flat form is not available in case Elasticsearch is used as a data source. Detailed technical specifications for each supported data source can be found by the link.
As a workaround, we suggest considering exporting the index data from Elasticsearch to CSV/JSON format. Next, Flexmonster can be directly connected to the exported file or to the script, returning the data. In such a case, the flat form will be available to use. However, this approach implies loading the whole data set at once.
Concerning the pagination.
As for now, Flexmonster does not support pagination by default.
However, the pagination feature for the flat form can be implemented using the custom data source API protocol provided by Flexmonster.
Please let us know in case you are interested in such a possibility so that we could provide you with the corresponding guide.
Do not hesitate to contact us in case further assistance is needed.
Our team is looking forward to hearing from you.
Thank you for the response. I also wanted to know if there is any maximum data limit we have in flexmonster if we are using elastic search
Thank you for your question.
In case Elasticsearch is used as a data source, all calculations are performed on the server-side. Only the data that needs to be displayed is sent to the client’s machine.
It means the size of the initial data set itself is only limited to server capabilities. The amount of the data passed to Flexmonster is determined by the report itself.
For example, in case two fields need to be displayed on the grid, only aggregated data representing these fields will be loaded. At the same time, the initial data set can contain millions of records and thousands of columns, but only the required data will be processed and passed to the client.
Such an approach allows visualizing large data sets, even if the capabilities of the client’s browser would not allow loading and processing it on the client-side.
Still, it is possible to configure the report in the way a large amount of data needs to be loaded from the server. In such a case, it is the client’s machine and browser capabilities that determine how much data can be loaded.
We hope it helps.
Please contact us in case any further assistance is needed.