james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <server-...@james.apache.org>
Subject [jira] [Resolved] (JAMES-2202) We should rely on Alias when dealing with ElasticSearch
Date Wed, 01 Nov 2017 11:06:01 GMT

     [ https://issues.apache.org/jira/browse/JAMES-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tellier Benoit resolved JAMES-2202.
-----------------------------------
    Resolution: Fixed

https://github.com/linagora/james-project/pull/1069 solved the issue

> We should rely on Alias when dealing with ElasticSearch
> -------------------------------------------------------
>
>                 Key: JAMES-2202
>                 URL: https://issues.apache.org/jira/browse/JAMES-2202
>             Project: James Server
>          Issue Type: Improvement
>          Components: elasticsearch
>    Affects Versions: master
>            Reporter: Tellier Benoit
>            Priority: Major
>
> Alias gives more flexibility when administrating ElasticSearch. It is a general good
practice.
> Also, we want to handle configurable index name and alias name. (This would allow for
instance to use several James server on the same ElasticSearch cluster).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message