The general rule in HCat/WebHCat is to keep deprecated API for 2 releases. That is why it has been removed now.
If we had added templeton/v2/jobs instead of templeton/v1/jobs, this would not help the client once v1 is desupported. So we'd have to support deprecated API for ever...
I think the fundamental issue is that API evolution is not well defined in WebHCat, as you can see it's still at v1.
Is this change something that Knox can handle or should we restore the API? (The change was made in trunk, so we can still restore it before 0.14 ships)