One of the small size companies that we work with has asked if we can use ODI instead of Clover ETL for Endeca implementation
Even if this may probably turn out be technically possible
- how much effort do you think will be required to fit ODI with endeca
- Can we get the same kind of flexibility in ODI that we get in Clover
- what is oracle view on this - use clover or anything will do
is there any specific reason why they don't want to use clover ETL?
I don't think it would be simple because it has even many custom discovery components and graph development/deployment would be a major concern for any custom approach.