Could not initialize class org.apache.solr.core.SolrCore

2007-01-10 Thread Cook, Jeryl
Title: Could not initialize class org.apache.solr.core.SolrCore I am sure this is a dumb mistake, but i followed the set up of SOLR/tomcat 5.5.20, but i keep getting this error.. java.lang.NoClassDefFoundError: Could not initialize class org.apache.solr.core.SolrCore

[jira] Updated: (SOLR-99) Allow default sort order

2007-01-10 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-99: -- Attachment: DefaultSortOrder.patch Allow default sort order

[jira] Commented: (SOLR-99) Allow default sort order

2007-01-10 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463530 ] Ryan McKinley commented on SOLR-99: --- I apologize... the first version does not pass

Re: Could not initialize class org.apache.solr.core.SolrCore

2007-01-10 Thread Yonik Seeley
On 1/10/07, Cook, Jeryl [EMAIL PROTECTED] wrote: I am sure this is a dumb mistake, but i followed the set up of SOLR/tomcat 5.5.20, but i keep getting this error.. java.lang.NoClassDefFoundError: Could not initialize class org.apache.solr.core.SolrCore Look for the first errors that appear

Re: Handling disparate data sources in Solr

2007-01-10 Thread Alan Burlison
Chris Hostetter wrote: : 1. The document is already decomposed into fields before the : insert/update, but one or more of the fields requires special handling. : 2. The document contains both metadata and content. PDF is a good : example of such a document type. there's a third big example:

Re: Could not initialize class org.apache.solr.core.SolrCore

2007-01-10 Thread Richard Lawson
I just ran into this myself, it's because there is no jndi entry for solr.home. A little further down on the wiki for installing tomcat is the instruction to create a solr.xml file and place it in TOMCAT_HOME/conf/Catalina/localhost you have to change the Environment entry to point to your

[jira] Updated: (SOLR-100) Exception handling for Solrb w/ test

2007-01-10 Thread William Groppe (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Groppe updated SOLR-100: Attachment: exception_handling.patch Exception handling for Solrb w/ test

[jira] Created: (SOLR-100) Exception handling for Solrb w/ test

2007-01-10 Thread William Groppe (JIRA)
Exception handling for Solrb w/ test Key: SOLR-100 URL: https://issues.apache.org/jira/browse/SOLR-100 Project: Solr Issue Type: Improvement Components: clients - ruby - flare

[jira] Commented: (SOLR-99) Allow default sort order

2007-01-10 Thread Hoss Man (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463695 ] Hoss Man commented on SOLR-99: -- specifying the number of results to return as part of the sort information is in fact

[jira] Commented: (SOLR-99) Allow default sort order

2007-01-10 Thread Yonik Seeley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463702 ] Yonik Seeley commented on SOLR-99: -- The number was there because I originally thought about allowing a chain of sorts

Re: Update Plugins (was Re: Handling disparate data sources in Solr)

2007-01-10 Thread Chris Hostetter
: indexing app I wrote into SOLR. It occurred to me that it would almost : be simpler to use the plugin-friendly QueryRequest mechanism rather than : the UpdateRequest mechanism; coupled with what you wrote below, Hoss, it : makes me think that a little refactoring of request handling might go a

Re: Handling disparate data sources in Solr

2007-01-10 Thread Chris Hostetter
: Hmm. Any idea of how much work this involves? As I said I can put time : towards this, but I don't know the innards of Solr as well as you and : the other folks on this list. I really can't even guess ... i've never even really looked at the current update code. :) -Hoss

[jira] Commented: (SOLR-99) Allow default sort order

2007-01-10 Thread Yonik Seeley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463740 ] Yonik Seeley commented on SOLR-99: -- I agree that throwing a ParseException (ideally a SolrException with a code of

[jira] Commented: (SOLR-99) Allow default sort order

2007-01-10 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463813 ] Ryan McKinley commented on SOLR-99: --- Ok, we all agree, that it should 1. Throw a reasonable error if something goes

adding modes to the add command

2007-01-10 Thread Ryan McKinley
How do you all feel about adding various modes to the add command? Something like: mode=add or replace document (default, the current behavior) mode=add or replace fields mode=add fields mode=add distinct fields The reason i ask is that i would like to frequently update a few fields without

SQL UpdatePlugin?

2007-01-10 Thread Ryan McKinley
I'd like to be able to add/update documents from an SQL query. Perhaps: addFromSQL mode=add or replace fields connection=jdbc:mysql://localhost/nblmc?username=xxxpassword=xxx driver=com.mysql.jdbc.Driver multifieldSeperator=\n SELECT * FROM my_stats_table /addFromSQL This would use the

Re: adding modes to the add command

2007-01-10 Thread Bertrand Delacretaz
On 1/11/07, Ryan McKinley [EMAIL PROTECTED] wrote: How do you all feel about adding various modes to the add command? Something like: mode=add or replace document (default, the current behavior) mode=add or replace fields mode=add fields mode=add distinct fields... Although this is useful