-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: 1.7.1
-
Component/s: JavaScript, MapReduce
-
None
-
Environment:Fri Oct 8 12:17:47 db version v1.7.2-pre-, pdfile version 4.5
Fri Oct 8 12:17:47 git version: 7a21313631aa998bf6456310882b9ba75be8679d
Fri Oct 8 12:17:47 sys info: Darwin 132.sub-75-193-231.myvzw.com 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386 BOOST_LIB_VERSION=1_44Fri Oct 8 12:17:47 db version v1.7.2-pre-, pdfile version 4.5 Fri Oct 8 12:17:47 git version: 7a21313631aa998bf6456310882b9ba75be8679d Fri Oct 8 12:17:47 sys info: Darwin 132.sub-75-193-231.myvzw.com 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386 BOOST_LIB_VERSION=1_44
-
Minor Change
-
ALL
-
Platform 6 07/17/15, Platform 8 08/28/15, Platform 7 08/10/15
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
To reproduce:
1. Execute a mapReduce with "x" variable in mapReduce scope and reference it in a function.
2. Execute another mapReduce (using same connection) without "x" variable in scope but still reference it in a function.
Problem:
Second mapReduce should have failed with "reference to undefined variable 'x'". Instead it works referencing old "x" variable.
- is duplicated by
-
-
- Closed
-