Why is the TransformationGraph a singlton?
I would like to use Clover in an environment where ther might be several (many?) graphs/jobs might be running at the same time.
The jobs would be independent of each other as the transform unrelated data.
Is this kind of setup possible?
could you tell me when you will change TransformationGraph from Singelton to normal.
Because my project require more than one graph run at a same time.
Hi!
Do you have any idea about when that would be?
Or, on the other hand, do you have any idea who much work it would be to lift that constraint? I would be willing to contribute, but as i (at the moment) have no idea about the complexity of that task, i don’t know if that would be feasable for a “newbie” to clover.
After a first glance at the code, i got the impression that it actually might be not too comples (but i might have missed a/the cruxial point)
Hi !
The singleton is there for historical reason. We plan to lift this constrain, but it will take some time.
Davod.
Hi
It is in our plans for following month or so.
Changing it is not so difficult but more it is complex/ It requires changes at several places. Some code is already capable of lifting the singleton pattern, some not.
The most difficult thing is that changing from singleton to normal object would definitely break some user transformation code - especially that which is referencing lookups or sequences registred with graph.
However, if you decide to start the transition, let me know - I could provide you with some instructions where to change things.
David.
Hello !
The code is already in the repository. With the new release - planned 1.9 - the singleton patter on graph will be history.