The addition of Postgres as an IndexDAO made it so that if you use Conductor core as your deployment mechanism, and you use Postgres and ES7, there is a collision now. The server fails to start because there are 2 IndexDAOs provided. There is a Configuration condition that does not appear to be working either.
But, this makes the correct assumption that if you're including ES7, then you intend to use ES7 as your indexing mechanism.
CC @bjpirt
Pull Request type
[ X ] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes (Please run ./gradlew generateLock saveLock to refresh dependencies)
The addition of Postgres as an IndexDAO made it so that if you use Conductor core as your deployment mechanism, and you use Postgres and ES7, there is a collision now. The server fails to start because there are 2 IndexDAOs provided. There is a Configuration condition that does not appear to be working either.
But, this makes the correct assumption that if you're including ES7, then you intend to use ES7 as your indexing mechanism.
CC @bjpirt
Pull Request type
./gradlew generateLock saveLockto refresh dependencies)