Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JAMES-3492 #328

Closed
wants to merge 29 commits into from
Closed

JAMES-3492 #328

wants to merge 29 commits into from

Conversation

andrevka
Copy link

includes #318
Use elasticsearch v7 modules everywhere

LanKhuat and others added 20 commits March 9, 2021 10:29
The check returns status 200 in ElasticSearch 7, preventing the usage of James custom mapping when creating index.
The fields are stored within the document and can be fetched with storedFields option.
@mbaechler
Copy link
Member

18:45:39,620 [INFO] Apache James :: Mailbox :: ElasticSearch ........... FAILURE [  8.768 s]

The module doesn't compile right now

Copy link
Contributor

@LanKhuat LanKhuat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you squash all the commits from #318 along with 0ee7303 commit?

@@ -47,6 +47,7 @@
import org.elasticsearch.search.builder.SearchSourceBuilder;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Disabled;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's deprecate ES7 metric reporting and only rely on the prometheus endpoints, rather that some custom, unmaintained reporters?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems reasonable to me to rely solely on prometheus

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall i remove it from the project?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can raise the topic on server-dev mailing list, explain that it do not work with ES v6, that the underlying library is unmaintained (gasp) and that we have a pronmetheus alternative.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll give my 👍 there.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chibenwa
Copy link
Contributor

I'm surprised JMAP integration tests did not break...

@andrevka
Copy link
Author

Where should the elasticsearch update instructions be added?

@chibenwa
Copy link
Contributor

In /upgrade-instructions.md

upgrade-instructions.md Outdated Show resolved Hide resolved
@chibenwa
Copy link
Contributor

Shall we rename packages and maven modules to remove the v7 suffix?

@chibenwa
Copy link
Contributor

Nice job BTW!

@chibenwa
Copy link
Contributor

We need a documentation update as well...

dockerfiles/run/docker-compose-branch-master.yml
dockerfiles/run/docker-compose.yml
README.adoc
docs/modules/servers/pages/distributed/run.adoc
docs/modules/servers/pages/distributed/operate/guide.adoc
docs/modules/servers/pages/distributed/operate/logging.adoc
docs/modules/servers/pages/distributed/run-docker.adoc
docs/modules/servers/pages/distributed/configure/elasticsearch.adoc
src/site/xdoc/server/quick-start-cassandra.xml
src/site/xdoc/server/config-elasticsearch.xml
src/site/markdown/server/install/guice-cassandra.md
src/site/markdown/server/install/guice-cassandra-rabbitmq-swift.md

Copy link
Contributor

@Arsnael Arsnael left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work, huge thanks :)

@chibenwa
Copy link
Contributor

Hello!

Huge thanks for your work on this topic. I did just merge this PR.

I will then start working on the 3.6.0 release from tomorrow.

Cheers,

@Arsnael Arsnael closed this Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants