You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using knapsack to migrate an index from one name to another in the same instance. To be clear I'm using 1.5.2.2 but I don't think it matters for this.
Steps:
Export an index "foo".
Import it with map; map=\{"foo":"new-foo"\}.
Result: the index settings are lost; the index "new-foo" has default settings.
Workaround: export with map. Import as normal. The new index will include the settings.
The workaround is totally appropriate but I had to stumble upon it. If this is a not a bug, maybe just a readme update in the import section would be sufficient.
The text was updated successfully, but these errors were encountered:
Yes, this is kind of a glitch. I have to add a check that index settings of mapped index names must be recognized when importing. An export with map points to the correct index name.
I'm using knapsack to migrate an index from one name to another in the same instance. To be clear I'm using 1.5.2.2 but I don't think it matters for this.
Steps:
map
;map=\{"foo":"new-foo"\}
.Result: the index settings are lost; the index "new-foo" has default settings.
Workaround: export with
map
. Import as normal. The new index will include the settings.The workaround is totally appropriate but I had to stumble upon it. If this is a not a bug, maybe just a readme update in the import section would be sufficient.
The text was updated successfully, but these errors were encountered: