[jira] Updated: (SOLR-239) Read IndexSchema from InputStream instead of Config file
[ https://issues.apache.org/jira/browse/SOLR-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will Johnson updated SOLR-239: -- Attachment: IndexSchemaStream2.patch updated with fixed and test raw-schema.jsp and added back the IndexSchema testDynamicCopy() test. Read IndexSchema from InputStream instead of Config file Key: SOLR-239 URL: https://issues.apache.org/jira/browse/SOLR-239 Project: Solr Issue Type: Improvement Affects Versions: 1.2 Environment: all Reporter: Will Johnson Priority: Minor Fix For: 1.2 Attachments: IndexSchemaStream.patch, IndexSchemaStream2.patch, IndexSchemaStream2.patch, IndexSchemaStream2.patch Soon to follow patch adds a constructor to IndexSchema to allow them to be created directly from InputStreams. The overall logic for the Core's use of the IndexSchema creation/use does not change however this allows java clients like those in SOLR-20 to be able to parse an IndexSchema. Once a schema is parsed, the client can inspect an index's capabilities which is useful for building generic search UI's. ie provide a drop down list of fields to search/sort by. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r541391 - in /lucene/solr/trunk: CHANGES.txt example/solr/conf/xslt/example_atom.xsl example/solr/conf/xslt/example_rss.xsl
I'd slap versions to those 2 XSL files to immediately answer which version of
Atom|RSS does this produce?
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Search - Share
- Original Message
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 24, 2007 3:06:31 PM
Subject: svn commit: r541391 - in /lucene/solr/trunk: CHANGES.txt
example/solr/conf/xslt/example_atom.xsl example/solr/conf/xslt/example_rss.xsl
Author: hossman
Date: Thu May 24 12:06:29 2007
New Revision: 541391
URL: http://svn.apache.org/viewvc?view=revrev=541391
Log:
SOLR-208: example XSLTs for RSS and Atom
Added:
lucene/solr/trunk/example/solr/conf/xslt/example_atom.xsl (with props)
lucene/solr/trunk/example/solr/conf/xslt/example_rss.xsl (with props)
Modified:
lucene/solr/trunk/CHANGES.txt
Modified: lucene/solr/trunk/CHANGES.txt
URL:
http://svn.apache.org/viewvc/lucene/solr/trunk/CHANGES.txt?view=diffrev=541391r1=541390r2=541391
==
--- lucene/solr/trunk/CHANGES.txt (original)
+++ lucene/solr/trunk/CHANGES.txt Thu May 24 12:06:29 2007
@@ -197,7 +197,12 @@
33. SOLR-234: TrimFilter can update the Token's startOffset and endOffset
if updateOffsets=true. By default the Token offsets are unchanged.
(ryan)
-
+
+34. SOLR-208: new example_rss.xsl and example_atom.xsl to provide more
+examples for people about the Solr XML response format and how they
+can transform it to suit different needs.
+(Brian Whitman via hossman)
+
Changes in runtime behavior
1. Highlighting using DisMax will only pick up terms from the main
user query, not boost or filter queries (klaas).
Added: lucene/solr/trunk/example/solr/conf/xslt/example_atom.xsl
URL:
http://svn.apache.org/viewvc/lucene/solr/trunk/example/solr/conf/xslt/example_atom.xsl?view=autorev=541391
==
--- lucene/solr/trunk/example/solr/conf/xslt/example_atom.xsl (added)
+++ lucene/solr/trunk/example/solr/conf/xslt/example_atom.xsl Thu May 24
12:06:29 2007
@@ -0,0 +1,63 @@
+?xml version='1.0' encoding='UTF-8'?
+
+!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the License); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ --
+
+!--
+ Simple transform of Solr query results to Atom
+ --
+
+xsl:stylesheet version='1.0'
+xmlns:xsl='http://www.w3.org/1999/XSL/Transform'
+
+ xsl:output method=xml encoding=utf-8 /
+
+ xsl:template match='/'
+xsl:variable name=query select=response/[EMAIL
PROTECTED]'responseHeader']/[EMAIL PROTECTED]'params']/[EMAIL PROTECTED]'q']/
+feed xmlns=http://www.w3.org/2005/Atom;;
+ titleExample Solr Atom Feed/title
+ subtitle
+ This has been formatted by the sample example_atom.xsl transform -
+ use your own XSLT to get a nicer Atom feed.
+ /subtitle
+ author
+nameApache Solr/name
+email[EMAIL PROTECTED]/email
+ /author
+ link rel=self type=application/atom+xml
+
href=http://localhost:8983/solr/q={$query}amp;wt=xsltamp;tr=atom.xsl/
+ updated
+xsl:value-of select=response/result/doc[position()=1]/[EMAIL
PROTECTED]'timestamp']/
+ /updated
+ idtag:localhost,2007:example/id
+ xsl:apply-templates select=response/result/doc/
+/feed
+ /xsl:template
+
+ !-- search results xslt --
+ xsl:template match=doc
+xsl:variable name=id select=[EMAIL PROTECTED]'id']/
+entry
+ titlexsl:value-of select=[EMAIL PROTECTED]'name']//title
+ link href=http://localhost:8983/solr/select?q={$id}/
+ idtag:localhost,2007:xsl:value-of select=$id//id
+ summaryxsl:value-of select=[EMAIL PROTECTED]'features']//summary
+ updatedxsl:value-of select=[EMAIL PROTECTED]'timestamp']//updated
+/entry
+ /xsl:template
+
+/xsl:stylesheet
Propchange: lucene/solr/trunk/example/solr/conf/xslt/example_atom.xsl
--
svn:eol-style = native
Propchange: lucene/solr/trunk/example/solr/conf/xslt/example_atom.xsl
--
Re: svn commit: r541391 - in /lucene/solr/trunk: CHANGES.txt example/solr/conf/xslt/example_atom.xsl example/solr/conf/xslt/example_rss.xsl
: I'd slap versions to those 2 XSL files to immediately answer which : version of Atom|RSS does this produce? i'm comfortable calling the example_rss.xsl RSS, since most RSS readers will know what do do with it, but i don't know that i'm comfrotable calling it any specific version of RSS, people are more likely to get irrate about claiming ot be a specific version if one little thing is wrong then they are about not claiming to be anything in particular. example.xsl says it outputs HTML but doesn't make any specific claims about which version of (x)html ... not asserting any particular allegience in a holy war is a good way to avoid getting slaughtered :) -Hoss
Re: svn commit: r541391 - in /lucene/solr/trunk: CHANGES.txt example/solr/conf/xslt/example_atom.xsl example/solr/conf/xslt/example_rss.xsl
On 5/25/07 10:45 AM, Chris Hostetter [EMAIL PROTECTED] wrote: : I'd slap versions to those 2 XSL files to immediately answer which : version of Atom|RSS does this produce? i'm comfortable calling the example_rss.xsl RSS, since most RSS readers will know what do do with it, but i don't know that i'm comfrotable calling it any specific version of RSS, people are more likely to get irrate about claiming ot be a specific version if one little thing is wrong then they are about not claiming to be anything in particular. Some versions of RSS are quite incompatible, so we MUST say what version we are implementing. RSS 1.0 is completely different from the 0.9 series and 2.0. Atom doesn't have a version number, but RFC 4287 Atom is informally called 1.0. wunder
Re: svn commit: r541391 - in /lucene/solr/trunk: CHANGES.txt example/solr/conf/xslt/example_atom.xsl example/solr/conf/xslt/example_rss.xsl
Some versions of RSS are quite incompatible, so we MUST say what version we are implementing. RSS 1.0 is completely different from the 0.9 series and 2.0. Atom doesn't have a version number, but RFC 4287 Atom is informally called 1.0. The rss_example is supposed to be RSS 2.0. The atom_example validated on feedvalidator.org as Atom 1.0, I assume that's the RFC 4287.
[jira] Commented: (SOLR-69) PATCH:MoreLikeThis support
[ https://issues.apache.org/jira/browse/SOLR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499198 ] Andrew Nagy commented on SOLR-69: - A really nice feature would be to allow for boosting for fields, for example: ?q=id:1mlt=truemlt.fl=title^5,author^3,topic This would find items that are more similar to the title over the author, etc. PATCH:MoreLikeThis support -- Key: SOLR-69 URL: https://issues.apache.org/jira/browse/SOLR-69 Project: Solr Issue Type: Improvement Components: search Reporter: Bertrand Delacretaz Priority: Minor Attachments: lucene-queries-2.0.0.jar, lucene-queries-2.1.1-dev.jar, SOLR-69-MoreLikeThisRequestHandler.patch, SOLR-69-MoreLikeThisRequestHandler.patch, SOLR-69-MoreLikeThisRequestHandler.patch, SOLR-69.patch, SOLR-69.patch, SOLR-69.patch, SOLR-69.patch Here's a patch that implements simple support of Lucene's MoreLikeThis class. The MoreLikeThisHelper code is heavily based on (hmm...lifted from might be more appropriate ;-) Erik Hatcher's example mentioned in http://www.mail-archive.com/[EMAIL PROTECTED]/msg00878.html To use it, add at least the following parameters to a standard or dismax query: mlt=true mlt.fl=list,of,fields,which,define,similarity See the MoreLikeThisHelper source code for more parameters. Here are two URLs that work with the example config, after loading all documents found in exampledocs in the index (just to show that it seems to work - of course you need a larger corpus to make it interesting): http://localhost:8983/solr/select/?stylesheet=q=apacheqt=standardmlt=truemlt.fl=manu,catmlt.mindf=1mlt.mindf=1fl=id,score http://localhost:8983/solr/select/?stylesheet=q=apacheqt=dismaxmlt=truemlt.fl=manu,catmlt.mindf=1mlt.mindf=1fl=id,score Results are added to the output like this: response ... lst name=moreLikeThis result name=UTF8TEST numFound=1 start=0 maxScore=1.5293242 doc float name=score1.5293242/float str name=idSOLR1000/str /doc /result result name=SOLR1000 numFound=1 start=0 maxScore=1.5293242 doc float name=score1.5293242/float str name=idUTF8TEST/str /doc /result /lst I haven't tested this extensively yet, will do in the next few days. But comments are welcome of course. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Solr Wiki] Update of Solr1.2 by ryan
What about this blurb for CHANGES.txt? The Solr Request Handler framework has been updated in two key ways: First, if a Request Handler is registered in solrconfig.xml with a name starting with / then it can be accessed using path-based URL, instead of using the legacy /select?qt=name URL structure. Second, the Request Handler framework has been extended making it possible to write Request Handlers that process streams of data for doing updates, and there is a new-style Request Handler for XML updates given the name of /update in the example solrconfig.xml. Existing installations without this /update handler will continue to use the old update servlet and should see no changes in behavior. For new-stype update handlers, errors are now reflected in the HTTP status code, Content-type checking is more strict, and the response format has changed and is controllable via the wt parameter. -Yonik On 5/22/07, Apache Wiki [EMAIL PROTECTED] wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Solr Wiki for change notification. The following page has been changed by ryan: http://wiki.apache.org/solr/Solr1%2e2 -- framework has been extended making it possible to write Request Handlers that process streams of data for doing updates, and the existing XML-based update functionality has been refactored into a Request Handler given the name of /update in the example solrconfig.xml. - Existing Apache Solr installations that do not have references to this name in the - solrconfig.xml will be unaffected, but installations which do use it will now need to be - more explicit about the Content-Type when posting XML data, and will get a response format + Existing Apache Solr installations that do not reference /update in solrconfig.xml will + be unaffected. Installations that use it will need to explicitly define the Content-Type + when posting XML data (ie: curl ... -H 'Content-type:text/xml; charset=utf-8'), and will - controlled by the (wt) Response Writer. + get a new response format controlled by the (wt) Response Writer. }}} * delete example in the tutorial currently doesn't work because content type isn't specified .. tutorial could be fixed, but SOLR-230 would be a better use of time. * [https://issues.apache.org/jira/browse/SOLR-230 SOLR-230] should be done to keep the tutorial nice and portable and eliminate the need for curl
Re: [Solr Wiki] Update of Solr1.2 by ryan
small typo: changes in behavior. For new-stype update handlers, errors are now new-style otherwise looks good
