# Map http response code/network port as string or short/integer?

**URL:** <https://discuss.elastic.co/t/map-http-response-code-network-port-as-string-or-short-integer/81206>\
**Category:** Elasticsearch\
**Created:** [April 4, 2017, 7:11pm UTC](https://discuss.elastic.co/t/map-http-response-code-network-port-as-string-or-short-integer/81206 "2017-04-04T19:11:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anhlqn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anhlqn/32/5454_2.png) [@anhlqn](https://discuss.elastic.co/u/anhlqn)\
**Post date:** [April 4, 2017, 7:11pm UTC](https://discuss.elastic.co/t/map-http-response-code-network-port-as-string-or-short-integer/81206/1 "2017-04-04T19:11:42Z")

</div>

For http response code like 200, 301 and network port like 53000, would there be any performance benefits between mapping those fields as string/keyword vs. short/integer?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 2, 2017, 7:11pm UTC](https://discuss.elastic.co/t/map-http-response-code-network-port-as-string-or-short-integer/81206/2 "2017-05-02T19:11:43Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.