InvalidPersistentPropertyPath with @Version [DATAMONGO-2174]

[spring-projects-issues]

Kency Kurian opened DATAMONGO-2174 and commented

Hello, 

I got this issue after upgrading from spring boot 2.0.0 to spring boot 2.1.1 (ie. spring data - Kay SR5 to Lovelace SR3). After a lot of trials to reproduce it in a new project, found that if the @Version is commented out in Report.java([git hub link|https://github.com/KencyK/spring-boot-migration]) the test passes. 

 

---

Affects: 2.1.3 (Lovelace SR3)

Reference URL: https://stackoverflow.com/questions/53987706/spring-mongo-invalidpersistentpropertypath-with-version

Issue Links:

• DATAMONGO-2168 Using className as type hint field name with versioned entities fails with InvalidPersistentPropertyPath in UpdateMapper

Referenced from: pull request #633, and commits 273088b, 65e0d18, 161a983, 0324ae6, 592b8b8

Backported to: 2.1.4 (Lovelace SR4), 2.0.13 (Kay SR13)

[spring-projects-issues]

Mark Paluch commented

This issue is somewhat related to DATAMONGO-2168 as the problem is caused by double-mapping of the update document

[spring-projects-issues]

Mark Paluch commented

To fix the double-mapping we would need to introduce another doUpdate method that performs just the updating portion and leaves mapping and version increment to its caller