Setup and cleanup tasks could affect job latency if they are caught running on
bad nodes
Key: MAPREDUCE-1099
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1099
Use deploy_design function in Vertica 3.5
-
Key: MAPREDUCE-1097
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1097
Project: Hadoop Map/Reduce
Issue Type: Improvement
Affects Versions: 0.21.0
Add getNames method to VerticaRecord to retrieve input column names
---
Key: MAPREDUCE-1096
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1096
Project: Hadoop Map/Reduce
Hadoop 0.20 Compatible IdentityMapper and IdentityReducer
-
Key: MAPREDUCE-1095
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1095
Project: Hadoop Map/Reduce
Issue Type: Improvem
CapacityScheduler's JobInitPoller shouldn't 'sleep'
---
Key: MAPREDUCE-1094
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1094
Project: Hadoop Map/Reduce
Issue Type: Bug
Compon
Java assertion failures triggered by tests
--
Key: MAPREDUCE-1093
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1093
Project: Hadoop Map/Reduce
Issue Type: Test
Reporter: Eli Collins
Enable asserts for tests by default
---
Key: MAPREDUCE-1092
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1092
Project: Hadoop Map/Reduce
Issue Type: Test
Reporter: Eli Collins
Atta
TaskTrackers only work with same build as the JobTracker
Key: MAPREDUCE-1091
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1091
Project: Hadoop Map/Reduce
Issue Type: Bug
Hi all :
I try to use the memory file system in hadoop. the idea is very simple. I
want to use memory file system to the map intermediate file. It is like
this; 1. the memory is limited, the data will be written into the disk. 2.If
the file in memory is deleted and there are space in memory, the d
Modify log statement in Tasktracker log related to memory monitoring to include
attempt id.
---
Key: MAPREDUCE-1090
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1090
10 matches
Mail list logo