With the addition of the EventKey (see #1916), JacksonEvent always creates a JacksonEventKey in order to use the same code for all paths. However, when put/delete calls are made with a String key, JacksonEvent does not need the JSON Pointer. But, it is created anyway. This adds more work to the put/delete calls that have not yet migrated to the String version.
This fixes regression by adding a lazy initialization option when used in JacksonEvent. We should not be lazy when used with the EventKeyFactory since we may lose some up-front validations.
Issues Resolved
N/A
Check List
[ ] New functionality includes testing.
[ ] New functionality has a documentation issue. Please link to it in this PR.
[ ] New functionality has javadoc added
[ ] Commits are signed with a real name per the DCO
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.
Description
With the addition of the
EventKey(see #1916),JacksonEventalways creates aJacksonEventKeyin order to use the same code for all paths. However, when put/delete calls are made with a String key,JacksonEventdoes not need the JSON Pointer. But, it is created anyway. This adds more work to the put/delete calls that have not yet migrated to the String version.This fixes regression by adding a lazy initialization option when used in
JacksonEvent. We should not be lazy when used with theEventKeyFactorysince we may lose some up-front validations.Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check here.