Alex Ott created ZEPPELIN-4793:
----------------------------------

             Summary: Can't visualize graph data in Zeppelin
                 Key: ZEPPELIN-4793
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4793
             Project: Zeppelin
          Issue Type: Bug
    Affects Versions: 0.9.0
            Reporter: Alex Ott


When trying to answer [following question on 
SO|https://stackoverflow.com/questions/61570214/how-to-visualize-graph-with-network-in-zeppelin],
 I've found a problem with visualization of network data, although generated 
data looks correct. It even don't work with following graph, although work fine 
if I don't specify {{edges}}:
{noformat}
%spark

print(s"""
%network {
"nodes": [{"id":"a","label":"person","data":{"name":"Alice","age":34}}, 
{"id":"b","label":"person","data":{"name":"Bob","age":36}}, 
{"id":"c","label":"person","data":{"name":"Charlie","age":30}}, 
{"id":"d","label":"person","data":{"name":"David","age":29}}, 
{"id":"e","label":"person","data":{"name":"Esther","age":32}}, 
{"id":"f","label":"person","data":{"name":"Fanny","age":36}}, 
{"id":"g","label":"person","data":{"name":"Gabby","age":60}}],
"edges": [{"source":"a", "target":"b", "id":"ab"}]
}
""")
{noformat}
In web console shows following error:
{noformat}
Graph drawing error  TypeError: "d.source is undefined"
    start vendor.f209b9124a2273d7.js:97
    value visualization-d3network.js:149
    l result.controller.js:684
    V result.controller.js:231
    oe result.controller.js:730
    renderDefaultDisplay result.controller.js:347
    n result.controller.js:226
    j vendor.f209b9124a2273d7.js:38
    f vendor.f209b9124a2273d7.js:36
    c vendor.f209b9124a2273d7.js:36
result.controller.js:701:18
    l result.controller.js:701
    V result.controller.js:231
    oe result.controller.js:730
    renderDefaultDisplay result.controller.js:347
    n result.controller.js:226
    j vendor.f209b9124a2273d7.js:38
    f vendor.f209b9124a2273d7.js:36
    c vendor.f209b9124a2273d7.js:36
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to