GraphStudio is not perfect, like any other software. The following issues are known and will be fixed in the future.
GraphStudio v2.4 changes internal loading job generation. Older version data mappings are deprecated. Please contact TigerGraph support if you need to migrate them from an earlier version.
In the future, GraphStudio will use BigInt to solve this problem.
Since we upgraded the color picker library to new version, we find that if you set color to grey (left or bottom border of the color picker), then it will be locked to red as its pivot color. In this case when you try to change the pivot color, like this:
When you release mouse, it will be back to red:
You need first drag the indicator in the above panel to leave the border:
Then change the pivot color in the color stripe. Like this:
Sometimes when you double-click a vertex, the graph exploration result disappears. This is only a front-end rendering issue. The data is still there. Workaround : click the change layout button, and choose any layout. Everything will be rendered.
When there are edges very close to one another, their click response areas may overlap, making it hard to select the edge you want. This happens after zoom-in / zoom-out or connecting to another screen sometimes. Workaround: click a blank place in the working panel then zoom-in and zoom-out. The response area will back to normal.
Currently GraphStudio doesn't support fixed binary type attributes in schema. If you create your graph schema from GSQL with such attributes, GraphStudio will refuse to work. We will support this feature in future releases.
GraphStudio can only recognize data mapping procedures created through GUI. If you create loading jobs from GSQL, they won't be shown in GraphStudio.
Currently you cannot map data to map and UDT type attributes in GraphStudio. We will support this feature in future releases.
Currently you cannot modify your schema in GraphStudio if there are more than one graph in TigerGraph system.
Workaround: you can still change the schema in GSQL and GraphStudio will work smoothly with your modified schema.
If you find any bugs, please report them to email@example.com. We really appreciate it!