Hi, I am having some problem using mapping on elasticsearch, when I use the field “Periodo” as a filter or as a group, some data goes missing, looks really weird. I attached the config file and four prints.
I can assure you that the data is correct in the database, if I sum all the “consumos” from the period, gives what is in the grand total and all date values that are used in the mapping are OK, so why is some data missing, is there some configuration that need to be made?
Thank you for reaching out to us and for providing additional details.
It does look like an issue, but still, we are not able to reproduce it with our Elastcisearch demo server.
Could you please provide a sample of your data index to reproduce the issue on our end (this can be done via email)?
This will help our team a lot to investigate the case further.
Looking forward to hearing from you.
We try to create an examplo that you can easily reproduce.
Thank you for providing the example.
This greatly helped our team to reproduce the issue on our end.
Our team will provide the fix in the minor release version with the ETA 24th of February.
Please let us know if you have any questions.
We are glad to inform you that our team has found a solution to the problem.
It turns out that if only the year and month are specified in the date formatting and the
interval is left as default (1 day), then for cases when the field members differ only by day, the data for some of the members could get lost.
For example, if we have the following data:
2019/08/22 15:37:05 and
2019/08/23 16:37:05, then when the date formatting is applied (
YYYY/MM) the members will turn out the same (
2019/08) and the data for one of them, for example,
2019/08/22 15:37:05 will get lost.
Therefore, for such cases, we kindly recommend setting the
interval property as well, for example:
This way the data should be shown correctly.
In addition, we are glad to announce that our team has made a couple of improvements addressing this case and the issue with showing dates in the drill-through view was fixed. This is available in the 2.8.1 version of Flexmonster.
You are welcome to update the component. Here are our updating tutorials for guidance:
1) Migration guide from 2.7 to 2.8
2) Updating to the latest version
Please let us know if everything works fine for you.
Looking forward to your reply.