Skip to content

"did not create a new index" when running es_create first time #47

@codekiln

Description

@codekiln

When DEM starts up, it automatically creates and activates indexes if none are created. This means that if your first DEM command is ./manage.py es_create my_index, the first thing it does is auto-create the indexes, and then when it comes time to actually perform the create action it doesn't find that the index has changed:

$ ./manage.py es_create movies
[2018-11-11 20:21:35.400650]: The doc type for index 'movies' changed; created a new index version 'test_movies-8' in elasticsearch.
[2018-11-11 20:21:35.412470]: For index 'movies', activating 'test_movies-8' because you said so.
[2018-11-11 20:21:35.431213]: The doc type for index 'movies' has not changed since 'test_movies-8'... 
PUT http://localhost:9200/test_movies-8 [status:400 request:0.003s]
[2018-11-11 20:21:35.437138]:   ... did not create a new index.

This task is to ensure this confusing messaging does not appear.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions