You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Pipes does not allow to add or delete the properties on the entity block if it is used in current graph.
It will take lots of extra work to remove the current used entity block, then add the updated entity block. All the mapping will be lost.
We are the customer of MarkLogic and heavily using Pipes.
Often we need to update the entity definitions later on and it is very difficult to do it in Pipes because of the above reason. Describe the solution you'd like
It will be good to be able the update the entity block even it is used in the current graph.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Chunyu01
changed the title
[FEATURE]Able to edit the Entity Block even it is used in current graph
[FEATURE]Able to update the Entity Block even it is used in current graph
Oct 1, 2020
If the properties in the entity definition are renamed, there's no way to "capture" this fact and preserve the mapping so the mapping to renamed properties would be lost in the Pipes graph
It would be possible to handle the case of adding / removing properties
The question is at which moment should Pipes detect the change. It would be possible to do this check on graph load and ask the user if they want to update the entities at that moment.
If the properties in the entity definition are renamed, there's no way to "capture" this fact and preserve the mapping so the mapping to renamed properties would be lost in the Pipes graph
It would be possible to handle the case of adding / removing properties
The question is at which moment should Pipes detect the change. It would be possible to do this check on graph load and ask the user if they want to update the entities at that moment.
It will be fine with above point 1 and 2.
Point 3, we are not fussy about the method, but just would like to have a way to be able to update the current entity block.
Is your feature request related to a problem? Please describe.
Pipes does not allow to add or delete the properties on the entity block if it is used in current graph.
It will take lots of extra work to remove the current used entity block, then add the updated entity block. All the mapping will be lost.
We are the customer of MarkLogic and heavily using Pipes.
Often we need to update the entity definitions later on and it is very difficult to do it in Pipes because of the above reason.
Describe the solution you'd like
It will be good to be able the update the entity block even it is used in the current graph.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: