Related issue: on the example, the default core name is null, and
creates odd-looking log messages:
NFO: [null] /update 0 202
Dec 27, 2007 11:13:12 AM org.apache.solr.core.SolrCore execute
INFO: [null] /select/ indent=on&start=0&q=solr&version=2.2&rows=10 0 65
Dec 27, 2007 11:13:23 AM org.apache.solr.core.SolrCore execute
INFO: [null] /select
explainOther=&fl=*,score&indent=on&start=0&q=solr&hl.fl=&qt=standard&wt=
standard&hl=on&version=2.2&rows=10 0 3
Dec 27, 2007 11:13:35 AM org.apache.solr.core.SolrCore execute
INFO: [null] /select
explainOther=&fl=*,score&indent=on&start=0&q=solr&hl.fl=
+&qt=standard&wt=standard&hl=on&version=2.2&rows=10 0 1
Perhaps we should omit the [<corename>] if it is null?
-Mike
On 21-Dec-07, at 2:40 PM, Ryan McKinley (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-441?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley resolved SOLR-441.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Ryan McKinley
example app comes up with some bad links
----------------------------------------
Key: SOLR-441
URL: https://issues.apache.org/jira/browse/SOLR-441
Project: Solr
Issue Type: Bug
Environment: Mac OSX, java version "1.5.0_13", Firefox
Reporter: Mike Travers
Assignee: Ryan McKinley
Priority: Minor
Fix For: 1.3
The solr example comes up with bad links on the admin page. They
contain ?core=null, which results in an error when they are
clicked. Removing the "core=null" from the URLs makes it work OK.
This is mostly an annoyance, spoiling what would otherwise be a
very slick out-of-the-box experience.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
