Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
On Wed, Apr 28, 2010 at 10:27 AM, matthew a. grisius mgris...@comcast.netwrote: I also share many of Phil's sentiments. I really want the project (bin/nutch crawl) to work for me as well and I want to help somehow. I would like to share a 5gb 'intranet' web site with ~50 people. And I have not graduated to making the 'deepcrawl' script work yet either, as I'm thinking that maybe Nutch might not be the 'right tool' for 'little projects' based on documentation, discussion list feedback, etc. . . . I think it's exactly what you need to do that. I was able to get the 1.0 release to work pretty quickly. Working 8 hour days, I had a server built and Nutch crawling sites within 40 hours. Actually after I found one specific tutorial I can get Nutch running in a basic bin/nutch crawl sort of way in about an hour. Wish I had found that site the first day... Going through that documentation, I found that it lacked one step and I fed that back to the author. He has already fixed it for 1.0 and if you follow his steps from top to bottom, you will get Nutch 1.0 running. The site is here: http://centoshelp.org/servers/installing-configuring-nutch-nutch-gui-sun-jdk-tomcat-6-on-centos-5.x Nutch 1.1 also follows the same installation steps and you get a working interface, but the crawls don't work well enough to get data into the indexes.
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
Oh yeah, I built a presentation and gave it to our local Linux User Group meeting. You might find it useful: http://leap-cf.org/presentations/nutch/NutchWebCrawler.odp On Sat, May 1, 2010 at 2:10 AM, Phil Barnett ph...@philb.us wrote: On Wed, Apr 28, 2010 at 10:27 AM, matthew a. grisius mgris...@comcast.net wrote: I also share many of Phil's sentiments. I really want the project (bin/nutch crawl) to work for me as well and I want to help somehow. I would like to share a 5gb 'intranet' web site with ~50 people. And I have not graduated to making the 'deepcrawl' script work yet either, as I'm thinking that maybe Nutch might not be the 'right tool' for 'little projects' based on documentation, discussion list feedback, etc. . . . I think it's exactly what you need to do that. I was able to get the 1.0 release to work pretty quickly. Working 8 hour days, I had a server built and Nutch crawling sites within 40 hours. Actually after I found one specific tutorial I can get Nutch running in a basic bin/nutch crawl sort of way in about an hour. Wish I had found that site the first day... Going through that documentation, I found that it lacked one step and I fed that back to the author. He has already fixed it for 1.0 and if you follow his steps from top to bottom, you will get Nutch 1.0 running. The site is here: http://centoshelp.org/servers/installing-configuring-nutch-nutch-gui-sun-jdk-tomcat-6-on-centos-5.x Nutch 1.1 also follows the same installation steps and you get a working interface, but the crawls don't work well enough to get data into the indexes.
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
Hi Phil, Thanks for your comments. Mine below: Unfortunately some parts of the documentation on Nutch (namely the tutorial, and other parts of the static site) have been out of date for a while. This has occurred really independent of the releases, and independent of the wiki [1], which hasn't really fallen out of date as quick. While documentation may not be part of the code, it's certainly part of the project. And it's just as important as the code. Yes, I know that documentation is the bane of programmers everywhere. I'm a coder. I get it. But when you change the way things work in a fundamental way that leaves all of your documentation behind, it's time to spend some time on it. Sure. So, what fundamental way has Nutch changed from 1.0 to 1.1? Can you elaborate? Also, in terms of spending time on Nutch's documentation, I'll try to as I get more time (as I'm sure other committers will as well), but I'd also say: if there's something to be improved, by all means, go for it, and patches welcome to contribute it back. For example, my find of broken code in bin/nutch crawl, a most basic way of getting it running. Can you elaborate on your find of broken code? Did you file a JIRA issue for this in the Nutch JIRA system [2] ? Yes, it led to another release. The bug fix I contributed was incorporated. Great! The more information you provide here about your environment and your situation that caused the error, as well as e.g., detailed information (a stack trace, an exception, something), the easier it is to track down what you're seeing. Yes, that was all in the unanswered emails. it would be easier for you to search your inbox than for me to send it all over again. I wouldn't assume that the inboxes of folks watching the list are always centered on the Nutch mailing lists. Realize that many of us are subscribed to several mailing lists, and sometimes, emails go unanswered for a while. That said, one thing to realize is that this is open source software, so in the end, as they say in Apache, those that do, decide, or patches welcome! In other words, if there are things that you see that could be fixed, improved, made more configurable, etc., including the code, but *also the documentation*, then by all means we'd appreciate your feedback and contribution. Nutch is not simply a product of the developers that contribute their (potentially and often unsalaried) time to work on it, but of its user community as well. I've been the leader of a major open source project for over 10 years. Last fall I relinquished the reins of that project to a new project leader, so I think I know how it works. We wrote an open source cross platform compiler for xBase (Clipper) code named Harbour Project, now in release 2.0. That would be why I not only raised the flag that it's not ready to release, but I tracked down a bug and submitted a bug fix. And I'm still saying it's not ready to release. There's still another bug that I have found that goes unanswered. Right, so then you know that bugs aren't just bugs -- they must come with a priority. There are several categories, High, Medium, Critical, or Blocker, just to name a few. When I cut a release as the Release Manager (RM), I always run unit tests and try and at least run a basic crawl first before cutting the RC. So, hopefully that catches anything that would be a big problem, but sometimes even that process breaks down since not everyone has e.g., large scale deployments, or maybe we're missing a unit test we need, etc. I'd say at ~10 releases of Nutch to date, and many many features, etc., we have fairly decent regression. In certain cases you are right, but I would take your above comments as verbatim across the board. For example, if you believe there is documentation lacking, then the first step is typically to file JIRA issues to alert committers and other users of Nutch of your concern and then have discussion on the lists regarding the issues. At some point a patch is produced, and then attached to the issue, where the committers can review the patches and then work to get them committed to the code base. Nutch has a number of unit tests for regression that ship with the product that tell me that it's not broken, and users that are able to make it work in their environments. There have been some recent bug fixes in the 1.1 RC that we caught which have been fixed (NUTCH-812, NUTCH-814, etc.), but that's natural. No, not we. Me. I found a bug, told you about it and provided the fix. Before I did that, I told you that your release candidate was broken. Just like I'm still saying, unless I'm doing something grossly wrong, it's still broken. Right, gotcha. I didn't map that you had been the guy that contributed the patch. Thanks for that. Good question. I'm not super familiar with the nightly tests, but my guess is that the scripts are outside the context of
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
On Sat, May 1, 2010 at 2:34 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Sure, hopefully you'll find the answer you're looking for. In the meanwhile, it's my job to keep cutting release candidates as the RM, that at least pass the basic criteria for release and right now that involves what I mentioned above. I hope to be able to get back onto my Nutch project when I get back to work next Thursday. Until then, it appears that someone else has reported the same behaviour that I am experiencing.
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
On Wed, Apr 28, 2010 at 11:01 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Unfortunately some parts of the documentation on Nutch (namely the tutorial, and other parts of the static site) have been out of date for a while. This has occurred really independent of the releases, and independent of the wiki [1], which hasn't really fallen out of date as quick. While documentation may not be part of the code, it's certainly part of the project. And it's just as important as the code. Yes, I know that documentation is the bane of programmers everywhere. I'm a coder. I get it. But when you change the way things work in a fundamental way that leaves all of your documentation behind, it's time to spend some time on it. For example, my find of broken code in bin/nutch crawl, a most basic way of getting it running. Can you elaborate on your find of broken code? Did you file a JIRA issue for this in the Nutch JIRA system [2] ? Yes, it led to another release. The bug fix I contributed was incorporated. And I have yet to get the deepcrawl script which seems to be the suggestion of how to get beyond bin/nutch crawl. It doesn't return any data at all and has an error in the middle of it's run regarding missing file which the last stage apparently failed to write. (I believe because the scheduler excluded everything) The more information you provide here about your environment and your situation that caused the error, as well as e.g., detailed information (a stack trace, an exception, something), the easier it is to track down what you're seeing. Yes, that was all in the unanswered emails. it would be easier for you to search your inbox than for me to send it all over again. I wonder if the developers have advanced so far past these basic scripts as to have pretty much left them behind. This leads to these basics that people start with not working. I wouldn't say developers have advanced beyond anything really for that matter :) The number of active developers in Nutch these days is fairly small, but interest and the user community is stable and there are some pretty large scale deployments of Nutch to my knowledge. That said, those folks have been following the mailing lists for a while, have been using the software for a while and thus their level of entry into the documentation may be at a little higher bar than that of a newer user such as yourself. bin/nutch crawl was plainly broken and it would never have worked for anyone who tried it. 'nuff said. That said, one thing to realize is that this is open source software, so in the end, as they say in Apache, those that do, decide, or patches welcome! In other words, if there are things that you see that could be fixed, improved, made more configurable, etc., including the code, but *also the documentation*, then by all means we'd appreciate your feedback and contribution. Nutch is not simply a product of the developers that contribute their (potentially and often unsalaried) time to work on it, but of its user community as well. I've been the leader of a major open source project for over 10 years. Last fall I relinquished the reins of that project to a new project leader, so I think I know how it works. We wrote an open source cross platform compiler for xBase (Clipper) code named Harbour Project, now in release 2.0. That would be why I not only raised the flag that it's not ready to release, but I tracked down a bug and submitted a bug fix. And I'm still saying it's not ready to release. There's still another bug that I have found that goes unanswered. I've spend dozens of hours trying to get 1.1 to work anything like 1.0 and I'm getting nowhere at all. It's pretty frustrating to spend that much time trying to figure out how it works and keep hitting walls. And then asking basic questions here that go unanswered. I apologize that your questions have gone unanswered and that you're hitting walls with regards to using Nutch. What questions did you ask? Perhaps it's the detail that you are providing (or not providing), or perhaps it's the way you're asking the questions. Or (even more likely) it's the fact that this is an open source project and thus the committers get around to user emails lists as one of the multiple items on their plate that they are working on the project and us committers may have missed your question, or perhaps those that had the time weren't particular experts in the one area of Nutch that you were asking about. There could be a number of reasons. Regardless, persistence is key as is *patience* and respectfulness. This has always to my knowledge been a really friendly community, so if you hang around and keep asking questions they will get answered I'm confident of that. Great. Now that it's out in the open, perhaps someone who does know about the things I asked about can reply to my questions. The view from
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
On Mon, Apr 26, 2010 at 1:55 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Please vote on releasing these packages as Apache Nutch 1.1. The vote is open for the next 72 hours. How do you test to see if Nutch works like the documentation says it works? I still find major differences between how existing documentation tells me, a newcomer to the project, how to get it running. For example, my find of broken code in bin/nutch crawl, a most basic way of getting it running. And I have yet to get the deepcrawl script which seems to be the suggestion of how to get beyond bin/nutch crawl. It doesn't return any data at all and has an error in the middle of it's run regarding missing file which the last stage apparently failed to write. (I believe because the scheduler excluded everything) I wonder if the developers have advanced so far past these basic scripts as to have pretty much left them behind. This leads to these basics that people start with not working. I've spend dozens of hours trying to get 1.1 to work anything like 1.0 and I'm getting nowhere at all. It's pretty frustrating to spend that much time trying to figure out how it works and keep hitting walls. And then asking basic questions here that go unanswered. The view from the outside is not so good from my direction. If you don't keep documentation up to date and you change the way things work, the project as seen from the outside, is plainly broken. I'd be happy to give you feedback on where I find these problems and I'll even donate whatever fixes I can come up with, but Java is not a language I'm familiar with and going is slow weeding through things. I really need this project to work for me. I want to help. 1. Where is the scheduler documented? If I want to crawl everything from scratch, where is the information from the last run stored? It seems like the schedule is telling my crawl to ignore pages due to scheduler knocking them out. It's not obvious to my why this is happening and how to stop it from happening. I think right now this is my major roadblock in getting bin/nutch crawl working. Maybe the scheduler code no longer works properly in bin/nutch crawl. I can't tell if it's that or if the default configurations don't work. 2, Where are the control files in conf documented? How do I know which ones do what and when? There's a half dozen *-urlfilters. Why? 3. Why doesn't your post nightly compile tests include bin/nutch crawl or if it does, why didn't it find the error that stopped it from running? 4. Where is the documentation on how to configure the new tika parser in your environment? I see that the old parsers have been removed by default, but there's nothing that shows me how to include/exclude document types. I believe your assessment of 'ready' is not inclusive of some very important things and that you would be doing a service to newcomers to bring documentation in line with current offerings. This is not trivial code and it takes a long time for someone from the outside to understand it. That process is being stifled on multiple fronts as far as I can see. Either that or I have missed an important document that exists and I haven't read it. Phil Barnett Senior Programmer / Analyst Walt Disney World, Inc.
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
I also share many of Phil's sentiments. I really want the project (bin/nutch crawl) to work for me as well and I want to help somehow. I would like to share a 5gb 'intranet' web site with ~50 people. And I have not graduated to making the 'deepcrawl' script work yet either, as I'm thinking that maybe Nutch might not be the 'right tool' for 'little projects' based on documentation, discussion list feedback, etc. . . . -m. On Wed, 2010-04-28 at 06:59 -0400, Phil Barnett wrote: On Mon, Apr 26, 2010 at 1:55 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Please vote on releasing these packages as Apache Nutch 1.1. The vote is open for the next 72 hours. How do you test to see if Nutch works like the documentation says it works? I still find major differences between how existing documentation tells me, a newcomer to the project, how to get it running. For example, my find of broken code in bin/nutch crawl, a most basic way of getting it running. And I have yet to get the deepcrawl script which seems to be the suggestion of how to get beyond bin/nutch crawl. It doesn't return any data at all and has an error in the middle of it's run regarding missing file which the last stage apparently failed to write. (I believe because the scheduler excluded everything) I wonder if the developers have advanced so far past these basic scripts as to have pretty much left them behind. This leads to these basics that people start with not working. I've spend dozens of hours trying to get 1.1 to work anything like 1.0 and I'm getting nowhere at all. It's pretty frustrating to spend that much time trying to figure out how it works and keep hitting walls. And then asking basic questions here that go unanswered. The view from the outside is not so good from my direction. If you don't keep documentation up to date and you change the way things work, the project as seen from the outside, is plainly broken. I'd be happy to give you feedback on where I find these problems and I'll even donate whatever fixes I can come up with, but Java is not a language I'm familiar with and going is slow weeding through things. I really need this project to work for me. I want to help. 1. Where is the scheduler documented? If I want to crawl everything from scratch, where is the information from the last run stored? It seems like the schedule is telling my crawl to ignore pages due to scheduler knocking them out. It's not obvious to my why this is happening and how to stop it from happening. I think right now this is my major roadblock in getting bin/nutch crawl working. Maybe the scheduler code no longer works properly in bin/nutch crawl. I can't tell if it's that or if the default configurations don't work. 2, Where are the control files in conf documented? How do I know which ones do what and when? There's a half dozen *-urlfilters. Why? 3. Why doesn't your post nightly compile tests include bin/nutch crawl or if it does, why didn't it find the error that stopped it from running? 4. Where is the documentation on how to configure the new tika parser in your environment? I see that the old parsers have been removed by default, but there's nothing that shows me how to include/exclude document types. I believe your assessment of 'ready' is not inclusive of some very important things and that you would be doing a service to newcomers to bring documentation in line with current offerings. This is not trivial code and it takes a long time for someone from the outside to understand it. That process is being stifled on multiple fronts as far as I can see. Either that or I have missed an important document that exists and I haven't read it. Phil Barnett Senior Programmer / Analyst Walt Disney World, Inc.
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
Hi Phil, Thanks very much for the feedback. I¹d like to take a second to address your points: How do you test to see if Nutch works like the documentation says it works? I still find major differences between how existing documentation tells me, a newcomer to the project, how to get it running. Unfortunately some parts of the documentation on Nutch (namely the tutorial, and other parts of the static site) have been out of date for a while. This has occurred really independent of the releases, and independent of the wiki [1], which hasn't really fallen out of date as quick. For example, my find of broken code in bin/nutch crawl, a most basic way of getting it running. Can you elaborate on your find of broken code? Did you file a JIRA issue for this in the Nutch JIRA system [2] ? And I have yet to get the deepcrawl script which seems to be the suggestion of how to get beyond bin/nutch crawl. It doesn't return any data at all and has an error in the middle of it's run regarding missing file which the last stage apparently failed to write. (I believe because the scheduler excluded everything) The more information you provide here about your environment and your situation that caused the error, as well as e.g., detailed information (a stack trace, an exception, something), the easier it is to track down what you're seeing. I wonder if the developers have advanced so far past these basic scripts as to have pretty much left them behind. This leads to these basics that people start with not working. I wouldn't say developers have advanced beyond anything really for that matter :) The number of active developers in Nutch these days is fairly small, but interest and the user community is stable and there are some pretty large scale deployments of Nutch to my knowledge. That said, those folks have been following the mailing lists for a while, have been using the software for a while and thus their level of entry into the documentation may be at a little higher bar than that of a newer user such as yourself. That said, one thing to realize is that this is open source software, so in the end, as they say in Apache, those that do, decide, or patches welcome! In other words, if there are things that you see that could be fixed, improved, made more configurable, etc., including the code, but *also the documentation*, then by all means we'd appreciate your feedback and contribution. Nutch is not simply a product of the developers that contribute their (potentially and often unsalaried) time to work on it, but of its user community as well. I've spend dozens of hours trying to get 1.1 to work anything like 1.0 and I'm getting nowhere at all. It's pretty frustrating to spend that much time trying to figure out how it works and keep hitting walls. And then asking basic questions here that go unanswered. I apologize that your questions have gone unanswered and that you're hitting walls with regards to using Nutch. What questions did you ask? Perhaps it's the detail that you are providing (or not providing), or perhaps it's the way you're asking the questions. Or (even more likely) it's the fact that this is an open source project and thus the committers get around to user emails lists as one of the multiple items on their plate that they are working on the project and us committers may have missed your question, or perhaps those that had the time weren't particular experts in the one area of Nutch that you were asking about. There could be a number of reasons. Regardless, persistence is key as is *patience* and respectfulness. This has always to my knowledge been a really friendly community, so if you hang around and keep asking questions they will get answered I'm confident of that. The view from the outside is not so good from my direction. If you don't keep documentation up to date and you change the way things work, the project as seen from the outside, is plainly broken. In certain cases you are right, but I would take your above comments as verbatim across the board. For example, if you believe there is documentation lacking, then the first step is typically to file JIRA issues to alert committers and other users of Nutch of your concern and then have discussion on the lists regarding the issues. At some point a patch is produced, and then attached to the issue, where the committers can review the patches and then work to get them committed to the code base. Nutch has a number of unit tests for regression that ship with the product that tell me that it's not broken, and users that are able to make it work in their environments. There have been some recent bug fixes in the 1.1 RC that we caught which have been fixed (NUTCH-812, NUTCH-814, etc.), but that's natural. I'd be happy to give you feedback on where I find these problems and I'll even donate whatever fixes I can come up with, but Java is not a language I'm familiar with and going is slow weeding through
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
Hi Matthew, Thanks for your feedback. If you have any specific updates/improvements/actionable items based on your comments below, we'd love to have you contribute them back in the form of contributions to the community. Otherwise, we will take your feedback, put it into the queue of other items in the Nutch issue tracking system for those who are committers on the project to work on, as time permits. Apache has a process for meritocracy [1] in terms of contributing to projects and being recognized for those contributions - we welcome feedback and actionable things in the forms of patches that improve the code, documentation, add new features, etc., while maintaining backwards compatibility with existing deployments and existing users. Thanks and hope to see some issues/feedback/patches continue to come! Cheers, Chris [1] http://www.apache.org/foundation/how-it-works.html#meritocracy On 4/28/10 7:27 AM, matthew a. grisius mgris...@comcast.net wrote: I also share many of Phil's sentiments. I really want the project (bin/nutch crawl) to work for me as well and I want to help somehow. I would like to share a 5gb 'intranet' web site with ~50 people. And I have not graduated to making the 'deepcrawl' script work yet either, as I'm thinking that maybe Nutch might not be the 'right tool' for 'little projects' based on documentation, discussion list feedback, etc. . . . -m. On Wed, 2010-04-28 at 06:59 -0400, Phil Barnett wrote: On Mon, Apr 26, 2010 at 1:55 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Please vote on releasing these packages as Apache Nutch 1.1. The vote is open for the next 72 hours. How do you test to see if Nutch works like the documentation says it works? I still find major differences between how existing documentation tells me, a newcomer to the project, how to get it running. For example, my find of broken code in bin/nutch crawl, a most basic way of getting it running. And I have yet to get the deepcrawl script which seems to be the suggestion of how to get beyond bin/nutch crawl. It doesn't return any data at all and has an error in the middle of it's run regarding missing file which the last stage apparently failed to write. (I believe because the scheduler excluded everything) I wonder if the developers have advanced so far past these basic scripts as to have pretty much left them behind. This leads to these basics that people start with not working. I've spend dozens of hours trying to get 1.1 to work anything like 1.0 and I'm getting nowhere at all. It's pretty frustrating to spend that much time trying to figure out how it works and keep hitting walls. And then asking basic questions here that go unanswered. The view from the outside is not so good from my direction. If you don't keep documentation up to date and you change the way things work, the project as seen from the outside, is plainly broken. I'd be happy to give you feedback on where I find these problems and I'll even donate whatever fixes I can come up with, but Java is not a language I'm familiar with and going is slow weeding through things. I really need this project to work for me. I want to help. 1. Where is the scheduler documented? If I want to crawl everything from scratch, where is the information from the last run stored? It seems like the schedule is telling my crawl to ignore pages due to scheduler knocking them out. It's not obvious to my why this is happening and how to stop it from happening. I think right now this is my major roadblock in getting bin/nutch crawl working. Maybe the scheduler code no longer works properly in bin/nutch crawl. I can't tell if it's that or if the default configurations don't work. 2, Where are the control files in conf documented? How do I know which ones do what and when? There's a half dozen *-urlfilters. Why? 3. Why doesn't your post nightly compile tests include bin/nutch crawl or if it does, why didn't it find the error that stopped it from running? 4. Where is the documentation on how to configure the new tika parser in your environment? I see that the old parsers have been removed by default, but there's nothing that shows me how to include/exclude document types. I believe your assessment of 'ready' is not inclusive of some very important things and that you would be doing a service to newcomers to bring documentation in line with current offerings. This is not trivial code and it takes a long time for someone from the outside to understand it. That process is being stifled on multiple fronts as far as I can see. Either that or I have missed an important document that exists and I haven't read it. Phil Barnett Senior Programmer / Analyst Walt Disney World, Inc. ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop:
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
Might I suggest, that since Nutch is now a TLP that you delay this release by a few weeks and have the vote done under the auspices of the Nutch PMC? Cheers, Grant On Apr 26, 2010, at 1:55 AM, Mattmann, Chris A (388J) wrote: Hi Folks, I have posted an updated candidate for the Apache Nutch 1.1 release. The source code is at: http://people.apache.org/~mattmann/apache-nutch-1.1/rc2/ The major difference between this release and rc #1 is the application of NUTCH-812 - Crawl.java incorrectly uses the Generator API resulting in NPE - as well as some commits by Sami Siren to fix missing ASL license headers. For more detailed information, see the included CHANGES.txt file for details on release contents and latest changes. The release was made using the Nutch release process, documented on the Wiki here: http://bit.ly/d5ugid A Nutch 1.1 tag is at: http://svn.apache.org/repos/asf/lucene/nutch/tags/1.1/ note There was a request by Sami Siren that the tutorial be updated to reflect the fact that this release is a source-only release, as well as a request to integrate RAT into the build, however, in the interest of getting this 1.1 out and getting going on the Nutch TLP, my proposal is: * update the docs independent of this release (the tutorial as it exists right now says 0.7 on it anyways and doesn't look like it's been updated in a while, so I think users can live with what's there and support on u...@nutch.apache.org or d...@nutch.apache.org until it's updated) * begin source only releases in general since we've long had the debate as to the size of the Nutch release. Most folks that use Nutch are likely familiar with running ant IMHO. * run RAT and integrate into the build /note Please vote on releasing these packages as Apache Nutch 1.1. The vote is open for the next 72 hours. Since Nutch is now a TLP and has its own PMC, there is a question of who are the binding release VOTES in this particular thread. My gut reaction is that since I started this release while we were under the Lucene PMC, for continuity purposes, only votes from Lucene PMC are binding, but everyone (especially newly minted Nutch PMC members!) are welcome to check the release candidate and voice their approval or disapproval. The vote passes if at least three binding +1 votes are cast. [ ] +1 Release the packages as Apache Nutch 1.1. [ ] -1 Do not release the packages because... Thanks! Cheers, Chris P.S. Here is my +1. ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Running ANT; was -- Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
At 10:55 PM -0700 4/25/10, Mattmann, Chris A (388J) wrote: Most folks that use Nutch are likely familiar with running ant IMHO. I guess then I fall into the category of not most folks. Have been running Nutch for about 14 months and I haven't a clue how to run ant. If there's a place to vote to suggest that compiled versions still be distributed, I vote for that. Thanks. \dmc -- *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ David M. Coled...@colegroup.com Editor Publisher, NewsInc. http://newsinc.netV: (650) 557-2993 Consultant: The Cole Group http://colegroup.com/ F: (650) 475-8479 *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
Re: Running ANT; was -- Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
Hi David, Thanks. In fact, running ant is probably simpler than running Nutch. The steps would be: * what OS are you on (Ant is available for all of them to my knowledge)? * if you need ant, grab a distro from ant.apache.org, otherwise, I'll assume that you've got ant installed and callable from the command line. * unpack the nutch src distribution, cd into that directory, type ant job, and there you go. HTH! You could try it out by taking the Nutch src code from SVN at: http://svn.apache.org/repos/asf/lucene/nutch/tags/1.1, and then trying the steps above. Cheers, Chris On 4/26/10 7:24 AM, David M. Cole d...@colegroup.com wrote: At 10:55 PM -0700 4/25/10, Mattmann, Chris A (388J) wrote: Most folks that use Nutch are likely familiar with running ant IMHO. I guess then I fall into the category of not most folks. Have been running Nutch for about 14 months and I haven't a clue how to run ant. If there's a place to vote to suggest that compiled versions still be distributed, I vote for that. Thanks. \dmc -- *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ David M. Coled...@colegroup.com Editor Publisher, NewsInc. http://newsinc.netV: (650) 557-2993 Consultant: The Cole Group http://colegroup.com/ F: (650) 475-8479 *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Re: Running ANT; was -- Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
On 2010-04-26 16:24, David M. Cole wrote: At 10:55 PM -0700 4/25/10, Mattmann, Chris A (388J) wrote: Most folks that use Nutch are likely familiar with running ant IMHO. I guess then I fall into the category of not most folks. Have been running Nutch for about 14 months and I haven't a clue how to run ant. If there's a place to vote to suggest that compiled versions still be distributed, I vote for that. Actually, we don't have a build target (yet) that produces a binary-only distribution that we can ship and which you can run out of the box (not counting the build/nutch.job alone, because it needs the Hadoop infrastructure to run). The current mixed (source+binary) distribution worked well enough so far, but the size of the distribution is becoming a concern, hence the idea to ship only the source. We may have been too hasty with that, though... What do others think? -- Best regards, Andrzej Bialecki ___. ___ ___ ___ _ _ __ [__ || __|__/|__||\/| Information Retrieval, Semantic Web ___|||__|| \| || | Embedded Unix, System Integration http://www.sigram.com Contact: info at sigram dot com
Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
Hi Grant, Thanks. I think it actually makes sense to finish off 1.1, and since there is overlap with the Nutch PMC and the Lucene PMC and since the thread started in Lucene before the TLP, I think it would be great e.g., if Andrzej, and Sami could check the release and that way we still have the continuity and can safely push it out as the last Nutch rel under the Lucene umbrella... Then all releases post 1.1 can cleanly be done under the auspices of the new PMC :) Cheers, Chris On 4/26/10 5:34 AM, Grant Ignersoll gsing...@apache.org wrote: Might I suggest, that since Nutch is now a TLP that you delay this release by a few weeks and have the vote done under the auspices of the Nutch PMC? Cheers, Grant On Apr 26, 2010, at 1:55 AM, Mattmann, Chris A (388J) wrote: Hi Folks, I have posted an updated candidate for the Apache Nutch 1.1 release. The source code is at: http://people.apache.org/~mattmann/apache-nutch-1.1/rc2/ The major difference between this release and rc #1 is the application of NUTCH-812 - Crawl.java incorrectly uses the Generator API resulting in NPE - as well as some commits by Sami Siren to fix missing ASL license headers. For more detailed information, see the included CHANGES.txt file for details on release contents and latest changes. The release was made using the Nutch release process, documented on the Wiki here: http://bit.ly/d5ugid A Nutch 1.1 tag is at: http://svn.apache.org/repos/asf/lucene/nutch/tags/1.1/ note There was a request by Sami Siren that the tutorial be updated to reflect the fact that this release is a source-only release, as well as a request to integrate RAT into the build, however, in the interest of getting this 1.1 out and getting going on the Nutch TLP, my proposal is: * update the docs independent of this release (the tutorial as it exists right now says 0.7 on it anyways and doesn't look like it's been updated in a while, so I think users can live with what's there and support on u...@nutch.apache.org or d...@nutch.apache.org until it's updated) * begin source only releases in general since we've long had the debate as to the size of the Nutch release. Most folks that use Nutch are likely familiar with running ant IMHO. * run RAT and integrate into the build /note Please vote on releasing these packages as Apache Nutch 1.1. The vote is open for the next 72 hours. Since Nutch is now a TLP and has its own PMC, there is a question of who are the binding release VOTES in this particular thread. My gut reaction is that since I started this release while we were under the Lucene PMC, for continuity purposes, only votes from Lucene PMC are binding, but everyone (especially newly minted Nutch PMC members!) are welcome to check the release candidate and voice their approval or disapproval. The vote passes if at least three binding +1 votes are cast. [ ] +1 Release the packages as Apache Nutch 1.1. [ ] -1 Do not release the packages because... Thanks! Cheers, Chris P.S. Here is my +1. ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Re: Running ANT; was -- Re: [VOTE] Apache Nutch 1.1 Release Candidate #2
Hey Andrzej, Actually, we don't have a build target (yet) that produces a binary-only distribution that we can ship and which you can run out of the box (not counting the build/nutch.job alone, because it needs the Hadoop infrastructure to run). I thought ant tar did this? That's what it sez on the release guide [1] and what I'm familiar with when I did the Nutch 0.9 release. The current mixed (source+binary) distribution worked well enough so far, but the size of the distribution is becoming a concern, hence the idea to ship only the source. We may have been too hasty with that, though... What do others think? Good question, Andrzej. I'll wait for feedback from others. My pref is for source-only, but I might be in the minority. :) Cheers, Chris [1] http://wiki.apache.org/nutch/Release_HOWTO ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
[VOTE] Apache Nutch 1.1 Release Candidate #2
Hi Folks, I have posted an updated candidate for the Apache Nutch 1.1 release. The source code is at: http://people.apache.org/~mattmann/apache-nutch-1.1/rc2/ The major difference between this release and rc #1 is the application of NUTCH-812 - Crawl.java incorrectly uses the Generator API resulting in NPE - as well as some commits by Sami Siren to fix missing ASL license headers. For more detailed information, see the included CHANGES.txt file for details on release contents and latest changes. The release was made using the Nutch release process, documented on the Wiki here: http://bit.ly/d5ugid A Nutch 1.1 tag is at: http://svn.apache.org/repos/asf/lucene/nutch/tags/1.1/ note There was a request by Sami Siren that the tutorial be updated to reflect the fact that this release is a source-only release, as well as a request to integrate RAT into the build, however, in the interest of getting this 1.1 out and getting going on the Nutch TLP, my proposal is: * update the docs independent of this release (the tutorial as it exists right now says 0.7 on it anyways and doesn't look like it's been updated in a while, so I think users can live with what's there and support on u...@nutch.apache.org or d...@nutch.apache.org until it's updated) * begin source only releases in general since we've long had the debate as to the size of the Nutch release. Most folks that use Nutch are likely familiar with running ant IMHO. * run RAT and integrate into the build /note Please vote on releasing these packages as Apache Nutch 1.1. The vote is open for the next 72 hours. Since Nutch is now a TLP and has its own PMC, there is a question of who are the binding release VOTES in this particular thread. My gut reaction is that since I started this release while we were under the Lucene PMC, for continuity purposes, only votes from Lucene PMC are binding, but everyone (especially newly minted Nutch PMC members!) are welcome to check the release candidate and voice their approval or disapproval. The vote passes if at least three binding +1 votes are cast. [ ] +1 Release the packages as Apache Nutch 1.1. [ ] -1 Do not release the packages because... Thanks! Cheers, Chris P.S. Here is my +1. ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
