[ https://issues.apache.org/jira/browse/GRIFFIN-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663238#comment-16663238 ]
ASF GitHub Bot commented on GRIFFIN-203: ---------------------------------------- GitHub user gavlyukovskiy opened a pull request: https://github.com/apache/incubator-griffin/pull/446 [GRIFFIN-203] "Plaintext mode" for measure creation Created json/yaml measure creation flow: ![2018-10-24 21 41 44](https://user-images.githubusercontent.com/15277543/47476643-4aa37680-d7d6-11e8-9488-fe2e247617a1.gif) Added ability to view measure as yaml: ![2018-10-24 21 42 23](https://user-images.githubusercontent.com/15277543/47476652-4d9e6700-d7d6-11e8-86f3-f35fdc44dda1.gif) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gavlyukovskiy/incubator-griffin raw-measures Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-griffin/pull/446.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #446 ---- commit e07a7e169b18f67fd5661ab085524c3bf9206c8b Author: Arthur Gavlyukovskiy <agavlyukovskiy@...> Date: 2018-10-25T04:53:01Z [GRIFFIN-203] "Plaintext mode" for measure creation Created json/yaml measure creation flow Added ability to view measure as yaml ---- > "Plaintext mode" for measure creation > ------------------------------------- > > Key: GRIFFIN-203 > URL: https://issues.apache.org/jira/browse/GRIFFIN-203 > Project: Griffin (Incubating) > Issue Type: New Feature > Reporter: Nikolay Sokolov > Priority: Major > > Creating custom rules from API might be cumbersome -- body should be prepared > outside of UI, and then submitted using HTTP call. To make user's life > easier, it would be useful to allow measure creation by editing JSON directly > on UI. Viewing side of this feature would be GRIFFIN-202. > Also, experience-wise, JSON might not be the best option for complex > spark-sql rules. Possible solution to that would be allowing to write YAML > representation instead of JSON, and then either submitting YAML body or > converting from YAML to JSON on UI side before submission. -- This message was sent by Atlassian JIRA (v7.6.3#76005)