Support for disabling dynamic creation of mappings for unmapped types about elastic4s HOT 10 CLOSED

Should just be a case of adding that parameter to the definition.

from elastic4s.

Ok usually I'm in favour of keeping the DSL to match the json values. So in this case something like dynamic strict or dynamicStrict true ? Although I actually think your syntax makes more sense than the actual elasticsearch one.

from elastic4s.

dynamicStrict SGTM

from elastic4s.

I've added a commit to allow this

create index "twitter" mappings(
  "tweet" as (
      //...
   ) dynamic Strict
)

But I can change it.

from elastic4s.

Which is the same as

create index "twitter" mappings(
  "tweet" as (
      //...
   ).dynamic(Strict)
)

If you like parenthesis

from elastic4s.

Great. Thanks!!

from elastic4s.

It's on master. Do you need a release to central ?

from elastic4s.

Sure.

from elastic4s.

Unfortunately, using Strict means that indexing will fail on documents with dynamic values:

"The dynamic parameter can also be set to strict, meaning that not only will new fields not be introduced into the mapping, but also that parsing (indexing) docs with such new fields will fail."

I have a scenario where I want to not index unmapped values, but not have them fail altogether. I think that setting dynamic to false achieves this goal (from the documentation, it appears that it works that way for subdocuments).

from elastic4s.

Hmm. It's worth checking.

from elastic4s.