A solution was found here http://stackoverflow.com/questions/22071198/adding-mapping-to-a-type-from-java-how-do-i-do-it
On Mon, Sep 15, 2014 at 4:16 PM, Jack Park <jackp...@topicquests.org> 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 > > http://stackoverflow.com/questions/24254081/elasticsearch-1-2-1-exception-root-type-mapping-not-empty-after-parsing > > 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: > > http://elasticsearch-users.115913.n3.nabble.com/A-fresh-variant-of-MapperParsingException-td4061732.html > > 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: > https://gist.github.com/KnowledgeGarden/b67b9f38a2ea9a29c21a > > 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 elasticsearch+unsubscr...@googlegroups.com. 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.
