Re: [VOTE] release rc3 as Solr 1.2
On Thu, 2007-05-31 at 19:02 -0400, Yonik Seeley wrote: > Sorry folks... one more time. This release candidate fixes SOLR-250 > (scripts need to tell curl the content-type), as well as the minor > README typo. > > Please vote to release the artifacts at > http://people.apache.org/~yonik/staging_area/solr/1.2rc3/ > as Apache Solr 1.2 > > +1 Did a quick test. +1 salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
Re: how to customize solr
No problem Thanks.. On 6/1/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: : I just would like to know if you can tell how can I trace the code through : servlet code to how it is flowing with what value. I'm using netbeans to : tracing the code. Sorry, I can't help you there ... i don't use debuggers with servlet containers. -Hoss -- Regards Ashwani Kabra
Re: how to customize solr
: I just would like to know if you can tell how can I trace the code through : servlet code to how it is flowing with what value. I'm using netbeans to : tracing the code. Sorry, I can't help you there ... i don't use debuggers with servlet containers. -Hoss
Re: how to customize solr
Thanks. Chris... I had got all and got the code and understood it. Now i can go ahead with this. but last thing is that i always work on windows and console application so i'm weaker in Servlet and jsp. I just would like to know if you can tell how can I trace the code through servlet code to how it is flowing with what value. I'm using netbeans to tracing the code. Thanks again Regards Ashwani Kabra
Re: how to customize solr
: friends i'm new to working on solr. I downloaded the code from incubator but : i din't get servlet code. servlet code is located in the src/webapp directory. : I want to see the code that how it is working and flowing but when i tried : it using testharness class it din't work for me..I used the solrconfig.xmland can you elaborate on "didn't work for me" ... the testharness is just a class, it requires you to write the code arround it ... what was your code? what outcome did you expect? what outcome did you get? was there an exception? what was the stack trace? : class.I want to know if i want to run the code and want to trace code where : should i start it from. the best way to understand the Solr code base is not to trace every line of code .. start by looking at the high level APIs, make sure you understand *conceptually* what things like hte StandardRequestHandler are doing (even if you don't how the meth'ds it calls work) then you can dig into the specific mehtods you are interested in. I recommend anyone who wants to get there hands dirty with the *guts* of Solr start by writting a few plugins... http://wiki.apache.org/solr/SolrPlugins -Hoss
Re: [VOTE] release rc3 as Solr 1.2
+1 Yonik Seeley wrote: Sorry folks... one more time. This release candidate fixes SOLR-250 (scripts need to tell curl the content-type), as well as the minor README typo. Please vote to release the artifacts at http://people.apache.org/~yonik/staging_area/solr/1.2rc3/ as Apache Solr 1.2 +1 -Yonik
Re: [VOTE] release rc3 as Solr 1.2
+1 again! :) On May 31, 2007, at 7:02 PM, Yonik Seeley wrote: Sorry folks... one more time. This release candidate fixes SOLR-250 (scripts need to tell curl the content-type), as well as the minor README typo. Please vote to release the artifacts at http://people.apache.org/~yonik/staging_area/solr/1.2rc3/ as Apache Solr 1.2 +1 -Yonik
[VOTE] release rc3 as Solr 1.2
Sorry folks... one more time. This release candidate fixes SOLR-250 (scripts need to tell curl the content-type), as well as the minor README typo. Please vote to release the artifacts at http://people.apache.org/~yonik/staging_area/solr/1.2rc3/ as Apache Solr 1.2 +1 -Yonik
[jira] Resolved: (SOLR-250) wrong content-type sent from scripts (commit, optimize, etc)
[ https://issues.apache.org/jira/browse/SOLR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-250. --- Resolution: Fixed fixed by specifying the content-type when using curl in the scripts. > wrong content-type sent from scripts (commit, optimize, etc) > > > Key: SOLR-250 > URL: https://issues.apache.org/jira/browse/SOLR-250 > Project: Solr > Issue Type: Bug >Reporter: Yonik Seeley >Assignee: Yonik Seeley > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SOLR-250) wrong content-type sent from scripts (commit, optimize, etc)
[ https://issues.apache.org/jira/browse/SOLR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley reassigned SOLR-250: - Assignee: Yonik Seeley > wrong content-type sent from scripts (commit, optimize, etc) > > > Key: SOLR-250 > URL: https://issues.apache.org/jira/browse/SOLR-250 > Project: Solr > Issue Type: Bug >Reporter: Yonik Seeley >Assignee: Yonik Seeley > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-250) wrong content-type sent from scripts (commit, optimize, etc)
wrong content-type sent from scripts (commit, optimize, etc) Key: SOLR-250 URL: https://issues.apache.org/jira/browse/SOLR-250 Project: Solr Issue Type: Bug Reporter: Yonik Seeley -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] release rc2 as Solr 1.2
: The standard scripts that talk to solr are now broken because they use : curl but didn't set Content-type (which defaults to Content-Type: : application/x-www-form-urlencoded, which is incorrect if we are : sending XML). Damn you curl! ... i guess we should fix this huh? -Hoss
Re: [VOTE] release rc2 as Solr 1.2
Argg. The standard scripts that talk to solr are now broken because they use curl but didn't set Content-type (which defaults to Content-Type: application/x-www-form-urlencoded, which is incorrect if we are sending XML). May 31, 2007 3:32:00 PM org.apache.solr.core.SolrException log SEVERE: org.apache.solr.core.SolrException: missing content stream I never noticed, since I don't use the scripts myself... but they are used in a master/slave setup. -Yonik
[jira] Assigned: (SOLR-69) PATCH:MoreLikeThis support
[ https://issues.apache.org/jira/browse/SOLR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley reassigned SOLR-69: - Assignee: Ryan McKinley > 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 >Assignee: Ryan McKinley >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-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=apache&qt=standard&mlt=true&mlt.fl=manu,cat&mlt.mindf=1&mlt.mindf=1&fl=id,score > http://localhost:8983/solr/select/?stylesheet=&q=apache&qt=dismax&mlt=true&mlt.fl=manu,cat&mlt.mindf=1&mlt.mindf=1&fl=id,score > Results are added to the output like this: > > ... > > > > 1.5293242 > SOLR1000 > > > > > 1.5293242 > UTF8TEST > > > > 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: [VOTE] release rc2 as Solr 1.2
+1 Bill On 5/31/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: somehow, we got a "g" typo in the jar name in the list of files in the README, but i don't think that's a big enough issue to worry about. +1 -Hoss
[jira] Updated: (SOLR-215) Multiple Solr Cores
[
https://issues.apache.org/jira/browse/SOLR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated SOLR-215:
---
Attachment: solr-215.patch
Thanks Mike for your usefull advice;
I've corrected the (modified) tests so they are now behaving as the non-patched
version do (aka no error nor failure, 133 tests); there were still some of them
using the 'unnamed/null' core. My bad, thanks again for pointing it out.
The 'superseding' patch is now called solr-215.patch so JIRA should take care
of keeping only the last version. (all others can be ignored & deleted).
This drop is based on svn revision 543145.
> Multiple Solr Cores
> ---
>
> Key: SOLR-215
> URL: https://issues.apache.org/jira/browse/SOLR-215
> Project: Solr
> Issue Type: Improvement
>Reporter: Henri Biestro
>Priority: Minor
> Attachments: solr-215.patch, solr-trunk-533775.patch,
> solr-trunk-538091.patch, solr-trunk-542847-1.patch, solr-trunk-542847.patch,
> solr-trunk-src.patch
>
>
> Allow multiple cores in one web-application (or one class-loader):
> This allows to have multiple cores created from different config & schema in
> the same application.
> The side effect is that this also allows different indexes.
> Implementation notes for the patch:
> The patch allows to have multiple 'named' cores in the same application.
> The current single core behavior has been retained - the core named 'null' -
> but code could not be kept 100% compatible. (In particular, Solrconfig.config
> is gone; SolrCore.getCore() is still here though).
> A few classes were only existing as singletons and have thus been refactored.
> The Config class feature-set has been narrowed to class loading relative to
> the installation (lib) directory;
> The SolrConfig class feature-set has evolved towards the 'solr config' part,
> caching frequently accessed parameters;
> The IndexSchema class uses a SolrConfig instance; there are a few parameters
> in the configuration that pertain to indexing that were needed.
> The SolrCore is built from a SolrConfig & an IndexSchema.
> The creation of a core has become:
> //create a configuration
> SolrConfig config = SolrConfig.createConfiguration("solrconfig.xml");
> //create a schema
> IndexSchema schema = new IndexSchema(config, "schema0.xml");
> //create a core from the 2 other.
> SolrCore core = new SolrCore("core0", "/path/to/index", config, schema);
> //Accessing a core:
> SolrCore core = SolrCore.getCore("core0");
> There are few other changes mainly related to passing through constructors
> the SolrCore/SolrConfig used.
> Some background on the 'whys':
> http://www.nabble.com/Multiple-Solr-Cores-tf3608399.html#a10082201
> http://www.nabble.com/Embedding-Solr-vs-Lucene%2C-multiple-Solr-cores--tf3572324.html#a9981355
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] release rc2 as Solr 1.2
somehow, we got a "g" typo in the jar name in the list of files in the README, but i don't think that's a big enough issue to worry about. +1 -Hoss
