# So I migrated a custom facet to 0.90.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [May 3, 2013, 7:14am UTC](https://discuss.elastic.co/t/so-i-migrated-a-custom-facet-to-0-90-0/11796 "2013-05-03T07:14:03Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Eric\_Jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eric_jain/32/834_2.png) [@Eric\_Jain](https://discuss.elastic.co/u/Eric_Jain)\ **Post date:** [May 3, 2013, 7:14am UTC](https://discuss.elastic.co/t/so-i-migrated-a-custom-facet-to-0-90-0/11796/1 "2013-05-03T07:14:03Z")
Lots of stuff has been renamed or moved around, and none of this is documented, but after looking at the code for some of elasticsearch's built-in facets I was able to update my code without too much effort. Then I spent the rest of the day trying to figure out why the facet was no longer producing correct results consistently; the problem turned out to be that elasticsearch now reuses GeoPoint instances, while I assumed they were immutable... Can anyone spot anything else I overlooked (and that might bite me later on)? [https://github.com/zenobase/geocluster-facet](https://github.com/zenobase/geocluster-facet) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:38am UTC](https://discuss.elastic.co/t/so-i-migrated-a-custom-facet-to-0-90-0/11796/2 "2017-07-06T02:38:31Z")
Closed on July 6, 2017, 2:38am UTC