Use doc_values in mappings

[Travis Tripp]

We also should set "doc_values": true

https://www.elastic.co/guide/en/elasticsearch/guide/current/doc-values.html

https://www.elastic.co/blog/support-in-the-wild-my-biggest-elasticsearch-problem-at-scale

I think we actually need to go through and do this on all mappings except analyzed strings. That should be a separate patch though.

Go to about halfway through this webinar: https://www.elastic.co/webinars/es-at-scale

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/288932

[OpenStack Infra (hudson-openstack)]

Change abandoned by Steve McLellan (<email address hidden>) on branch: master
Review: https://review.openstack.org/287401
Reason: Abandoning in favor of alternative approach in https://review.openstack.org/#/c/288932

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/288932
Committed: https://git.openstack.org/cgit/openstack/searchlight/commit/?id=12eb651ee39e455b61285b5e5f935fa0ba2bd478
Submitter: Jenkins
Branch: master

commit 12eb651ee39e455b61285b5e5f935fa0ba2bd478
Author: Steve McLellan <email address hidden>
Date: Fri Mar 4 23:04:10 2016 -0600

    Set doc_values on field definitions

    Using the doc_values field storage format can result in dramatically
    reduced memory usage at the cost of some disk space. This patch enforces
    what is the default in Elasticsearch 2.x. It does so by modifying the
    mapping to add doc_values: True for appropriate field types. This can
    be overridden globally in configuration, per plugin via a property or
    for individual field types.

    See
    https://www.elastic.co/guide/en/elasticsearch/guide/current/doc-values.html

    This is an alternative to https://review.openstack.org/#/c/287401/

    Change-Id: I5e5fb880657fcab7223e0e5f7525aec07fbdf612
    Closes-Bug: #1498995

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/searchlight 0.2.0.0rc1 release candidate.