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

Investigate strange logs on startup #519

Open
schneijan opened this issue Feb 2, 2021 · 2 comments
Open

Investigate strange logs on startup #519

schneijan opened this issue Feb 2, 2021 · 2 comments
Assignees
Labels
maintainance Basic maintainance operations to keep the project stable

Comments

@schneijan
Copy link
Member

schneijan commented Feb 2, 2021

2021-02-02 16:00:38.979  WARN   --- [           main] .m.c.i.MongoPersistentEntityIndexCreator : Automatic index creation will be disabled by default as of Spring Data MongoDB 3.x.
	Please use 'MongoMappingContext#setAutoIndexCreation(boolean)' or override 'MongoConfigurationSupport#autoIndexCreation()' to be explicit.
	However, we recommend setting up indices manually in an application ready block. You may use index derivation there as well.
	> -----------------------------------------------------------------------------------------
	> @EventListener(ApplicationReadyEvent.class)
	> public void initIndicesAfterStartup() {
	>
	>     IndexOperations indexOps = mongoTemplate.indexOps(DomainType.class);
	>
	>     IndexResolver resolver = new MongoPersistentEntityIndexResolver(mongoMappingContext);
	>     resolver.resolveIndexFor(DomainType.class).forEach(indexOps::ensureIndex);
	> }
	> -----------------------------------------------------------------------------------------
@schneijan schneijan added the maintainance Basic maintainance operations to keep the project stable label Feb 2, 2021
@schneijan schneijan self-assigned this Feb 2, 2021
@schneijan
Copy link
Member Author

There is not much we can do to get rid of this issue. A solution would probably to upgrade Mongo dependencies again: https://jira.spring.io/browse/DATAMONGO-2435

@ana-silva
Copy link
Collaborator

@schneijan ok, I would say we do the update after the first release because we started the testing phase already. Probably we will need a new test phase after the upgrade of mongoDB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintainance Basic maintainance operations to keep the project stable
Projects
None yet
Development

No branches or pull requests

2 participants