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
Currently the situation in the spi of the federated catalog is that you only can add nodes to your directory.
But dataspaces can be agile, so mabey some participant doesnt wanna stay in the dataspace or you just dont wanna crawl him. So mabey a new feature about deleting a node out of the FederatedCacheNodeDirectory could be very useful.
That the topic to delete a participant out of a federated catalog with cached data will be probably more complex then just deleting the node out of this directory, as i already tested this quick solution, but i think this feature will be needed.
What do you think about this and what steps need to happen to realize this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently the situation in the spi of the federated catalog is that you only can add nodes to your directory.
But dataspaces can be agile, so mabey some participant doesnt wanna stay in the dataspace or you just dont wanna crawl him. So mabey a new feature about deleting a node out of the FederatedCacheNodeDirectory could be very useful.
That the topic to delete a participant out of a federated catalog with cached data will be probably more complex then just deleting the node out of this directory, as i already tested this quick solution, but i think this feature will be needed.
What do you think about this and what steps need to happen to realize this?
Beta Was this translation helpful? Give feedback.
All reactions