EmbeddableDocumentStore Raven.Bundles.UniqueConstraints not picked up from plugin folder

[Valeriob]

After spending much time trying to understand why this is not working anymore i reached this conclusion : 

Test project with RavenDB 3.0 client and server and Raven.Bundles.UniqueConstraints.dll in the .\Plugins directory all works fine.

Upgraded to RavenDB 3.5 client and server, DocumentDatabase.PutTriggers collections is empty.

Digging deeper looks like that InMemoryRavenConfiguration.Catalog has loaded Raven.Bundles.UniqueConstraints.dll  correctly, but InMemoryRavenConfigurationFilterActiveBundles excludes this from completing the MEF dependency, so the collection PutTriggers is not loaded correctly.

Is it a wanted behavior or a bug ? In the first case is better to document it because i spent a lot of time to find out what was happening. I hope the RavenDb Server will still load the plugin from the Plugins folder

From what i could see this happens also in the normal DatabaseVersion aswell.

Thanks,

Valerio

[Tal Weiss]

You're missing "UniqueConstraints" in your active bundle settings

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Hibernating Rhinos Ltd  

Tal Weiss l Core Team Developer l Mobile:+972-54-802-4849

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811l Skype: talweiss1982

RavenDB paving the way to "Data Made Simple" http://ravendb.net/ 

[Valeriob]

This is a breaking change since RC (tested on 35165) ! 

Very very dangerous, i'm so lucky to have seen this in time, because we are testing RC and we are about to put 3.5 in production, if i had not perused this problem i would encountered serious data corruption in production upgrading from RC to RTM !

Please do not do it again :(

Thanks

Valerio

On Thursday, November 10, 2016 at 3:15:41 PM UTC+1, Tal Weiss wrote:

You're missing "UniqueConstraints" in your active bundle settings

On Thu, Nov 10, 2016 at 4:08 PM, Valeriob <vale...@gmail.com> wrote:

After spending much time trying to understand why this is not working anymore i reached this conclusion : 

Test project with RavenDB 3.0 client and server and Raven.Bundles.UniqueConstraints.dll in the .\Plugins directory all works fine.

Upgraded to RavenDB 3.5 client and server, DocumentDatabase.PutTriggers collections is empty.

Digging deeper looks like that InMemoryRavenConfiguration.Catalog has loaded Raven.Bundles.UniqueConstraints.dll  correctly, but InMemoryRavenConfigurationFilterActiveBundles excludes this from completing the MEF dependency, so the collection PutTriggers is not loaded correctly.

Is it a wanted behavior or a bug ? In the first case is better to document it because i spent a lot of time to find out what was happening. I hope the RavenDb Server will still load the plugin from the Plugins folder

From what i could see this happens also in the normal DatabaseVersion aswell.

Thanks,

Valerio

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[David Boike]

The magic string is actually "Unique Constraints" with a space. Here's an example:

documentStore = new EmbeddableDocumentStore

{

DataDirectory = "Data",

UseEmbeddedHttpServer = true,

Configuration =

{

Port = 32076,

PluginsDirectory = "Plugins",

HostName = "localhost",

Settings =

{

{ "Raven/ActiveBundles", "Unique Constraints" }

}

},

};