Re: ready for release 1.2
- - example/etc/LICENSE.javax.servlet.txt - - example/etc/LICENSE.javax.xml.html - - example/etc/LICENSE.jsse.txt We actually don't need to mention anything for Jetty in LICENSE.txt if it's all under the ASL2.0 But what about the CDDL license? should we remove it from LICENSE.txt? I think we probably need their NOTICE file though (copy it into ours). added in rev 542763
[jira] Commented: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500083 ] Erik Hatcher commented on SOLR-84: -- Those are great Steve! Thanks for submitting them. New Solr logo? -- Key: SOLR-84 URL: https://issues.apache.org/jira/browse/SOLR-84 Project: Solr Issue Type: Improvement Reporter: Bertrand Delacretaz Priority: Minor Attachments: logo-grid.jpg, logo-solr-d.jpg, logo-solr-e.jpg, logo-solr-source-files-take2.zip, solr-84-source-files.zip, solr-f.jpg, solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, solr-nick.gif, solr.jpg, sslogo-solr-flare.jpg, sslogo-solr.jpg, sslogo-solr2-flare.jpg, sslogo-solr2.jpg Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) sarraux-dessous.ch) has reworked his logo proposal to be more solar. This can either be the start of a logo contest, or if people like it we could adopt it. The gradients can make it a bit hard to integrate, not sure if this is really a problem. WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r542765 - /lucene/solr/trunk/build.xml
On 5/30/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
+++ lucene/solr/trunk/build.xml Tue May 29 23:45:56 2007
@@ -449,7 +449,7 @@
tarfileset dir=.
prefix=${fullnamever}
includes=LICENSE.txt NOTICE.txt *.txt *.xml lib/** src/** example/**
-excludes=**/data/ **/classes/ **/*.sh **/bin/ src/scripts/
src/site/build/ /
+excludes=**/data/ **/logs/* **/classes/ **/*.sh **/bin/ src/scripts/
src/site/build/
Ahh thanks... I had tried a couple of variations, but it got late ;-)
-Yonik
[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-trunk-542847.patch A revised version of the patch based on revision 542847. The patch was produced with the following command run from trunk directory: svn diff --diff-cmd /usr/bin/diff -x -w -B -b -E -d -N solr-trunk-542847.patch This should take care of the white spaces as well as inclusion of new files. All unit tests behave as in the single core version; 133 tests, 5 failures, 0 errors The content of the patch also includes modifications to the admin, servlet filters to accomodate the declaration handling of multiple cores. The example conf web.xml have been modified to declare 2 other cores (besides the default) named 'core0' and 'core1'. The filter itself forwards to the proper servlet if no specific handler exists in the core configuration. Example: Step0 java -Durl='http://localhost:8983/solr/core0/update' -jar post.jar solr.xml monitor.ml Will index the 2 documents in solr.xml monitor.xml Step1: http://localhost:8983/solr/core0/admin/stats.jsp Will produce the statistics page from the admin servlet on core0 index; 2 documents Step2: http://localhost:8983/solr/core1/admin/stats.jsp Will produce the statistics page from the admin servlet on core1 index; no documents Step3: java -Durl='http://localhost:8983/solr/core0/update' -jar post.jar ipod*.xml java -Durl='http://localhost:8983/solr/core1/update' -jar post.jar mon*.xml Adds the ipod*.xml to index of core0 and the mon*.xml to the index of core1; running queries from the admin interface, you can verify indexes have different content. Comments advice welcome. 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-trunk-533775.patch, solr-trunk-538091.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.
[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-trunk-542847-1.patch Supersedes previous patches (including solr-trunk-542847.patch); all other attached patches should be ignored ( removed by anyone with proper permissions?). Forgot to svn add some new files before creating the patch; fixed a stupid logic error in SolrInit when parameters were missing; added a way to get to the config schema file names from a configured core. 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-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.
[VOTE] release Solr 1.2
I propose to release the artifacts at http://people.apache.org/~yonik/staging_area/solr/1.2/ as Apache Solr 1.2 They were created from http://svn.apache.org/viewvc/lucene/solr/branches/branch-1.2/, branched today. I've verified the md5's and signatures after I uploaded to the staging area. I'll create the svn tag and release after the vote passes. Here's my +1 -Yonik
Re: [VOTE] release Solr 1.2
Just downloaded apache-solr-1.2.0.zip on vista. ant example works fine (except for a bunch of Warning: .. .java modified in the future.) +1 Yonik Seeley wrote: I propose to release the artifacts at http://people.apache.org/~yonik/staging_area/solr/1.2/ as Apache Solr 1.2 They were created from http://svn.apache.org/viewvc/lucene/solr/branches/branch-1.2/, branched today. I've verified the md5's and signatures after I uploaded to the staging area. I'll create the svn tag and release after the vote passes. Here's my +1 -Yonik
trunk is now 1.3
The solr trunk is now officially version 1.3, as we can make any tweaks we need for 1.2 (hopefully none) on that branch. So feel free to start updating the features page or tutorial, etc, before 1.2 is actually released (scheduled for saturday, but notices won't go out until sunday since it takes a little while to propagate to the mirrors). -Yonik
[jira] Commented: (SOLR-243) Create a hook to allow custome code to create custome index readers
[
https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500219
]
Yonik Seeley commented on SOLR-243:
---
Minor nit: is there a reason that IndexReaderFactory can't be a class instead
of an interface?
It doesn't seem to be a likely candidate for multiple inheritance, and making
it a class allows us to upgrade the interface in the future while providing a
backward compatible default implementation for people who have already
implemented it.
Create a hook to allow custome code to create custome index readers
---
Key: SOLR-243
URL: https://issues.apache.org/jira/browse/SOLR-243
Project: Solr
Issue Type: Improvement
Components: search
Affects Versions: 1.3
Environment: Solr core
Reporter: John Wang
Fix For: 1.3
Attachments: indexReaderFactory.patch, indexReaderFactory.patch
I have a customized IndexReader and I want to write a Solr plugin to use my
derived IndexReader implementation. Currently IndexReader instantiation is
hard coded to be:
IndexReader.open(path)
It would be really useful if this is done thru a plugable factory that can be
configured, e.g. IndexReaderFactory
interface IndexReaderFactory{
IndexReader newReader(String name,String path);
}
the default implementation would just return: IndexReader.open(path)
And in the newSearcher and getSearcher methods in SolrCore class can call the
current factory implementation to get the IndexReader instance and then build
the SolrIndexSearcher by passing in the reader.
It would be really nice to add this improvement soon (This seems to be a
trivial addition) as our project really depends on this.
Thanks
-John
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] release Solr 1.2
On 5/30/07, Yonik Seeley [EMAIL PROTECTED] wrote: ...I propose to release the artifacts at http://people.apache.org/~yonik/staging_area/solr/1.2/ as Apache Solr 1.2... +1 I haven't followed the latest developments, but all JUnit tests pass, example setup works (macosx/JDK1.5), and signatures and md5 look good (checked the tgz file only). -Bertrand
Re: Commented: (SOLR-216) Improvements to solr.py
On May 29, 2007, at 4:38 PM, Mike Klaas wrote:
I agree. I was not aware of field boosts at the time. I'll code
this change.
Unfortunately, it is still somewhat awkward. In my python client I
end up passing (name, value, field boost or None) everywhere,
but that clutters up the api considerably.
It might be worth taking a look at the ruby client to see what
Eric's done for the api.
In the ruby client, we have the ability to use a Ruby Hash as a
document when no boosts are needed:
doc = {:field = value}
But also use the Field object when boosts are desired:
doc = Solr::Document.new
doc Solr::Field.new(:field = value, :boost = 3.0)
The boost stuff was contributed by Coda Hale (credit where it's
due :) - I had punted on that initially.
Erik
Re: [VOTE] release Solr 1.2
+1 Looks good on RH Linux. Bill On 5/30/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote: On 5/30/07, Yonik Seeley [EMAIL PROTECTED] wrote: ...I propose to release the artifacts at http://people.apache.org/~yonik/staging_area/solr/1.2/ as Apache Solr 1.2... +1 I haven't followed the latest developments, but all JUnit tests pass, example setup works (macosx/JDK1.5), and signatures and md5 look good (checked the tgz file only). -Bertrand
Re: [VOTE] release Solr 1.2 -- ugho
I found a rather severe error... my fault, part of SOLR-249 I noticed that: http://localhost:8983/solr/update?stream.url=http://www.ask.com does not give me an error (it should!) In replacing the new SolrException( ), 2 files do not have the preceding throw -- it makes exceptions, but does not throw them!!! I will fix this on trunk and, http://svn.apache.org/repos/asf/lucene/solr/branches/branch-1.2/ sorry ryan
[jira] Updated: (SOLR-69) PATCH:MoreLikeThis support
[ https://issues.apache.org/jira/browse/SOLR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-69: -- Attachment: SOLR-69-MoreLikeThisRequestHandler.patch Updated patch to: * use searcher.getSchema().getAnalyzer() * be able to find similar documents from posted text * be able to return the interesting terms used for the MLT query Andrew: about field boosting... This handler uses the lucene contrib MoreLikeThis implementation -- that does not have a way to boost one field above another, If it did, we could easily add it ;) 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-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.
[jira] Commented: (SOLR-243) Create a hook to allow custome code to create custome index readers
[
https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500261
]
John Wang commented on SOLR-243:
Hi Yonik:
1) context in factory: I am not sure how the interface would look like,
suggestions?
2) I catch the exception to default to the normal IndexReader.open mechanism.
3) I just picked it to be an interface, I think making it an abstract class is
fine.
thanks
-John
Create a hook to allow custome code to create custome index readers
---
Key: SOLR-243
URL: https://issues.apache.org/jira/browse/SOLR-243
Project: Solr
Issue Type: Improvement
Components: search
Affects Versions: 1.3
Environment: Solr core
Reporter: John Wang
Fix For: 1.3
Attachments: indexReaderFactory.patch, indexReaderFactory.patch
I have a customized IndexReader and I want to write a Solr plugin to use my
derived IndexReader implementation. Currently IndexReader instantiation is
hard coded to be:
IndexReader.open(path)
It would be really useful if this is done thru a plugable factory that can be
configured, e.g. IndexReaderFactory
interface IndexReaderFactory{
IndexReader newReader(String name,String path);
}
the default implementation would just return: IndexReader.open(path)
And in the newSearcher and getSearcher methods in SolrCore class can call the
current factory implementation to get the IndexReader instance and then build
the SolrIndexSearcher by passing in the reader.
It would be really nice to add this improvement soon (This seems to be a
trivial addition) as our project really depends on this.
Thanks
-John
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-243) Create a hook to allow custome code to create custome index readers
[
https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500262
]
John Wang commented on SOLR-243:
My motivation in doing this is to create a plugin into solr for my project:
www.browseengine.com
or
bobo-browse.sourceforge.net
which is a more extensive facetted search implementation. I need a special
IndexReader to do the plugin.
Please take a look.
Thanks
-John
Create a hook to allow custome code to create custome index readers
---
Key: SOLR-243
URL: https://issues.apache.org/jira/browse/SOLR-243
Project: Solr
Issue Type: Improvement
Components: search
Affects Versions: 1.3
Environment: Solr core
Reporter: John Wang
Fix For: 1.3
Attachments: indexReaderFactory.patch, indexReaderFactory.patch
I have a customized IndexReader and I want to write a Solr plugin to use my
derived IndexReader implementation. Currently IndexReader instantiation is
hard coded to be:
IndexReader.open(path)
It would be really useful if this is done thru a plugable factory that can be
configured, e.g. IndexReaderFactory
interface IndexReaderFactory{
IndexReader newReader(String name,String path);
}
the default implementation would just return: IndexReader.open(path)
And in the newSearcher and getSearcher methods in SolrCore class can call the
current factory implementation to get the IndexReader instance and then build
the SolrIndexSearcher by passing in the reader.
It would be really nice to add this improvement soon (This seems to be a
trivial addition) as our project really depends on this.
Thanks
-John
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] release Solr 1.2 -- ugho
Heh... last minute patch bites again. I'm re-spinning the release now. -Yonik On 5/30/07, Ryan McKinley [EMAIL PROTECTED] wrote: I found a rather severe error... my fault, part of SOLR-249 I noticed that: http://localhost:8983/solr/update?stream.url=http://www.ask.com does not give me an error (it should!) In replacing the new SolrException( ), 2 files do not have the preceding throw -- it makes exceptions, but does not throw them!!! I will fix this on trunk and, http://svn.apache.org/repos/asf/lucene/solr/branches/branch-1.2/ sorry ryan
Re: [VOTE] release rc2 as Solr 1.2
Yonik Seeley wrote: Following a bug found and fixed by Ryan, ^ and *caused*! I'm glad I happened to be working with something that touched the problem today. SOLR-20 has some tests that fire up jetty, so next time this will be less likely. Here's my +1 (hopefully my last for this release ;-) +1 tests/example run on Vista + JDK 1.6
Re: [VOTE] release rc2 as Solr 1.2
+1 On May 30, 2007, at 9:23 PM, Yonik Seeley wrote: Following a bug found and fixed by Ryan, I rebuilt the release artifacts from branch-1.2 and placed them at http://people.apache.org/~yonik/staging_area/solr/1.2rc2/ Please vote to release these artifacts as Apache Solr 1.2 Here's my +1 (hopefully my last for this release ;-) -Yonik
how to customize solr
Hello, friends i'm new to working on solr. I downloaded the code from incubator but i din't get servlet code. 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 schema.xml given in the example But i saw when we run it on browser it called execute function in solrcore class.I want to know if i want to run the code and want to trace code where should i start it from. any help as i'm begginer for solr and want to work as developer. Thanks.. -- Regards Ashwani Kabra
