[Version 1.3.2] Root type mapping not empty after parsing! Remaining fields:

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Version 1.3.2] Root type mapping not empty after parsing! Remaining fields:

Jack Park-2
I got this on 1.2.2 and found on the web that it was a bug. So, I upgraded to 1.3.2 and got the same bug.

There was a note here that suggested adding "mappings": to the top of the mappings doc. Didn't help on 1.2.2

And didn't change anything on 1.3.2

Here is the trace without "mappings"

 Root type mapping not empty after parsing! Remaining fields:   [xvertices : {core={properties={label={index=analyzed, store=true, type=string}, InVertexId={index=not_analyzed, store=true, type=string}, lox={index=not_analyzed, store=true, type=string}, OutVertexId={index=not_analyzed, store=true, type=string}, lists={properties={outEdgeIdList={index=not_analyzed, store=true, type=string}, inEdgeIdList={index=not_analyzed, store=true, type=string}}}}}}]

Here was where I had the same problem in my nodejs client:

and it was fixed by precisely the document I am using on the java client.

My code which reads a given file and index name from a config file and performs the mappings is here:

It's somewhat hairy code. If the index exists, it takes the time to dump the mappings to see what's in there. Otherwise, it brings in the json file, turns it into a JSONObject, and passes that in as mappings.

the mappings file which fails is below

Many thanks for ideas
Jack


{
    "core": {
        "properties": {
            "lox": {
                "index": "not_analyzed",
                "type": "string",
                "store": true
            },
            "InVertexId": {
                "index": "not_analyzed",
                "type": "string",
                "store": true
            },
            "OutVertexId": {
                "index": "not_analyzed",
                "type": "string",
                "store": true
            },
            "label": {
                "index": "analyzed",
                "type": "string",
                "store": true
            },
            "lists": {
                "properties": {
                    "inEdgeIdList": {
                        "index": "not_analyzed",
                        "type": "string",
                        "store": true
                    },
                    "outEdgeIdList": {
                        "index": "not_analyzed",
                        "type": "string",
                        "store": true
                    }
                }
            }
        }
    }

}

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH6s0fyS2x2PYKhaqFcX%3D3dWvC-eGcBR6v-yYr5apKrNOv%2Bq7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [Version 1.3.2] Root type mapping not empty after parsing! Remaining fields:

Jack Park-2

On Mon, Sep 15, 2014 at 4:16 PM, Jack Park <[hidden email]> wrote:
I got this on 1.2.2 and found on the web that it was a bug. So, I upgraded to 1.3.2 and got the same bug.

There was a note here that suggested adding "mappings": to the top of the mappings doc. Didn't help on 1.2.2

And didn't change anything on 1.3.2

Here is the trace without "mappings"

 Root type mapping not empty after parsing! Remaining fields:   [xvertices : {core={properties={label={index=analyzed, store=true, type=string}, InVertexId={index=not_analyzed, store=true, type=string}, lox={index=not_analyzed, store=true, type=string}, OutVertexId={index=not_analyzed, store=true, type=string}, lists={properties={outEdgeIdList={index=not_analyzed, store=true, type=string}, inEdgeIdList={index=not_analyzed, store=true, type=string}}}}}}]

Here was where I had the same problem in my nodejs client:

and it was fixed by precisely the document I am using on the java client.

My code which reads a given file and index name from a config file and performs the mappings is here:

It's somewhat hairy code. If the index exists, it takes the time to dump the mappings to see what's in there. Otherwise, it brings in the json file, turns it into a JSONObject, and passes that in as mappings.

the mappings file which fails is below

Many thanks for ideas
Jack


{
    "core": {
        "properties": {
            "lox": {
                "index": "not_analyzed",
                "type": "string",
                "store": true
            },
            "InVertexId": {
                "index": "not_analyzed",
                "type": "string",
                "store": true
            },
            "OutVertexId": {
                "index": "not_analyzed",
                "type": "string",
                "store": true
            },
            "label": {
                "index": "analyzed",
                "type": "string",
                "store": true
            },
            "lists": {
                "properties": {
                    "inEdgeIdList": {
                        "index": "not_analyzed",
                        "type": "string",
                        "store": true
                    },
                    "outEdgeIdList": {
                        "index": "not_analyzed",
                        "type": "string",
                        "store": true
                    }
                }
            }
        }
    }

}

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH6s0fw2q2WvK0B4jhYpC%3DJCiyHzxKdmakuRfqxNRw1riE3-5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.