[jira] [Commented] (HADOOP-12620) Advanced Hadoop Architecture (AHA) - Common
[ https://issues.apache.org/jira/browse/HADOOP-12620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045779#comment-15045779 ] Neelesh Srinivas Salian commented on HADOOP-12620: -- [~dinatreya], I think what [~aw] meant was to have the description as a document attached to the jira to avoid the noise of having the entire description being sent out to the Watchers per update. > Advanced Hadoop Architecture (AHA) - Common > --- > > Key: HADOOP-12620 > URL: https://issues.apache.org/jira/browse/HADOOP-12620 > Project: Hadoop Common > Issue Type: New Feature >Reporter: Dinesh S. Atreya > > h1. Advance Hadoop Architecture (AHA) / Advance Hadoop Adaptabilities (AHA) > One main motivation for this JIRA is to address a comprehensive set of uses > with just minimal enhancements to Hadoop to transition Hadoop to > Advanced/Cloud Data Architecture. > HDFS has traditionally had a write-once-read-many access model for files > until “[Append to files in HDFS | > https://issues.apache.org/jira/browse/HADOOP-1700 ]” capability was > introduced. The next minimal enhancements to core Hadoop include capability > to do “updates-in-place” in HDFS. > • Support seeks for writes (in addition to reads). > • After seek, if the new byte length is the same as the old byte length, > in place update is allowed. > • Delete is an update with appropriate Delete marker > • If byte length is different, old entry is marked as delete with new one > appended as before. > • It is the client’s discretion to perform either update, append or both > and the API changes in different Hadoop components should provide these > capabilities. > Please note that this JIRA is limited to essentially a specific type of > updates, in-place updates that do not change the byte length (e.g., buffer > spaces are included in the length). Updates that change the byte length are > not-supported in-place and are considered as Appends/Inserts. Similarly > Deletes that create holes are not supported. The reason is simple, > fragmentations and holes cause performance penalties and make the process > complicated and may involve a lot of changes to Hadoop and are out-of-scope. > These minimal changes will enable laying the basis for transforming the core > Hadoop to an interactive and real-time platform and introducing significant > native capabilities to Hadoop. These enhancements will lay a foundation for > all of the following processing styles to be supported natively and > dynamically. > • Real time > • Mini-batch > • Stream based data processing > • Batch – which is the default now. > Hadoop engines can dynamically choose processing style to use based on the > type of data and volume of data sets and enhance/replace prevailing > approaches. > With this Hadoop engines can evolve to utilize modern CPU, Memory and I/O > resources with increasing efficiency. The Hadoop task engines can use > vectorized/pipelined processing and greater use of memory throughout the > Hadoop platform. > These will enable enhanced performance optimizations to be implemented in > HDFS and made available to all the Hadoop components. This will enable Fast > processing of Big Data and enhance all the characteristics volume, velocity > and variety of big data. > There are many influences for this umbrella JIRA: > • Preserve and Accelerate Hadoop > • Efficient Data Management of variety of Data Formats natively in Hadoop > • Enterprise Expansion > • Internet and Media > • Databases offer native support for a variety of Data Formats such as > JSON, XML Indexes, and Temporal etc. – Hadoop should do the same. > It is quite probable that there may be many sub-JIRAs created to address > portions of this. This JIRA captures a variety of use-cases in one place. > Some Data Management /Platform initial use-cases are given hereunder. > h2. WEB > With the AHA (Advance Hadoop Architecture) enhancements, a variety of Web > standards can be natively supported such as updateable JSON > [http://json.org/], XML, RDF and other documents. > While Hadoop origination can be traced to the WEB, some of the [Web standards > | http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html] are not completely > supported natively in Hadoop such as HTTP PUT and PATCH (PUT and POST are > only partially supported in terms of creation). With the proposed enhancement > all of the standards POST, PUT and PATCH (new addition to Web standards) can > be natively completely supported (in addition to GET) through Hadoop. > Hypertext Transfer Protocol -- HTTP/1.1 ([Original RFC | > http://tools.ietf.org/html/rfc2616], [Current RFC | > http://tools.ietf.org/html/rfc7231] ) > Current RFCS: > • [ Hypertext Transfer Protocol (HTTP/1.1):
[jira] [Updated] (HADOOP-12219) Fix typos in hadoop-common-project module
[ https://issues.apache.org/jira/browse/HADOOP-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neelesh Srinivas Salian updated HADOOP-12219: - Assignee: Anthony Rojas (was: Neelesh Srinivas Salian) > Fix typos in hadoop-common-project module > - > > Key: HADOOP-12219 > URL: https://issues.apache.org/jira/browse/HADOOP-12219 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 2.7.1 >Reporter: Ray Chiang >Assignee: Anthony Rojas >Priority: Minor > Labels: supportability > Attachments: HADOOP-12219.001.patch > > > Fix a bunch of typos in comments, strings, variable names, and method names > in the hadoop-common-project module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12218) Fix typos in hadoop-tools module
[ https://issues.apache.org/jira/browse/HADOOP-12218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neelesh Srinivas Salian updated HADOOP-12218: - Assignee: Anthony Rojas (was: Neelesh Srinivas Salian) > Fix typos in hadoop-tools module > > > Key: HADOOP-12218 > URL: https://issues.apache.org/jira/browse/HADOOP-12218 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 2.7.1 >Reporter: Ray Chiang >Assignee: Anthony Rojas >Priority: Minor > Labels: supportability > Attachments: HADOOP-12218.001.patch > > > Fix a bunch of typos in comments, strings, variable names, and method names > in the hadoop-tools module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11854) Fix Typos in all the projects
[ https://issues.apache.org/jira/browse/HADOOP-11854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neelesh Srinivas Salian updated HADOOP-11854: - Assignee: Anthony Rojas (was: Neelesh Srinivas Salian) > Fix Typos in all the projects > - > > Key: HADOOP-11854 > URL: https://issues.apache.org/jira/browse/HADOOP-11854 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Anthony Rojas >Priority: Minor > Labels: BB2015-05-TBR > Attachments: HADOOP-11854.003.patch, HADOOP-11854.004.patch, > HADOOP-11854.005.patch, HADOOP-11854.suggestions.001.patch, > HADOOP-11854.suggestions.002.patch > > > Recently I had seen, there are so many jira's for fixing the typo's ( Keep on > accumulating more ). Hence I want to plan in proper manner such that > everything will be addressed.. > I am thinking, we can fix project level ( at most package level)... > My intention to avoid the number of jira's on typo's...One more suggestion to > reviewer's is please dn't commit for class level try to check project level ( > atmost package level) if any such typo's present... > Please correct me If I am wrong.. I will close this jira.. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11854) Fix Typos in all the projects
[ https://issues.apache.org/jira/browse/HADOOP-11854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14951253#comment-14951253 ] Neelesh Srinivas Salian commented on HADOOP-11854: -- [~rchiang], if this isn't being worked on atm, do you mind assigning it to me? I can look into it. Thank you. > Fix Typos in all the projects > - > > Key: HADOOP-11854 > URL: https://issues.apache.org/jira/browse/HADOOP-11854 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Ray Chiang >Priority: Minor > Labels: BB2015-05-TBR > Attachments: HADOOP-11854.003.patch, HADOOP-11854.004.patch, > HADOOP-11854.005.patch, HADOOP-11854.suggestions.001.patch, > HADOOP-11854.suggestions.002.patch > > > Recently I had seen, there are so many jira's for fixing the typo's ( Keep on > accumulating more ). Hence I want to plan in proper manner such that > everything will be addressed.. > I am thinking, we can fix project level ( at most package level)... > My intention to avoid the number of jira's on typo's...One more suggestion to > reviewer's is please dn't commit for class level try to check project level ( > atmost package level) if any such typo's present... > Please correct me If I am wrong.. I will close this jira.. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12458) Retries is typoed to spell Retires in parts of hadoop-yarn and hadoop-common
[ https://issues.apache.org/jira/browse/HADOOP-12458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14942429#comment-14942429 ] Neelesh Srinivas Salian commented on HADOOP-12458: -- [~qwertymaniac] Thank you for the review, notes and commit. > Retries is typoed to spell Retires in parts of hadoop-yarn and hadoop-common > > > Key: HADOOP-12458 > URL: https://issues.apache.org/jira/browse/HADOOP-12458 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7.1 >Reporter: Neelesh Srinivas Salian >Assignee: Neelesh Srinivas Salian >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4222.001.patch > > > Spotted this typo in the code while working on a separate YARN issue. > E.g DEFAULT_RM_NODEMANAGER_CONNECT_RETIRES > Checked in the whole project. Found a few occurrences of the typo in > code/comment. > The JIRA is meant to help fix those typos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-7945) Document that Path objects do not support ":" in them.
[ https://issues.apache.org/jira/browse/HADOOP-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neelesh Srinivas Salian updated HADOOP-7945: Fix Version/s: 2.0.0-alpha 3.0.0 Status: Patch Available (was: Open) > Document that Path objects do not support ":" in them. > -- > > Key: HADOOP-7945 > URL: https://issues.apache.org/jira/browse/HADOOP-7945 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 0.20.0 >Reporter: Harsh J >Priority: Critical > Labels: newbie > Fix For: 3.0.0, 2.0.0-alpha > > Attachments: HADOOP-7945.patch > > > Until HADOOP-3257 is fixed, this particular exclusion should be documented. > This is a major upsetter to many beginners. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-7945) Document that Path objects do not support ":" in them.
[ https://issues.apache.org/jira/browse/HADOOP-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14937458#comment-14937458 ] Neelesh Srinivas Salian commented on HADOOP-7945: - [~qwertymaniac] has this been resolved or is it in progress? We should get this in to avoid confusion. I would like to work on it if possible. Thank you. > Document that Path objects do not support ":" in them. > -- > > Key: HADOOP-7945 > URL: https://issues.apache.org/jira/browse/HADOOP-7945 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 0.20.0 >Reporter: Harsh J >Priority: Critical > Labels: newbie > Attachments: HADOOP-7945.patch > > > Until HADOOP-3257 is fixed, this particular exclusion should be documented. > This is a major upsetter to many beginners. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
