[tidoop-hadoop-ext] Infer the CKAN endpoint(s) from the input/output URLs

telefonicaid / fiware-tidoop

Hadoop extensions for CKAN, STH...

GNU Affero General Public License v3.0

2 stars 1 forks source link

[tidoop-hadoop-ext] Infer the CKAN endpoint(s) from the input/output URLs #8

Open frbattid opened 9 years ago

frbattid commented 9 years ago

Instead of passing an explicit single CKAN endpoint, by giving the host, the port and specifying if SSL is enabled, infer such information form the input and output URLs. This has several advantages:

The CKAN supporting the input data may be different to the CKAN supporting the output data.
The input data may be located at several different CKAN instnaces.

Effort: 3 man day

frbattid commented 9 years ago

When implementing this issue, the different CKAN API keys must be stored in a secure file. Possible format: a properties file containing (ip, api key) pairs and (fqdn, api key) pairs:

<ip>=<api_key>
<fqdn>=<api_key>