FooDB | Your own custom-build database | SQL Database library

Figured that out long time ago obviously, but finally remembered to put it here. So I finally used own class for settings instead of application.properties. Added all the settings into HashMap and injected that into StandardServiceRegistryBuilder which was injected into MetadataSources. Then I had to annotate all the classes into MetadataSources instance and make a new instance of SchemaExport using metadatasources as parameter.

I believe the problem is with mappings Foo.Dependents <-> DependencyFoo.Dependent and Foo.DependentsOf <-> DependencyFoo.DependentOf.

The actual dependents/dependents of foo should really be something like (pseudocode):

DataSourceBuilder.create().build() is going to instantiate HikariDataSource as it is the default DataSource as of SpringBoot 2.0. If you look into HikariDataSource source code the properties are jdbcUrl, username NOT url, user. So, you need to change property keys in application.properties file as follows:

MongoBulkWriteException contains a List, each failed write will be represented by an element in this list. Each element in this list contains an index attribute which is populated with the index of the element in the supplied list of documents.

So, you can use this index to work out which of the supplied documents failed.

Here's a test case showing this in action:

Use the .map() method!

So I've done some debugging and found something which might explain what's happening. At this point I'm not sure if it's a bug (could be this one), but I have not been able to find any other documentation to clarify this either.

For reference this is spring-boot 1.5.4.

I started from the log, you can find below an excerpt, more specifically the line regarding DataSourceInitializer.init (below with ==> at the beginning):

Assuming Java 8 and considering the fact that feedbackStatus may contain more than one element with the same ID.

1. Transform the list into a Map using ID as key and having a list of elements.
2. Iterate the list and use the Map to find all messages.

The code would be:

For example:

The answers given by wemu are completely correct: it was necessary, as the pom is currently written, to do mvn compile rather than flyway:migrate. Moreover, wemu's subsequent suggestion about moving the configuration should make it possible to invoke Flyway directly which is probably the correct way to do things. I guess the error messages from the Flyway plugin are completely accurate: it did not see the authorization/db access configuration but I did not know enough about Maven to understand why and spent significant time thinking the info was wrong not merely unavailable to the plugin.