KNOX-2995 - Support json parsing NaN values

[upczsh]

What changes were proposed in this pull request?

Implemented the changes I listed in KNOX-2995:

• Solve the problem of page parsing failure when Json returns NaN value.

Added JsonReadFeature.ALLOW_NON_NUMERIC_NUMBERS.mappedFeature() to support this feature

I click on the page with return json and the content of Resopnse is empty. like this :

Checking the gateway.log log shows the following error message.

The display results after my repair are as follows：

How was this patch tested?

I have added test cases. You can run the test cases to see if they are successful.
Run JsonFilterReaderTest.testNaN() function.
Or look at the actual problems I encountered above to test.

[upczsh]

you can see this issuse: KNOX-2995

[smolnar82]

@upczsh - could you please be more verbose on the PR description above?
We do provide a template OOTB, which we require to be filled in when someone opens a PR.
See this one as a recent sample: #826

[smolnar82]

Why don't you add this feature when creating the factory in line 69?
Moreover, the referenced feature has been deprecated since 2.10 according to Jackson docs (we use 2.11.4 in Knox already):

        /**
         * Feature that allows parser to recognize set of
         * "Not-a-Number" (NaN) tokens as legal floating number
         * values (similar to how many other data formats and
         * programming language source code allows it).
         * Specific subset contains values that
         * <a href="http://www.w3.org/TR/xmlschema-2/">XML Schema</a>
         * (see section 3.2.4.1, Lexical Representation)
         * allows (tokens are quoted contents, not including quotes):
         *<ul>
         *  <li>"INF" (for positive infinity), as well as alias of "Infinity"
         *  <li>"-INF" (for negative infinity), alias "-Infinity"
         *  <li>"NaN" (for other not-a-numbers, like result of division by zero)
         *</ul>
         *<p>
         * Since JSON specification does not allow use of such values,
         * this is a non-standard feature, and as such disabled by default.
          *
          * @deprecated Since 2.10 use {@link com.fasterxml.jackson.core.json.JsonReadFeature#ALLOW_NON_NUMERIC_NUMBERS} instead
          */
         @Deprecated
         ALLOW_NON_NUMERIC_NUMBERS(false),

[upczsh]

@smolnar82 Thanks for your guidance, I have used JsonReadFeature.ALLOW_NON_NUMERIC_NUMBERS instead of the deprecated JsonParser.Feature.ALLOW_NON_NUMERIC_NUMBERS.
On the other hand, the reason for not adding it on line 69 is that this setting is the content of parse, and other json parse configurations may be enabled in the future, so I wrote a separate method.

[smolnar82]

LGTM

[smolnar82]

@upczsh - could you please be more verbose on the PR description above?
We do provide a template OOTB, which we require to be filled in when someone opens a PR.
See this one as a recent sample: #826

[smolnar82]

@upczsh - We are about to release Knox v2.1.0 and I'd like to include your change.
However, I cannot merge it until you update the PR description as requested above.
Thanks!

[upczsh]

@upczsh - We are about to release Knox v2.1.0 and I'd like to include your change. However, I cannot merge it until you update the PR description as requested above. Thanks!

terribly sorry!!! I have updated the PR description.It's my honor to contribute!