You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2016/06/23 23:07:16 UTC
[jira] [Created] (PIG-4934) SET command does not work well with
deprecated settings
Rohini Palaniswamy created PIG-4934:
---------------------------------------
Summary: SET command does not work well with deprecated settings
Key: PIG-4934
URL: https://issues.apache.org/jira/browse/PIG-4934
Project: Pig
Issue Type: Bug
Reporter: Rohini Palaniswamy
For eg: If mapred.job.map.memory.mb was specified in the script using set command and mapreduce.map.memory.mb was present in mapred-site.xml, that takes effect. This is because of the use of Properties and not Configuration.
GruntParser.processSet() calls HExecutionEngine.setProperty which just updates pigContext.getProperties()
{code}
public void setProperty(String property, String value) {
Properties properties = pigContext.getProperties();
properties.put(property, value);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)