Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ambiguous field mapping detected #4250

Open
kassepro1 opened this issue Jun 28, 2024 · 0 comments
Open

Ambiguous field mapping detected #4250

kassepro1 opened this issue Jun 28, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@kassepro1
Copy link

Describe the bug
Ambiguous field mapping detected; Both protected volatile int com.ibm.fhir.model.type.Element.hashCode and private volatile int com.ibm.fhir.model.type.code.IdentifierUse.hashCode
Environment
Java 21
Spring boot 3..3.3
Mongo db

  1. See error
    Ambiguous field mapping detected; Both protected volatile int com.ibm.fhir.model.type.Element.hashCode and private volatile int com.ibm.fhir.model.type.code.IdentifierUse.hashCode
    Expected behavior
    A clear and concise description of what you expected to happen.

Additional context
Caused by: org.springframework.data.mapping.MappingException: Ambiguous field mapping detected; Both protected volatile int com.ibm.fhir.model.type.Element.hashCode and private volatile int com.ibm.fhir.model.type.code.IdentifierUse.hashCode map to the same field name hashCode; Disambiguate using @field annotation
at org.springframework.data.mongodb.core.mapping.BasicMongoPersistentEntity$AssertFieldNameUniquenessHandler.assertUniqueness(BasicMongoPersistentEntity.java:347) ~[spring-data-mongodb-4.3.0.jar:4.3.0]

@kassepro1 kassepro1 added the bug Something isn't working label Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant