Skip to content
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

have the endpoint configuration at general.json #31

Closed
andimou opened this issue May 10, 2013 · 3 comments
Closed

have the endpoint configuration at general.json #31

andimou opened this issue May 10, 2013 · 3 comments

Comments

@andimou
Copy link
Member

andimou commented May 10, 2013

Hi,
it would be nice to have the details about the endpoint configured at the general.json instead of specifying them at the loader.

@andimou
Copy link
Member Author

andimou commented Aug 7, 2013

@coreation, do you think that it would make sense to have the (default) endpoint configuration at the general.json rather than at the loader/job?

@coreation
Copy link
Member

Not at the moment since the general.json is still a general configuration, and this is specifically done for jobs that load data into a triple store. There are shortterm plans to create loaders that put triples into phyiscal files as well. We're planning on making a system that loads configurations dynamically from the installed packages in your tdt/start. So for now, I wouldn't recommend doing this :).

@andimou
Copy link
Member Author

andimou commented Aug 7, 2013

ok, but by the time that someone decides to install a triplestore next to his/her tdt/input, it wouldn't harm to be able to have a general configuration for all his/her loaders of type:RDF. Namely, an optional configuration only for those who use tdt/input in combination with a triplestore.

@andimou andimou closed this as completed Aug 7, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants