QueryMapper should be configurable for MongoTemplate [DATAMONGO-1966]

[spring-projects-issues]

Nick Balkissoon opened DATAMONGO-1966 and commented

We should allow QueryMapper to be configurable if someone wants to extend the functionality of QueryMapper.  I have a use case where I am transforming data before persisting it to Mongo, and so when I'm querying I'd like to do the same transformation to queries so that our data transformation is transparent to anyone querying the db.  So QueryMapper should be exposed for DI or shouldn't be final so we can override the default if we extend MongoTemplate.

this.queryMapper = new QueryMapper(this.mongoConverter);

Curious to hear people's thoughts on this

---

No further details from DATAMONGO-1966

[spring-projects-issues]

Oliver Drotbohm commented

The way data is transformed is not handled by QueryMapper but the converter. You can register custom Converter implementations to tweak the reading and writing for a particular type.

It might be worth describing the actual use case you have in mind in more detail, before we discuss which parts of the code needs to change. Note, that usually things that are not tweakable from the outside are designed that way for a reason – which I am happy to share on request – and simple request to make it configurable is not going to cut it

[spring-projects-issues]

Nick Balkissoon commented

Thanks for the quick response. Our particular use case is we have encrypted fields that when we persist mongo we are transforming into this encrypted object with two values: encryptedValue, and hash. The hash is what i will search on. So say lastName is encrypted, then when i search on {lastName : “foo”} id like to seamlessly transform this query to {lastName.hash : “thehashoffoo”}

[spring-projects-issues]

Nick Balkissoon commented

Took a second look and doesn't look like this would be possible using Converters

[spring-projects-issues]

Nick Balkissoon commented

Does what I'm proposing seem like  viable solution to my problem?  If so, I can submit a PR

[spring-projects-issues]

danielandersson commented

Any updates on this Oliver Drotbohm?

To give you another example where a configurable QueryMapper would be nifty, I'm facing a situation where all entities in MongoDB belongs to an organisation and I would like to include organisationId (fetched from the RequestContext) in every query towards MongoDB. That would be possible if I could just wrap QueryMapper.getMappedObject.