LynxKite v1.4.3 Release Notes

    • History editing improvements. Operations with problems (such as importing a file that no longer exists) can be edited now. Long histories can now be edited without problem. The UI has been revised a bit. (The Validate button has been removed.)
    • Switching to Spark 1.4.0.
    • New operation Copy graph into a segmentation can import the project as its own segmentation and create edges between the original vertices and their corresponding vertices in the segmentation.
    • Operations Degree, Aggregate on neighbors, and Weighted aggregate on neighbors can now also make calculations directly on unique neighboring vertices (that is, regardless of the number of edges between the vertices).
    • For neighbor aggregations and degree the meaning of "symmetric" edges makes more sense now: the number of symmetric edges between A and B is now understood as max(number of edgex A->B, number of edges B->A)
    • EC2 Kite instances now listen on port 4044 (instead of 5080 before).
    • Smoke test script added: when you install a new Kite instance, you can run kite_xxx/tools/daily_test.sh to see if everything is set up correctly.
    • Fixed saving workflows. The save dialog didn't actually show in prod deployments.
    • Fixed a bug where we didn't close some files when we didn't need them which caused s3 lockups.
    • Appending data to an existing DB table is not supported anymore (as it's dangerous if done accidentally). In other words, you can only export to a DB by creating a new table.
    • Removed the SQL dump option in file export operations. The only supported output format is CSV now.
    • Improved watchdog to detect a wider range of potential problems.
    • Fixed bug: editing the history now causes project reload.
    • Fixed a bug where vertices became frozen when attributes were visualized on them.
    • Fixed a bug where cross edges between project and segmentation could be broken for certain operations.