Allow modelKey to be a nested field

I am trying to migrate my existing project from lounge to ottoman, but my existing project stores type in a meta object. Since this is a nested field, I’m not currently able to set modelKey to meta.type without getting a Couchbase InternalServerFailureError. I would issue a pull-request, but I would need some help on where to get started with this change. I’m not sure how difficult it would be. Thanks.

[doceme]

Hi @AV25242. Yes, we are currently in the process of migrating from lounge to ottoman using version 2.2.0. We haven’t hit any show-stoppers yet. Thanks!

[doceme]

Hello @AV25242, thanks for your consideration of this request. I understand that ottoman creates a GSI to handle the model.find operations and I’m okay with that. We currently have a GSI for meta.type lookups that we created, but I imagine it would get replaced with the ottoman created one after the transition. I am completely okay with modelKey being immutable and would expect it to be. I think limiting the nesting depth of the modelKey is perfectly reasonable. We don’t currently have any plans to migrate away from using the _default scope/collection, but I believe I understand the implications if we do down the road.