[
https://issues.apache.org/jira/browse/HDFS-8779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708973#comment-14708973
]
Walter Su commented on HDFS-8779:
---------------------------------
Seems like we run out of options:
1. change JsonString from server side. (01, 02 patch)
2. hack JsonString from client side. (03 patch)
3. hack Json Parser(04 patch) (It's impossible to hack browser' Json Parser.
You have to hack a parser library.)
4. hack JavaScript Engine.
#1 is the best way but is incompatible. I think server side has a bad design
in the first place. We have to add a workaround at client side, just like
HDFS-8388. I think #3,#4 is very inappropriate. So, [~wheat9]. could you
reconsider #2 approach again? in 03 patch.
> WebUI can't display randomly generated block ID
> -----------------------------------------------
>
> Key: HDFS-8779
> URL: https://issues.apache.org/jira/browse/HDFS-8779
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Reporter: Walter Su
> Assignee: Walter Su
> Priority: Minor
> Attachments: HDFS-8779.01.patch, HDFS-8779.02.patch,
> HDFS-8779.03.patch, HDFS-8779.04.patch, after-02-patch.png, before.png,
> patch-to-json-parse.txt
>
>
> Old release use randomly generated block ID(HDFS-4645).
> max value of Long in Java is 2^63-1
> max value of -number-(*integer*) in Javascript is 2^53-1. ( See
> [Link|https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER])
> Which means almost every randomly generated block ID exceeds MAX_SAFE_INTEGER.
> A integer which exceeds MAX_SAFE_INTEGER cannot be represented in Javascript.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
