[ISSUE #8879] reduce seach key times in method,to import performance

[ChineseTony]

Which Issue(s) This PR Fixes

Fixes #8879

Brief Description

How Did You Test This Change?

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.54%. Comparing base (dd62ed0) to head (f4eb1f0).
Report is 3 commits behind head on develop.

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #8880      +/-   ##
=============================================
- Coverage      47.61%   47.54%   -0.08%     
+ Complexity     11752    11733      -19     
=============================================
  Files           1304     1304              
  Lines          91043    91037       -6     
  Branches       11675    11673       -2     
=============================================
- Hits           43354    43280      -74     
- Misses         42352    42414      +62     
- Partials        5337     5343       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[qianye1001]

If refactoring this part of the code, it might be simpler to use ConcurrentHashMap instead of HashMap.

[ChineseTony]

ok, I will chage this code

   private boolean isFieldNullable(Field field) {
        return ConcurrentHashMapUtils.computeIfAbsent(NULLABLE_FIELD_CACHE, field, input -> {
            Annotation annotation = input.getAnnotation(CFNotNull.class);
            return annotation == null;
        });
    }

[RongtongJin]

Could you provide specific performance improvement data using tests? It would be better to use tests to also verify correctness.

[ChineseTony]

ok,thanks ,but isFieldNullable function can use temp variable to save and reture the value ,Don't need search key twice