[ https://issues.apache.org/jira/browse/PIG-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612037#comment-15612037 ]
Adam Szita commented on PIG-4934: --------------------------------- I see, in this case we can indeed do the optimization. Revised [^PIG-4934.3.patch] > 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 > Assignee: Adam Szita > Attachments: PIG-4934.2.patch, PIG-4934.3.patch, PIG-4934.patch > > > 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)