On Wed, Jul 17, 2013 at 7:23 PM, Langston, Jim <jim.langs...@compuware.com>wrote:
> As a follow up – I did upgrade the cluster to 1.2.6 and that > did take care of the issue. The upgrade went very smoothly, > the longest part was being thorough on the configuration > files, but I was able to able to quickly update the schema's > after restarting the cluster. > Glad to hear it! =Rob
