[
https://issues.apache.org/jira/browse/NIFI-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888686#comment-17888686
]
Pierre Villard commented on NIFI-13864:
---------------------------------------
Can you share more details?
Is the problematic scientific notation right after the InvokeHTTP? Or is it
after another processor? If another processor, which one? Is this processor
using record reader/writer? If yes, which record reader/writer? and with which
configuration?
Ideally, if you could share a JSON flow definition made of something like
GenerateFlowFile -> ConvertRecord that reproduces the issue, this would be
helpful.
Thanks
> scientific notation issue of invokeHTTP in returned json -- NiFi2.0-M4
> ----------------------------------------------------------------------
>
> Key: NIFI-13864
> URL: https://issues.apache.org/jira/browse/NIFI-13864
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.0.0-M4
> Environment: Rocky9, NiFi2.0.0-M4
> Reporter: Tao Li
> Priority: Major
> Attachments: image (2).png, image (3).png
>
>
> seems M4 still has scientific notation issue. invokeHTTP returned json from
> API. number in the json was converted to e-notation by processor.
> we tried swagger, it return correct value. the image(2).png -- invokeHTTP,
> image(3).png -- swagger.
> Is there any workaround way to fix this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
