This means there's no markup in the OpenSearch output?
Yes, no markup for now.
Shouldn't there be?
The restriction on description field is : Can contain simple escaped HTML
markup, such as b, i, a, and img elements.
So, ya, why not. We can add b around highlights.
What you and others
Jérôme Charron wrote:
This means there's no markup in the OpenSearch output?
Yes, no markup for now.
Doesn't this break any existing application that uses OpenSearch and
displays summaries in a web browser? This is an incompatible change
which we should avoid.
Shouldn't there be?
YourSoft írta:
Hi,
I have a suggestion to improve nutch search results.
The big search engines (like google) measure the distance between
the query words.
E.g.:
query string: lucene in action
When you search for it in google, google will boost up that documents
where the lucene in action is
Doesn't this break any existing application that uses OpenSearch and
displays summaries in a web browser? This is an incompatible change
which we should avoid.
Also a friendly hint to all plugin hackers, you need to enable
summary-basic in your existing nutch-site.xml to get things
Hi all,
i start nutch-0.8-dev (Revision 405738) on distributed filesystem.
If i execute bin/hadoop dfs -report an exception occurs.
java.lang.RuntimeException: java.lang.IllegalAccessException: Class
org.apache.hadoop.io.WritableFactories can not access a member of
class
Sami Siren wrote:
Doesn't this break any existing application that uses OpenSearch and
displays summaries in a web browser? This is an incompatible change
which we should avoid.
Also a friendly hint to all plugin hackers, you need to enable
summary-basic in your existing nutch-site.xml
This is a known, fixed, Hadoop bug:
http://issues.apache.org/jira/browse/HADOOP-201
I'm going to release Hadoop 0.2.1 with this and one other patch as soon
as Subversion is back up, then upgrade Nutch to use 0.2.1.
Doug
Marko Bauhardt wrote:
Hi all,
i start nutch-0.8-dev (Revision
String toString(Encoder, Formatter) like in the Lucene's Highlighter and
provide some basic implementations of Encoder and Formatter.
That sounds fine, but in the meantime, let's not reproduce the
html-specific code in lots of places. We need it in both search.jsp and
in
What would be good issues to tackle, bugs to fix in either Nutch or the
Hadoop code base. I lookup through the JIRA but don' t really
understand if things are being worked on or not?
Dennis
Jérôme Charron wrote:
Yes Doug, but in fact, the idea is to add the toString(Formatter) method in
a common place (Summary).
And add one specific Formatter implementation for OpenSearch and another
one
for search.jsp :
The reason is that they should not use the same HTML code :
1. OpenSearch
10 matches
Mail list logo
