[jira] [Updated] (MAPREDUCE-4512) TextInputFormat delimiter bug:- Input Text portion ends with Delimiter starts with same char/char sequence
[ https://issues.apache.org/jira/browse/MAPREDUCE-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gelesh updated MAPREDUCE-4512: -- Description: TextInputFormat delimiter bug scenario , a character sequence of the input text, in which the first character matches with the first character of delimiter, and the remaining input text character sequence matches with the entire delimiter character sequence from the starting position of the delimiter. eg delimiter =record; and Text = record 1:- name = Gelesh e mail = gelesh.had...@gmail.com Location Bangalore record 2: name = sdf .. location =Bangalorrecord 3: name Here string =Bangalorrecord 3: satisfy two conditions 1) contains the delimiter record 2) The character / character sequence immediately before the delimiter (ie ' r ') matches with first character (or character sequence ) of delimiter. (ie =Bangalor ends with and Delimiter starts with same character/char sequence 'r' ), Here the delimiter is not encountered by the program resulting in improper value text in map that contains the delimiter was: TextInputFormat delimiter bug scenario , a character sequence of the input text, in which the first character matches with the first character of delimiter, and reaming input text character sequence matches with the entire delimiter character sequence from the starting position of the delimiter. eg delimiter =record; and Text = record 1:- name = Gelesh e mail = gelesh.had...@gmail.com Location Bangalore record 2: name = sdf .. location =Bangalorrecord 3: name Here string =Bangalorrecord 3: satisfy two condition 1) contains the delimiter record 2) The character / character sequence immediately b4 the delimiter (ie 'r') matches with first character (or character sequence ) of delimiter. (ie =Bangalor ends with and Delimiter starts with same character/char sequence 'r' ), Hear the delimiter is skipped Environment: Linux (was: Lynux) Affects Version/s: 0.20.204.0 0.21.0 1.0.3 Test case input file text record 1 name: Java Location:UAErecord 2 name:Gelesh Location:Bangalorrecord 3 name Hadoop Location:Kerala Delimiter = record expected values in map 1 name: Java Location:UAE 2 name:Gelesh Location:Bangalor 3 name Hadoop Location:Kerala Actual values received in map 1 name: Java Location:UAE 2 name:Gelesh Location:Bangalorrecord 3 name Hadoop Location:Kerala TextInputFormat delimiter bug:- Input Text portion ends with Delimiter starts with same char/char sequence - Key: MAPREDUCE-4512 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4512 Project: Hadoop Map/Reduce Issue Type: Bug Components: contrib/mumak, mr-am, mrv1, mrv2, task Affects Versions: 0.20.204.0, 0.21.0, 1.0.3, 2.0.0-alpha Environment: Linux Reporter: Gelesh Labels: patch Fix For: 0.20.204.0 Attachments: MAPREDUCE-4512.txt Original Estimate: 1m Remaining Estimate: 1m TextInputFormat delimiter bug scenario , a character sequence of the input text, in which the first character matches with the first character of delimiter, and the remaining input text character sequence matches with the entire delimiter character sequence from the starting position of the delimiter. eg delimiter =record; and Text = record 1:- name = Gelesh e mail = gelesh.had...@gmail.com Location Bangalore record 2: name = sdf .. location =Bangalorrecord 3: name Here string =Bangalorrecord 3: satisfy two conditions 1) contains the delimiter record 2) The character / character sequence immediately before the delimiter (ie ' r ') matches with first character (or character sequence ) of delimiter. (ie =Bangalor ends with and Delimiter starts with same character/char sequence 'r' ), Here the delimiter is not encountered by the program resulting in improper value text in map that contains the delimiter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job gives ambiguous message as Killed job job id
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428590#comment-13428590 ] Harsh J commented on MAPREDUCE-4431: bq. In case the job was already killed, should we perhaps return 0 exitCode (since the kill was (already) successful? On second thought, lets not do this, as it would be in violation of what a command's run means. Only if the command were truly successful for that very instance we should return 0. So +1 and committing shortly. killing already completed job gives ambiguous message as Killed job job id -- Key: MAPREDUCE-4431 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 2.0.0-alpha, 3.0.0 Reporter: Nishan Shetty Assignee: Devaraj K Priority: Minor Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch If we try to kill the already completed job by the following command it gives ambiguous message as Killed job job id ./mapred job -kill already completed job id -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4431) killing already completed job gives ambiguous message as Killed job job id
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated MAPREDUCE-4431: --- Target Version/s: 2.2.0-alpha Affects Version/s: (was: 3.0.0) Hadoop Flags: Reviewed killing already completed job gives ambiguous message as Killed job job id -- Key: MAPREDUCE-4431 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 2.0.0-alpha Reporter: Nishan Shetty Assignee: Devaraj K Priority: Minor Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch If we try to kill the already completed job by the following command it gives ambiguous message as Killed job job id ./mapred job -kill already completed job id -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4503) Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles
[ https://issues.apache.org/jira/browse/MAPREDUCE-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428604#comment-13428604 ] Hudson commented on MAPREDUCE-4503: --- Integrated in Hadoop-Hdfs-0.23-Build #334 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/334/]) svn merge -c 1369197 FIXES: MAPREDUCE-4503. Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles (Robert Evans via jeagles) (Revision 1369209) Result = SUCCESS jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1369209 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRApps.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/util/TestMRApps.java Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles --- Key: MAPREDUCE-4503 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4503 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha Reporter: Robert Joseph Evans Assignee: Robert Joseph Evans Fix For: 0.23.3, 3.0.0, 2.2.0-alpha Attachments: MR-4503.txt, MR-4503.txt in 1.0 if a file was both in a jobs cache archives and cache files, and InvalidJobConfException was thrown. We should replicate this behavior on mrv2. We should also extend it so that if a cache archive or cache file is not going to be downloaded at all because of conflicts in the names of the symlinks a similar exception is thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4503) Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles
[ https://issues.apache.org/jira/browse/MAPREDUCE-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428606#comment-13428606 ] Hudson commented on MAPREDUCE-4503: --- Integrated in Hadoop-Hdfs-trunk #1125 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1125/]) MAPREDUCE-4503. Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles (Robert Evans via jeagles) (Revision 1369197) Result = SUCCESS jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1369197 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRApps.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/util/TestMRApps.java Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles --- Key: MAPREDUCE-4503 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4503 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha Reporter: Robert Joseph Evans Assignee: Robert Joseph Evans Fix For: 0.23.3, 3.0.0, 2.2.0-alpha Attachments: MR-4503.txt, MR-4503.txt in 1.0 if a file was both in a jobs cache archives and cache files, and InvalidJobConfException was thrown. We should replicate this behavior on mrv2. We should also extend it so that if a cache archive or cache file is not going to be downloaded at all because of conflicts in the names of the symlinks a similar exception is thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4503) Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles
[ https://issues.apache.org/jira/browse/MAPREDUCE-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428609#comment-13428609 ] Hudson commented on MAPREDUCE-4503: --- Integrated in Hadoop-Mapreduce-trunk #1157 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1157/]) MAPREDUCE-4503. Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles (Robert Evans via jeagles) (Revision 1369197) Result = FAILURE jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1369197 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRApps.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/util/TestMRApps.java Should throw InvalidJobConfException if duplicates found in cacheArchives or cacheFiles --- Key: MAPREDUCE-4503 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4503 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha Reporter: Robert Joseph Evans Assignee: Robert Joseph Evans Fix For: 0.23.3, 3.0.0, 2.2.0-alpha Attachments: MR-4503.txt, MR-4503.txt in 1.0 if a file was both in a jobs cache archives and cache files, and InvalidJobConfException was thrown. We should replicate this behavior on mrv2. We should also extend it so that if a cache archive or cache file is not going to be downloaded at all because of conflicts in the names of the symlinks a similar exception is thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
