The edges from the graph driver will only be able to be derived from edge tables, removing the ability to use 'fieldToField' and 'fieldToId' configurations. Those methods:
were never used in practice
created extensive complications in the code and configuration files,
any case where that kind of linkage would be needed, it was easier just to put the logic in the plug in and have it create an edge table
Additionally, this PR will also remove the JSON path based description of the 'toField' and 'fromField'. It was overly complicated, not user friendly, and never used. Again, any cases were a sub field needs to be used to create an edge, it is better to put the logic in the plugin, rather then try and predict every possible scenario in the engine.
The edges from the graph driver will only be able to be derived from edge tables, removing the ability to use 'fieldToField' and 'fieldToId' configurations. Those methods:
Additionally, this PR will also remove the JSON path based description of the 'toField' and 'fromField'. It was overly complicated, not user friendly, and never used. Again, any cases were a sub field needs to be used to create an edge, it is better to put the logic in the plugin, rather then try and predict every possible scenario in the engine.