-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Direct functionality between datastores #2144
Comments
The current workaround is to use exporter and importer back-to-back. Another option is to use API functions. We have to think how we develop both merger and data transformer going forward, but it has to wait until we finish v0.8 changes. |
You can currently filter parameter values and entities by scenario and tool filters. |
I definitely agree we need more datastore to datastore functionality. |
This option seems the most proper way to go. Can we allow filtering by alternative as well? @soininen |
The icon "data transformer" can be confusing as it only works along with some "executable" icons. It might fit better in the link as the filter does. |
Alternative filtering is coming... We don't seem to have an issue about it though. |
It would be nice if the magic "Merger" could filter out a subset from its upstream datastore (entities, parameters, etc.) as per users' request. With that, the Merger becomes a generic tunnel for data transmission between datastores, which we haven't had yet.
The text was updated successfully, but these errors were encountered: