[
https://issues.apache.org/jira/browse/JAMES-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271960#comment-17271960
]
Juhan Aasaru commented on JAMES-3492:
-------------------------------------
Thanks for the info.
We are planning to go to live with our MVP using Elasticsearch 6.8 around end
of March.
But we have an internal requirement that we cannot rely on anything that is not
maintained. So yes we would be interested to work on this (realistic would be
to do this around May 2021) but we would first need somehow to figure out the
exact effort required (for planning).
So I think it would be good idea to invest a little time first to do the
compatibility study and then come up with the upgrade plan. Do I understand
correctly that the path would be the following:
# run test suite against Elasticsearch 7 and come up with all the things that
don't work
# create a upgrade plan (list of tasks) based on that
# implement tasks listed in the plan
# testing
> Elasticsearch 6->7 upgrade for guice version
> --------------------------------------------
>
> Key: JAMES-3492
> URL: https://issues.apache.org/jira/browse/JAMES-3492
> Project: James Server
> Issue Type: Improvement
> Reporter: Juhan Aasaru
> Priority: Major
>
> Guice versions use Elasticsearch 6 that has reached end of life.
> We are thinking about starting to work on this issue but first we need to
> estimate the effort required. If anyone has any input on this please add a
> comment. Thanks!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
