# Is custom routing deprecated? **URL:** \ **Category:** Elasticsearch\ **Created:** [December 8, 2015, 10:45pm UTC](https://discuss.elastic.co/t/is-custom-routing-deprecated/36678 "2015-12-08T22:45:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![AndreKR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrekr/32/6233_2.png) [@AndreKR](https://discuss.elastic.co/u/AndreKR)\ **Post date:** [December 8, 2015, 10:45pm UTC](https://discuss.elastic.co/t/is-custom-routing-deprecated/36678/1 "2015-12-08T22:45:57Z")
[This blog entry](https://www.elastic.co/blog/customizing-your-document-routing) has a warning at its top: > WARNING: This article contains outdated information. We no longer recommend taking its advice. Does that mean the `routing` parameter should not be used at all anymore? Is there a reason? It seems beneficial to me to restrict a query to just one shard whenever possible. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 10, 2015, 4:08am UTC](https://discuss.elastic.co/t/is-custom-routing-deprecated/36678/2 "2015-12-10T04:08:53Z")
> [@AndreKR](#): > > Does that mean the routing parameter should not be used at all anymore? Is there a reason? It seems beneficial to me to restrict a query to just one shard whenever possible. No, it just means that it's nearly 3 years old so there are things in there that no longer apply. However you can still do custom routing. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:32pm UTC](https://discuss.elastic.co/t/is-custom-routing-deprecated/36678/3 "2017-07-05T23:32:10Z")