I also am not a fan of hive.mapred.mode If you turn it off, you may unintentionally turn off other checks, and it uses strict/nonstrict instead of true/false which is easier to validate. That's, at best, a problem for another JIRA, though, as it's fairly well established.

I agree with Kevin, but I don't think this should be postponed for another JIRA. Please add a new configuration property now instead of further overloading what is an already ill-defined and poorly documented configuration property.

Carl Steinbach
added a comment - 26/Jul/12 01:31 - edited -1
I also am not a fan of hive.mapred.mode If you turn it off, you may unintentionally turn off other checks, and it uses strict/nonstrict instead of true/false which is easier to validate. That's, at best, a problem for another JIRA, though, as it's fairly well established.
I agree with Kevin, but I don't think this should be postponed for another JIRA. Please add a new configuration property now instead of further overloading what is an already ill-defined and poorly documented configuration property.

The patch is not attached to this ticket, and it looks like Phabricator stopped automatically attaching patches some time ago. Is anyone at Facebook looking into fixing this?

Part of the agreement when we started using Phabricator was that the tool would automatically copy review comments back to JIRA. This feature hasn't worked in months, and unless it starts working soon I think we should stop using Phabricator and switch back to ReviewBoard. Is anyone looking into fixing this? If not we should probably just switch back now.

Carl Steinbach
added a comment - 26/Jul/12 01:37 Two more points which are tangentially related:
The patch is not attached to this ticket, and it looks like Phabricator stopped automatically attaching patches some time ago. Is anyone at Facebook looking into fixing this?
Part of the agreement when we started using Phabricator was that the tool would automatically copy review comments back to JIRA. This feature hasn't worked in months, and unless it starts working soon I think we should stop using Phabricator and switch back to ReviewBoard. Is anyone looking into fixing this? If not we should probably just switch back now.

Ashutosh Chauhan
added a comment - 10/Jan/13 19:53 This issue is fixed and released as part of 0.10.0 release. If you find an issue which seems to be related to this one, please create a new jira and link this one with new jira.