To my mind it depends a little on what functionality is behind the account. If this is a huge chunk of functionality, that presently depends on their infrastructure but doesn't have to, then I think that's fine (though certainly enough to self-host would be better). If this is basically a thin wrapper and all the actual functionality is in their proprietary server code, then it's hugely disingenuous.
The code does not depend on the infrastructure. You can execute the Pig code locally on your machine, or on your own hadoop cluster. This really is a 'free' give-away of code.
Comments
To my mind it depends a little on what functionality is behind the account. If this is a huge chunk of functionality, that presently depends on their infrastructure but doesn't have to, then I think that's fine (though certainly enough to self-host would be better). If this is basically a thin wrapper and all the actual functionality is in their proprietary server code, then it's hugely disingenuous.
The code does not depend on the infrastructure. You can execute the Pig code locally on your machine, or on your own hadoop cluster. This really is a 'free' give-away of code.
Fantastic! Thanks.