In other words,
Is there a problem that can be solved by directly determining your map job abbreviations, but for which you cannot generate a request for using Hive QL?
If yes, then this means that Hive QL is limited in it by expressive power and cannot express all possible tasks of map reduction.
In practice, this means that Hive QL is not a complete substitute for defining your own map reduction jobs.
source
share