Skip to content
This repository has been archived by the owner on Sep 23, 2022. It is now read-only.

Not dealing with duplicate names well #14

Closed
gshively11 opened this issue Mar 13, 2015 · 5 comments
Closed

Not dealing with duplicate names well #14

gshively11 opened this issue Mar 13, 2015 · 5 comments
Labels

Comments

@gshively11
Copy link

Kibana does not enforce unique names for searches/dashboards/etc. It causes weird behavior in the backup process. We need to ensure that names are unique for all saved assets.

@gshively11 gshively11 added the bug label Mar 13, 2015
@gshively11
Copy link
Author

Discovered in #10

@bobcat0070
Copy link

Not sure if you want to explore this option, but could be worth porting to leverage https://github.com/taskrabbit/elasticsearch-dump ... this seemingly deals with duplicates without any problems.

@gshively11
Copy link
Author

@bobcat0070 It's a good suggestion, we are actually already leveraging it 😄

However, we are taking the data pulled by elasticsearch-dump and splitting it into separate files, so that they can be modified/deployed separately. That introduces this issue, because if two documents in the index have the same _id, they overwrite each other.

@bobcat0070
Copy link

Gotcha, so simply naming based on _type + _id would fix it.

@gshively11
Copy link
Author

Fixed in bec62a5

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants