Add support for "enabled" field about elastic4s HOT 8 CLOSED

Are you talking about _source: enabled ?

from elastic4s.

No, I really mean the "enabled" field in the core type:

{
   "mappings": {
    "whatever": {
      "type": "object",
      "enabled": false
    }
  }
}

What setting the value to false does is disable parsing and analysis so that you can store arbitrary JSON values.

from elastic4s.

Can you link me to docs on that, and I'll get it added.

from elastic4s.

You're fast :-)

You'll need to scroll down a bit:

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-object-type.html

An example of where it's used internally is in the _percolator index to store the query. It's not the same as dynamic in that it generates no schema, so you don't get conflicts if you first try to store a JSON object in one document, and then a string in another for a field flagged with "enabled": false.

from elastic4s.

Will add all those missing fields.

from elastic4s.

@richardhundt is this issue still present?

from elastic4s.

This should be fixed now, closing.

from elastic4s.

I think this is still open. You can disable a particular field createIndex(indexName).mappings(mapping("_doc").fields(objectField("o").enabled(false)), but I don’t think you can disable indexing all fields of the document e.g. createIndex(indexName).mappings(mapping("_doc").enabled(false)). Elasticsearch documentation: mapping enabled

from elastic4s.