Thanks everybody for the ideas here and sent to me offline. Here is a list of
the suggestions in no particular order:
* ETL is a proper term here, so this shouldn't be the reason for renaming
* CTP - copy-transform-paste (which coincidentally evoked an analogy with the
tedious process of copying
I don't think that ETL is strictly devoted to data warehouse. We use ETL
transforms from and to our database to drive other processes including
external vendors. So ETL in our case is far removed from the warehouse.
Now, I will admit that data warehouse functions do an awful lot of ETL but
the need
Interesting project.
I agree with Ari. Independent that the target would not be a analytical
databases, LinkETL is itself a ETL tool that fits perfectly in the data
mediation, following wikipedia definition for ETL[3]:
"As such, ETL is a key process to bring all the data together in a
standard,
> I have a friend who does ETL and it sounds like exactly the sort of thing
> he'd use. Why is ETL not a suitable choice?
ETL as a process is very close to what the product does (the sequence of
operations can be represented as extract/transform/load at the higher level,
although not all algori
On 12/06/2015 12:48am, Andrus Adamchik wrote:
> Now we realized that "ETL" in the name is wrong, as it has data warehouse
> connotations. So looking for another name for this project. All the most
> obvious names (e.g. 'datapump") are already taken by various commercial and
> open source project
Sorry for a somewhat OT post.
There's this fairly new Cayenne-based project called LinkETL [1]. It is a
model-driven dynamically-configurable framework to acquire data from external
sources and save it in your database. The original scenario for LinkETL was to
handle data integration between a
