I like the idea of some sort of remote ImportData, but I feel like we would
still be better off uploading/configuring it in the createContext step.
> So, what about a new type of ImportData, tentatively named FetchData (feel
> free to suggest a better name),
>
How about RemoteData, or OnlineData?
> No tasks are created during the creation, when run happens, the importer
> checks for FetchData,
> if available, it will fetch it, create a File or Directory import data,
> create the tasks, attach
> the transformations
>
Rather than have this occur in "run", I feel like this step would make
more sense in "createContext". I'm not sure about the REST API, but the
Importer code does have a createContextAsync method, so this would still
support asynchronous behavior.
If this option also gets pulled into the importer UI, it would make for a
clearer user experience if you could see what is being imported before you
import it
So I feel like this new type of ImportData is a good idea, but we should
still try to upload it and create tasks in the createContext step. If the
existing REST API does not support asynchronosly creating the context, then
this is functionality that should be added, especially since there is
already asynchronous support in the Importer code.
Torben
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
