Which newbie Jira's need work?
Hi All, First off I've submitted a patch for HADOOP-11813 as a starter for 10, this was an easy change and starts to get me familiar with where things are. Now I've been looking through the newbie Jira's to see what else I can do to help, but I'm struggling to see the wood for the trees, which I suspect is down to my lack of knowledge around how things hang together. I figured I'd go for some easy stuff to start with, so had a look at HADOOP-10861. Most of the html I can find under /hadoop-hdfs-project/hadoop-hdfs/src/main/webapps seems to be valid. After further digging I found HDFS-274 which appears to be a patch for the pages when they were .jsp instead of html, so does this just need closing? So essentially this boils down to two mains questions: * How do I know if a newbie Jira is even still valid? * Does anybody have any suggestions for a suitable newbie ticket to pick up? Thanks Darrell
Re: Which newbie Jira's need work?
Hi Tsuyoshi On Wed, Apr 22, 2015 at 9:16 AM, Tsuyoshi Ozawa wrote: > Hi Darrell, > > Thank you for having interest for contributions to Hadoop project! > > > * How do I know if a newbie Jira is even still valid? > > Please ping committers whether the issue is valid when the issue looks > to have been resolved already. > What is the recommended way to do this? Tag them in a Jira comment? Send a message to the mailing list? > > > * Does anybody have any suggestions for a suitable newbie ticket to pick > up? > > One suggestion from me is to use JQL on JIRA to find issues for newbie. > If you run following query, you will find fresh and open issues. > > project = "Hadoop Common" and labels = "newbie" and status = open > ORDER BY updatedDate > I have already been looking through these from a link Allen sent me, but this is what prompted my previous post. It's hard to tell if something has been done elsewhere, e.g. HADOOP-10861 > > Also I think one good starting point is to fix documentation, typos in > code, trivial changes, or something. > OK, I'll take another sweep through and see what I can find. Thanks Darrell > > Thanks, > - Tsuyoshi > > > On Wed, Apr 22, 2015 at 4:47 PM, Darrell Taylor > wrote: > > Hi All, > > > > First off I've submitted a patch for HADOOP-11813 as a starter for 10, > this > > was an easy change and starts to get me familiar with where things are. > > > > Now I've been looking through the newbie Jira's to see what else I can do > > to help, but I'm struggling to see the wood for the trees, which I > suspect > > is down to my lack of knowledge around how things hang together. > > > > I figured I'd go for some easy stuff to start with, so had a look at > > HADOOP-10861. Most of the html I can find > > under /hadoop-hdfs-project/hadoop-hdfs/src/main/webapps seems to be > valid. > > After further digging I found HDFS-274 which appears to be a patch for > the > > pages when they were .jsp instead of html, so does this just need > closing? > > > > So essentially this boils down to two mains questions: > > > > * How do I know if a newbie Jira is even still valid? > > * Does anybody have any suggestions for a suitable newbie ticket to pick > up? > > > > Thanks > > Darrell >
Re: Which newbie Jira's need work?
Hi Chris, Thanks for the info, I'm working through the newbie list and trying to pick anything up that seems simple. So, I got to MAPREDUCE-5673 and while this looks easy I asked myself if it was even worth doing? My reasoning is that this was raised by somebody who thinks it's a good idea to have the host(IP) in the jobhistory webUI (which it probably is), is there any collective thought around whether people think this is a good idea or not? Do the Jira's go through any sort of vetting process? I guess what I'm asking is could anyone just submit a Jira with a subjective opinion and there is a chance that it would make it all the way through to trunk? I'll probably take a look through this anyway as it's a good way of trying to learn what goes where. But I'm just curious how the process works. Thanks Darrell On Thu, Apr 23, 2015 at 6:23 PM, Chris Nauroth wrote: > If you happen to know which committers tend to do a lot of code reviews in > the specific area of the code covered by your patch, then tagging them in > a jira comment is an effective approach. If you're unsure who to contact, > then please feel free to email the appropriate project-specific *-dev list > for help. > > I agree that our jira metadata can be messy, and that can make it > challenging to find issues that really do need work. The committers have > some efforts under way now to try to keep our bug tracking cleaner. One > specific thing we can all do in this area is to apply the "newbie" label > to appropriate issues, so that new contributors can run an easy jira > query. Meanwhile, if there is every any doubt, please feel free to ask > committers. In the case of HADOOP-10861, I think the right approach is to > review the current web UI code, and if there are no occurrences of invalid > HTML, then the issue can be resolved as Not a Problem. > > Chris Nauroth > Hortonworks > http://hortonworks.com/ > > > > > > > On 4/23/15, 12:53 AM, "Darrell Taylor" wrote: > > >Hi Tsuyoshi > >On Wed, Apr 22, 2015 at 9:16 AM, Tsuyoshi Ozawa wrote: > > > >> Hi Darrell, > >> > >> Thank you for having interest for contributions to Hadoop project! > >> > >> > * How do I know if a newbie Jira is even still valid? > >> > >> Please ping committers whether the issue is valid when the issue looks > >> to have been resolved already. > >> > > > >What is the recommended way to do this? Tag them in a Jira comment? Send > >a message to the mailing list? > > > > > >> > >> > * Does anybody have any suggestions for a suitable newbie ticket to > >>pick > >> up? > >> > >> One suggestion from me is to use JQL on JIRA to find issues for newbie. > >> If you run following query, you will find fresh and open issues. > >> > >> project = "Hadoop Common" and labels = "newbie" and status = open > >> ORDER BY updatedDate > >> > > > >I have already been looking through these from a link Allen sent me, but > >this is what prompted my previous post. It's hard to tell if something > >has > >been done elsewhere, e.g. HADOOP-10861 > > > > > >> > >> Also I think one good starting point is to fix documentation, typos in > >> code, trivial changes, or something. > >> > > > >OK, I'll take another sweep through and see what I can find. > > > >Thanks > >Darrell > > > > > > > >> > >> Thanks, > >> - Tsuyoshi > >> > >> > >> On Wed, Apr 22, 2015 at 4:47 PM, Darrell Taylor > >> wrote: > >> > Hi All, > >> > > >> > First off I've submitted a patch for HADOOP-11813 as a starter for 10, > >> this > >> > was an easy change and starts to get me familiar with where things > >>are. > >> > > >> > Now I've been looking through the newbie Jira's to see what else I > >>can do > >> > to help, but I'm struggling to see the wood for the trees, which I > >> suspect > >> > is down to my lack of knowledge around how things hang together. > >> > > >> > I figured I'd go for some easy stuff to start with, so had a look at > >> > HADOOP-10861. Most of the html I can find > >> > under /hadoop-hdfs-project/hadoop-hdfs/src/main/webapps seems to be > >> valid. > >> > After further digging I found HDFS-274 which appears to be a patch for > >> the > >> > pages when they were .jsp instead of html, so does this just need > >> closing? > >> > > >> > So essentially this boils down to two mains questions: > >> > > >> > * How do I know if a newbie Jira is even still valid? > >> > * Does anybody have any suggestions for a suitable newbie ticket to > >>pick > >> up? > >> > > >> > Thanks > >> > Darrell > >> > >
Maven always detects changes - Is this a Docker 'feature'?
Hi, Is it normal behaviour for maven to detect changes when I run tests with no changes? e.g. $ mvn test -Dtest=TestDFSShell -nsu -o ... [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ hadoop-hdfs --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 576 source files to /home/darrell/hadoop/hadoop-hdfs-project/hadoop-hdfs/target/classes ... Then I run the same command again without touching anything else and it compiles everything again. It's getting rather tedious. I am running this from inside the docker container. Any help appreciated. Thanks Darrell.
Who do I need to pester / bribe with donuts?
Hi All, I realise everybody is busy, but who do I need to chase down to get the three patches I've submitted moving? Only small fixes, but I figure the sooner they are resolved that's three less tickets in Jira. They are : https://issues.apache.org/jira/browse/HDFS-5033 https://issues.apache.org/jira/browse/YARN-2355 https://issues.apache.org/jira/browse/HADOOP-9891 I am willing to help prioritise this with donut bribes ;) Thanks Darrell
Re: Maven always detects changes - Is this a Docker 'feature'?
darrell@0e58329b3df9:~/hadoop/hadoop-project/target$ ant -diagnostics ... --- Temp dir --- Temp dir is /tmp Temp dir is writeable Temp dir alignment with system clock is -580 ms ... Also comparing the clock inside Docker compared to the host machine the only difference is TZ, Docker is UTC, my host machine is BST. So underlying time is the same. Any other pointers? On Tue, Jun 16, 2015 at 10:57 AM, Steve Loughran wrote: > Your clocks are probably confused. > > ant -diagnostics actually measures clock drift between > System.currentTimeMillis() and the timestamps coming off the tmp dir. You > should do the same with files touched in target/ > > > > On 15 Jun 2015, at 23:31, Colin P. McCabe wrote: > > > > Hi Darrell, > > > > Sorry, I'm not familiar with this feature of Maven. Perhaps try > > asking on the Apache Maven mailing list? > > > > best, > > Colin > > > > On Fri, May 22, 2015 at 8:34 AM, Darrell Taylor > > wrote: > >> Hi, > >> > >> Is it normal behaviour for maven to detect changes when I run tests > with no > >> changes? > >> > >> e.g. > >> $ mvn test -Dtest=TestDFSShell -nsu -o > >> ... > >> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ > >> hadoop-hdfs --- > >> [INFO] Changes detected - recompiling the module! > >> [INFO] Compiling 576 source files to > >> /home/darrell/hadoop/hadoop-hdfs-project/hadoop-hdfs/target/classes > >> ... > >> > >> Then I run the same command again without touching anything else and it > >> compiles everything again. It's getting rather tedious. > >> > >> I am running this from inside the docker container. > >> > >> Any help appreciated. > >> > >> Thanks > >> Darrell. > >
[jira] [Resolved] (HADOOP-11314) Fixing warnings by apt parser
[
https://issues.apache.org/jira/browse/HADOOP-11314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrell Taylor resolved HADOOP-11314.
-
Resolution: Implemented
> Fixing warnings by apt parser
> -
>
> Key: HADOOP-11314
> URL: https://issues.apache.org/jira/browse/HADOOP-11314
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
>Reporter: Tsuyoshi Ozawa
> Labels: newbie
>
> {{mvn site:stage}} show lots warnings as follows:
> {code}
> $mvn clean site; mvn site:stage -DstagingDirectory=/tmp/hadoop-site;
> [WARNING] [APT Parser] Modified invalid link: 'Set Storage Policy' to
> '#Set_Storage_Policy'
> [WARNING] [APT Parser] Modified invalid link: 'OS Limits' to '#OS_Limits'
> [WARNING] [APT Parser] Modified invalid link: 'Administration Commands' to
> '#Administration_Commands'
> [WARNING] [APT Parser] Modified invalid link: 'User Commands' to
> '#User_Commands'
> [WARNING] [APT Parser] Modified invalid link: 'Hadoop+Rack+Awareness' to
> '../hadoop-common/ClusterSetup.html#HadoopRackAwareness'
> [WARNING] [APT Parser] Modified invalid link: 'oiv_legacy Command' to
> '#oiv_legacy_Command'
> [WARNING] [APT Parser] Modified invalid link: '-px' to '#a-px'
> [WARNING] [APT Parser] Modified invalid link: '-skipcrccheck' to
> '#a-skipcrccheck'
> [WARNING] [APT Parser] Modified invalid link: '-update' to '#a-update'
> [WARNING] [APT Parser] Modified invalid link: 'Single Namenode Clusters' to
> '#Single_Namenode_Clusters'
> [WARNING] [APT Parser] Modified invalid link: 'ACL Status JSON Schema' to
> '#ACL_Status_JSON_Schema'
> [WARNING] [APT Parser] Modified invalid link: 'Access Time' to '#Access_Time'
> [WARNING] [APT Parser] Modified invalid link: 'Append to a File' to
> '#Append_to_a_File'
> [WARNING] [APT Parser] Modified invalid link: 'Block Size' to '#Block_Size'
> [WARNING] [APT Parser] Modified invalid link: 'Boolean JSON Schema' to
> '#Boolean_JSON_Schema'
> [WARNING] [APT Parser] Modified invalid link: 'Buffer Size' to '#Buffer_Size'
> [WARNING] [APT Parser] Modified invalid link: 'Cancel Delegation Token' to
> '#Cancel_Delegation_Token'
> [WARNING] [APT Parser] Modified invalid link: 'Check access' to
> '#Check_access'
> [WARNING] [APT Parser] Modified invalid link: 'Concat File(s)' to
> '#Concat_Files'
> [WARNING] [APT Parser] Modified invalid link: 'ContentSummary JSON Schema' to
> '#ContentSummary_JSON_Schema'
> [WARNING] [APT Parser] Modified invalid link: 'Create Parent' to
> '#Create_Parent'
> [WARNING] [APT Parser] Modified invalid link: 'Create Snapshot' to
> '#Create_Snapshot'
> [WARNING] [APT Parser] Modified invalid link: 'Create a Symbolic Link' to
> '#Create_a_Symbolic_Link'
> [WARNING] [APT Parser] Modified invalid link: 'Create and Write to a File' to
> '#Create_and_Write_to_a_File'
> [WARNING] [APT Parser] Modified invalid link: 'Delete Snapshot' to
> '#Delete_Snapshot'
> [WARNING] [APT Parser] Modified invalid link: 'Delete a File/Directory' to
> '#Delete_a_FileDirectory'
> [WARNING] [APT Parser] Modified invalid link: 'Error Responses' to
> '#Error_Responses'
> [WARNING] [APT Parser] Modified invalid link: 'FileChecksum JSON Schema' to
> '#FileChecksum_JSON_Schema'
> [WARNING] [APT Parser] Modified invalid link: 'FileStatus JSON Schema' to
> '#FileStatus_JSON_Schema'
> [WARNING] [APT Parser] Modified invalid link: 'FileStatus Properties' to
> '#FileStatus_Properties'
> [WARNING] [APT Parser] Modified invalid link: 'FileStatuses JSON Schema' to
> '#FileStatuses_JSON_Schema'
> [WARNING] [APT Parser] Modified invalid link: 'Get Content Summary of a
> Directory' to '#Get_Content_Summary_of_a_Directory'
> [WARNING] [APT Parser] Modified invalid link: 'Get Delegation Token' to
> '#Get_Delegation_Token'
> [WARNING] [APT Parser] Modified invalid link: 'Get Delegation Tokens' to
> '#Get_Delegation_Tokens'
> [WARNING] [APT Parser] Modified invalid link: 'Get
