Issue with config/mappings/_default


(Kenneth Loafman) #1

Hi,

If I put a mapping under |config/mappings/_default|, restart, and try to
save to a new index (auto-created), the save returns with a 500 error,
NullPointerException (no diagnostics). If I do the following manually:

$ [create newindex]
$ curl -XPUT 'http://192.168.1.4:9200/newindex/twitter/_mapping'
-d "cat /opt/elasticsearch-0.8.0/config/mappings/_default/twitter.json"

then try to save to it, all is well. The problem is that I have to use
auto-create for the index and I need to have different defaults than ES
defaults for our mappings. If I knew I was creating a new index, then I
could do a put-mapping and things would work, but I can't tell if it is
new or old, that comes from the front end processing. I need to be able
to set defaults on all the known doc types that we use, or have some
quick (atomic) way to tell if an index already exists.

...Thanks,
...Ken


(Shay Banon) #2

Can you list the steps you take exactly that recreates the problem, and
include the default mapping you use and the json you try to index?

On Wed, Jul 14, 2010 at 11:00 PM, Kenneth Loafman <kenneth.loafman@gmail.com

wrote:

Hi,

If I put a mapping under config/mappings/_default, restart, and try to
save to a new index (auto-created), the save returns with a 500 error,
NullPointerException (no diagnostics). If I do the following manually:

$ [create newindex]
$ curl -XPUT 'http://192.168.1.4:9200/newindex/twitter/_mapping'
-d "cat /opt/elasticsearch-0.8.0/config/mappings/_default/twitter.json"

then try to save to it, all is well. The problem is that I have to use
auto-create for the index and I need to have different defaults than ES
defaults for our mappings. If I knew I was creating a new index, then I
could do a put-mapping and things would work, but I can't tell if it is new
or old, that comes from the front end processing. I need to be able to set
defaults on all the known doc types that we use, or have some quick (atomic)
way to tell if an index already exists.

...Thanks,
...Ken


(system) #3