Incorrect Mapping Created for Nested Types about mongoosastic

[taterbase]

taterbase#79 (comment)

Please provide a detailed example of how to create a custom mapping using elasticals, mongoosastic.

[taterbase]

taterbase#79 (comment)

I have the same issue (es_analyzer has no effect) and I'm not even using nested types....

[ztratar]

I too am hitting this issue and need it resolved to continue use of mongoosastic. Love the plugin, but this is proving to be a really, really important feature unless I run some silly, unnecessary data migrations.

[ztratar]

Specifically:

var EducationSchema = new Schema({
    school_name: {
        type: String,
        es_indexed: true
    },
    start_date: {
        year: {
            type: Number,
            es_indexed: true
        },
        month: {
            type: Number,
            es_indexed: true
        },
        day: {
            type: Number
        }
    },
    end_date: {
        year: {
            type: Number,
            es_indexed: true
        },
        month: {
            type: Number,
            es_indexed: true
        },
        day: {
            type: Number
        }
    },
    study: {
        type: String,
        es_indexed: true,
        es_type: 'string',
        es_fields: {
            raw: { type: 'string', index: 'not_analyzed' }
        }
    },
    degree: String
});

var UserSchema = new Schema({
...
    educations: {
        type: [EducationSchema],
        es_indexed: true
    },
...
});

The study field is not mapped with a raw multi_field.

[rdubigny]

On @ztratar 's model I bet start_day.day is indexed in elastic search as well despite it should not. I use a similar model. I didn't managed to make "es_indexed" nor "es_boost" nor "es_cast" to work within nested objects. It's behave like these are simply not read. I haven't tested the other attributes.

[ksavidetove]

Referencing here issues #28 and #48 since I develepped a fix and opened a PR to resolve it