Deprecate MultiField()

[mausch]

I think MultiField() for mapping should be marked as [Obsolete]. It's been deprecated since ES 1.0 so NEST should reflect that.
Otherwise people will inadvertently use it (at least I did!) which causes problems down the line. In my particular case, this caused issues when comparing mappings.
Another solution would be generating the new-style multi-fields from the same MultiField() definition, but that would be a breaking change and could be confusing.

[Mpdreamz]

++

in NEST 2.0 they have been removed altogether.

[TheFireCookie]

What is this assigned for then? :)

What is the equivalent syntax on NEST for the "new" Fields of ES?

[gmarz]

@TheFireCookie use the Fields() method under the property you're mapping:

.String(s => s
    .Name("mainfield")
    .Fields(f => f
        .String(fs => fs.Name("mainfield.raw").Index(FieldIndexOption.NotAnalyzed))
    )
)

[TheFireCookie]

So I just that the .MultiField method to Obsolete and I can do a pull request ?

[gmarz]

@TheFireCookie that's correct- a PR would be much appreciated!

[gmarz]

Closed via #1618