Using Alias mapping design for specific scenario

Our project contain customers. each customer doing transaction which being
indexed at ES for later searching capabilities.

Not all transaction structured the same and the structure is possibly to be
changed (Changing fields and types/mappings).

I need to design ES indexing in advanced so it will be:

  1. Easy to change the doc fields(rename current ones).
  2. Easy to change already existed field types.

I read about aliasing mapping and re indexing but I still didn't understand
the concept or how to implement this to have best practice design for my
scenario,

Any suggestions and farther explaining in additional to the official
documentation would be warmly welcomed.

Thank you.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/86197349-e251-4273-bcbb-a0954cce04dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.