[
https://issues.apache.org/jira/browse/NIFI-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903754#comment-15903754
]
Aldrin Piri commented on NIFI-3546:
-----------------------------------
Hey [~ggwizdz1],
This is occurring in the nifi-standard-content-viewer. More specifically, I am
assuming this is within the codemirror JS plugin that we use to do syntax
highlighting/formatting. I would imagine that the JS is converting these
numbers into the changed format because it also identifies the values as
numbers instead of treating them as a raw string. To reproduce, generating a
flowfile with the above data, performing an update attribute to mark its
mime.type as application/json and then scope out the associated content in the
viewer.
> JSON Formatted view of content will convert numbers to Scientific Format
> ------------------------------------------------------------------------
>
> Key: NIFI-3546
> URL: https://issues.apache.org/jira/browse/NIFI-3546
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.1.1
> Reporter: Aldrin Piri
> Priority: Trivial
>
> When using the content viewer, I was evaluating some data that was in JSON
> format. In the original view, I had the data as expected:
> {code}
> {"timestamp": 1488474750276.346, "name": "longitude", "value": -83.23728}
> {code}
> However, when switching to the formatted view, the timestamp is converted
> {code}
> {
> "timestamp" : 1.488474750276346E12,
> "name" : "longitude",
> "value" : -83.23728
> }
> {code}
> This can be confusing as it may seem as though the content format is
> different than anticipated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
