[
https://issues.apache.org/jira/browse/FLINK-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202754#comment-15202754
]
Zoltán Zvara commented on FLINK-3624:
-------------------------------------
I'd introduce a versioning for the REST API as well, since it is absent
currently. Maybe it would solve the problem by rerouting the default requests
to {{/v1}} implicitly, while new applications should use {{v2}}.
> Use camelCase naming of JSON attributes generated by the REST API instead of
> dash
> ---------------------------------------------------------------------------------
>
> Key: FLINK-3624
> URL: https://issues.apache.org/jira/browse/FLINK-3624
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Reporter: Zoltán Zvara
>
> It forces inconvenient attribute access in some scripting languages, for
> example JavaScript (which includes the JSON (JavaScript Object Notation)
> specification) and against the widely used and accepted camelCase style.
> Example:
> {code:title=http://localhost:8081/jobs/8510e306a40e9266fcc6e0989a258a01/vertices|borderStyle=solid}
> {
> jid: "8510e306a40e9266fcc6e0989a258a01",
> name: "Socket Window WordCount",
> isStoppable: false,
> state: "RUNNING",
> start-time: 1458147070328,
> end-time: -1,
> duration: 418389,
> now: 1458147488717,
> {code}
> {{isStoppable}} is camelCase, {{start-time}} is not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
