It seems that StatisticsCalculator doesn´t work well when I group features by numeric (only numbers: [0-9]+) field keys. I attach a sample.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Agree that looks like a bug, I was also able to reproduce it. It looks like numeric values loses their trailing zeroes, so that values like 1, 10 and 100 gets grouped together as one.
Another workaround is to cast pk_celda to string by inserting a StringFormatter before the StatisticsCalculator:
Hi @j4, thanks for pointing this out to us, I have let our development team know and they are going to take a look at what is going on here. I will post any updates here.
Hi @j4, thanks for pointing this out to us, I have let our development team know and they are going to take a look at what is going on here. I will post any updates here.
Agree that looks like a bug, I was also able to reproduce it. It looks like numeric values loses their trailing zeroes, so that values like 1, 10 and 100 gets grouped together as one.
Another workaround is to cast pk_celda to string by inserting a StringFormatter before the StatisticsCalculator:
Yep, this WAS a bug alright. Sorry about that. It was specific to this transformer and only happened with integers in the group by. Fix going in right now. Will be released as part of a 2017.1.1 hotfix wrap up (and therefore will bein 2017.1.2 and 2018.x as well. Thanks for the good diagnosis @david_r -- sorry for the problem @egomm
Great news @j4, the bug has been fixed in the latest hot fix 2017.1.1.1, which you can download at safe.com/downloads, it is also fixed in any future versions. Thanks again for catching this!
Great news @j4, the bug has been fixed in the latest hot fix 2017.1.1.1, which you can download at safe.com/downloads, it is also fixed in any future versions. Thanks again for catching this!
Yes, good news. I saw this news on Twitter account :)