URL: http://svn.apache.org/viewvc?rev=411943view=rev
Log:
Updating to Hadoop release 0.3.1. Hadoop now uses Jakarta Commons
Logging, configured for log4j by default.
If log4j is now included in the core, we can remove the lib-log4j plugin.
If no objection, I will doing it.
Jérôme
--
As far I understand hadoop use commons logging. Should we switch to
use commons logging as well?
Am 06.06.2006 um 11:02 schrieb Jérôme Charron:
URL: http://svn.apache.org/viewvc?rev=411943view=rev
Log:
Updating to Hadoop release 0.3.1. Hadoop now uses Jakarta Commons
Logging, configured
[
http://issues.apache.org/jira/browse/NUTCH-294?page=comments#action_12414960 ]
Dawid Weiss commented on NUTCH-294:
---
Ehm, sorry I'm so late with this -- tons of work.
1) Stefan, if you can't get it working, speak up what is not working
(exceptions?
[
http://issues.apache.org/jira/browse/NUTCH-294?page=comments#action_12414962 ]
Stefan Neufeind commented on NUTCH-294:
---
1) I enabled it in plugins.include and restarted tomcat - but there is no
checkbox for me.
2) My idea was if maybe an index of
As far I understand hadoop use commons logging. Should we switch to
use commons logging as well?
Why not...
(but using commons logging doesn't exclude to have a default implementation,
such as log4j used by hadoop).
Stefan Groschupf wrote:
As far I understand hadoop use commons logging. Should we switch to use
commons logging as well?
+1
Doug
[
http://issues.apache.org/jira/browse/NUTCH-48?page=comments#action_12415016 ]
Sami Siren commented on NUTCH-48:
-
stefan, I tried to apply your combined patch but it seems that the test case
does not compile.
Did you mean query enhancement/refignment
Piotr,
is there a reason why this (among other) documentation (for all relevant
versions)
could not be maintained in trunk?
--
Sami Siren
Piotr Kosiorowski wrote:
Andrzej Bialecki wrote:
+1, yes it would be really confusing. Since there are more and more
people trying 0.8, could we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody,
does anyone know, if there is a relatively easy way to make Nutch use
wildcards and / or regular expressions for searching instead of the
default BooleanQuery?
I have already tried a more or less naive approach by replacing all
Sami Siren wrote:
hmm... didn't think about that, are there more opinions about this?
--
Sami Siren
Are you sure there is no trademark infringement here? Perhaps we
should call it something else, just to avoid any potential legal
unpleasantries ...
FYI, the records at USPTO.gov seem to
CommonGrams loads analysis.common.terms.file for each query
---
Key: NUTCH-301
URL: http://issues.apache.org/jira/browse/NUTCH-301
Project: Nutch
Type: Improvement
Components: searcher
Versions:
11 matches
Mail list logo
