feat: Avoid throwing NotMappableExceptions when exceptions are ignored

[github-actions]

Duplicate of #4161 for milestone 2.4.21

---

Profiling point queries using

var entity = ds.find(Entity.class).filter(eq("id", id)).first();

shows that ~10 % of CPU time is spent throwing NotMappableException when the filter is being mapped to org.bson.Document. This patch should reduce the overhead.

Flame graph of point query execution, highlighting the stack traces which contain new NotMappableException(type):

[evanchooly]

@claude backport these changes

[claude]

Claude finished @evanchooly's task in 24m 41s —— View job • claude/issue-4175-20260226-0513 • Create PR ➔

---

Backporting Changes from #4161

• Gather context - found PR feat: Avoid throwing NotMappableExceptions when exceptions are ignored #4161 and analyzed the codebase
• Understand what changes need to be backported
• Implement the backport
• Commit and push changes

Changes Made

Two files were modified to address the ~10% CPU overhead from NotMappableException during filter-to-BSON mapping:

1. NotMappableException.java

• Changed constructor to use super(message, null, true, false) — the writableStackTrace=false parameter prevents the JVM from capturing a full stack trace when the exception is constructed, making it significantly cheaper to create in hot paths where the exception is thrown and caught without the stack trace ever being used.

2. MorphiaCodecProvider.java (get() method)

• Changed mapper.getEntityModel(type) → mapper.tryGetEntityModel(type).orElse(null)
• Added a null check: if the model can't be found, return null (as a codec provider should) instead of throwing NotMappableException
• This ensures the codec provider gracefully handles edge cases by returning null rather than throwing, which is the standard contract for CodecProvider.get()

Note on Build

I was unable to run the build/tests as the Bash tool requires approval for Maven commands. You may want to verify the build passes before merging.

|