You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Stefan Matheis (steffkes) (Created) (JIRA)" <ji...@apache.org> on 2012/03/13 10:21:38 UTC
[jira] [Created] (SOLR-3238) Sequel of Admin UI
Sequel of Admin UI
------------------
Key: SOLR-3238
URL: https://issues.apache.org/jira/browse/SOLR-3238
Project: Solr
Issue Type: Improvement
Components: web gui
Reporter: Stefan Matheis (steffkes)
Assignee: Stefan Matheis (steffkes)
Fix For: 4.0
Catchall Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262180#comment-13262180 ]
Ryan McKinley commented on SOLR-3238:
-------------------------------------
I like the idea of adding version to the param string -- that could be initalized in index.html too
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232007#comment-13232007 ]
Stefan Matheis (steffkes) commented on SOLR-3238:
-------------------------------------------------
Chen, that's correct .. i've [fixed|https://github.com/steffkes/solr-admin/commit/7b2129d9969c90dae23c74d36b1eae3704b2df3d] that already a few days ago while improving the handling of dataimports. Actually preparing the patch which includes this change.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Vadim Kisselmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230056#comment-13230056 ]
Vadim Kisselmann commented on SOLR-3238:
----------------------------------------
It's weird:)
"ant run-example" starts server with jetty, and it works.
As next step i build it one more time with "ant example" and start my tomcat, and it works, too.
When i update to new Solr version form trunk, and build it with "ant example", i get this error again.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264273#comment-13264273 ]
Stefan Matheis (steffkes) commented on SOLR-3238:
-------------------------------------------------
bq. cloud/zookeeper-data cannot show the node tree as the previous version.It says 'Fetch zookeeper data'without showing anything of the solr node.
Sorry Emma, i overlooked your comment - is it still not working for you?
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234227#comment-13234227 ]
Stefan Matheis (steffkes) commented on SOLR-3238:
-------------------------------------------------
bq. New Issue?
Vadim, i think that would make sense yes :)
The Code which shows the error message you've mentioned on the first comment, is this one: https://github.com/steffkes/solr-admin/blob/master/js/scripts/app.js#L212 - it's requesting {{/admin/system}}
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3238) Sequel of Admin UI
Posted by "Vadim Kisselmann (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230104#comment-13230104 ]
Vadim Kisselmann edited comment on SOLR-3238 at 3/15/12 1:14 PM:
-----------------------------------------------------------------
Now i have error messages:
SCHWERWIEGEND: The web application [/solr2] appears to have started a thread named [main-SendThread(zookeeper:2181)] but has failed to stop it. This is very likely to create a memory leak.
Exception in thread "Thread-2" java.lang.NullPointerException
at org.apache.solr.cloud.Overseer$CloudStateUpdater.amILeader(Overseer.java:179)
at org.apache.solr.cloud.Overseer$CloudStateUpdater.run(Overseer.java:104)
at java.lang.Thread.run(Thread.java:662)
15.03.2012 13:25:17 org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.zookeeper.server.ZooTrace. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1531)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1196)
15.03.2012 13:25:17 org.apache.coyote.http11.Http11Protocol destroy
SLF4J: The requested version 1.5.8 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
log4j:WARN No appenders could be found for logger (org.apache.solr.core.SolrResourceLoader).
log4j:WARN Please initialize the log4j system properly.
Steps:
I deleted the one default core in solr.xml, because i would create new cores with CoreAdminHandler.
I started tomcat.
Now it's completely broken. Rebuild and restart, whether jetty or tomcat, change nothing.
EDIT:
i get the same problem on another server(tomcat, sharded, without ZK). With an old revision from Feb. it works,
with new checkout from trunk not.
EDIT2:
It works when i remove the example-folder, checkout new version from trunk and rebuild it. i think it's a problem
with solr.xml. On server-restart it breaks. With older revisions like r1292064 from Feb. it works.
I think you're right, this has nothing to do with the admin UI. Sorry for spam here.
New Issue?
was (Author: ldb):
Now i have error messages:
SCHWERWIEGEND: The web application [/solr2] appears to have started a thread named [main-SendThread(zookeeper:2181)] but has failed to stop it. This is very likely to create a memory leak.
Exception in thread "Thread-2" java.lang.NullPointerException
at org.apache.solr.cloud.Overseer$CloudStateUpdater.amILeader(Overseer.java:179)
at org.apache.solr.cloud.Overseer$CloudStateUpdater.run(Overseer.java:104)
at java.lang.Thread.run(Thread.java:662)
15.03.2012 13:25:17 org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.zookeeper.server.ZooTrace. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1531)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1196)
15.03.2012 13:25:17 org.apache.coyote.http11.Http11Protocol destroy
SLF4J: The requested version 1.5.8 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
log4j:WARN No appenders could be found for logger (org.apache.solr.core.SolrResourceLoader).
log4j:WARN Please initialize the log4j system properly.
Steps:
I deleted the one default core in solr.xml, because i would create new cores with CoreAdminHandler.
I started tomcat.
Now it's completely broken. Rebuild and restart, whether jetty or tomcat, change nothing.
EDIT:
i get the same problem on another server(tomcat, sharded, without ZK). With an old revision from Feb. it works,
with new checkout from trunk not.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Matheis (steffkes) updated SOLR-3238:
--------------------------------------------
Description: Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI (was: Catchall Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI)
Affects Version/s: 4.0
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Shawn Heisey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291422#comment-13291422 ]
Shawn Heisey commented on SOLR-3238:
------------------------------------
bq. Yes, use normal solr requests. If you turn on firebug (or equivalent) you can see what the UI is actually calling to get out the machine readable values. For cache stats, that will be something like: http://localhost:8983/solr/admin/mbeans?stats=true&wt=json
Awesome! I can even use wt=xml and modify my Perl script for any differences between 3.x and 4.x. I have just tried the same URL on 3.x and found that it works there, too. My scripts currently use the stats.jsp and a couple of other URLs, not mbeans. I will have to experiment, but do you know of any documentation that covers everything that's available?
With SolrJ, currently I can use ModifiableSolrParams and set qt to /admin/mbeans to make this work. In the wake of issues like SOLR-3161, SolrJ might need a new way to specify the base URL path.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262146#comment-13262146 ]
Ryan McKinley commented on SOLR-3238:
-------------------------------------
For the real release we want a long cache. (though it is an admin UI, so its not all that important)
for JS dev, can't you just disable HTTP cache in FF/firebug?
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Benson Margulies (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249979#comment-13249979 ]
Benson Margulies commented on SOLR-3238:
----------------------------------------
It would be nice to see a total document count across the shards.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3238) Sequel of Admin UI
Posted by "Vadim Kisselmann (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230056#comment-13230056 ]
Vadim Kisselmann edited comment on SOLR-3238 at 3/15/12 10:47 AM:
------------------------------------------------------------------
It's weird:)
"ant run-example" starts server with jetty, and it works.
As next step i build it one more time with "ant example" and start my tomcat, and it works, too.
When i update to new Solr version from trunk, and build it with "ant example", i get this error again.
was (Author: ldb):
It's weird:)
"ant run-example" starts server with jetty, and it works.
As next step i build it one more time with "ant example" and start my tomcat, and it works, too.
When i update to new Solr version form trunk, and build it with "ant example", i get this error again.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Matheis (steffkes) updated SOLR-3238:
--------------------------------------------
Attachment: SOLR-3238.patch
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "dylan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253059#comment-13253059 ]
dylan commented on SOLR-3238:
-----------------------------
Chinese words collected by admin ui are not correctly recognized by /analysis/field or /select.
1. open admin ui. Singlre Core > Query.
add q: name:中文
and I get the following information in tomcat's log:
path=/select params={wt=xml&rows=10&start=0&q=name:?????￥} hits=0 status=0 QTime=2
2. open admin ui. Singlre Core > Analysis.
FieldValue: 中文
and I get the following information in tomcat's log:
path=/analysis/field params={analysis.showmatch=true&analysis.query=&analysis.fieldname=ageseg&analysis.fieldvalue=?????￥&wt=json} status=0 QTime=2
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Vadim Kisselmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230030#comment-13230030 ]
Vadim Kisselmann commented on SOLR-3238:
----------------------------------------
I use Solr 4.0 from trunk(latest) with tomcat6.
I get an error in New Admin UI (since one week, i update every day from trunk):
This interface requires that you activate the admin request handlers, add the following configuration to your solrconfig.xml:
<!-- Admin Handlers - This will register all the standard admin RequestHandlers. -->
<requestHandler name="/admin/" class="solr.admin.AdminHandlers" />
Admin request Handlers are definitely activated in my solrconfig.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Shawn Heisey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264359#comment-13264359 ]
Shawn Heisey commented on SOLR-3238:
------------------------------------
I have just fired up the example from a trunk checkout that's a day or two old and taken a quick look.
On the analysis page: Is it possible to have the information fields always appear in the same order? That order is up to you, I just want it to be consistent. I just ran an analysis on the title field in the trunk example and the first step in the output was in this order: text, start, end, type, position. The other two steps were ordered like this: text, position, start, end, type. At first I thought that the position had disappeared after the first step, then I noticed it was still there, just in a different place.
On the logging page: Many of the settings show null, italicized. This would be fine, except that when you click on one, null is not one of the choices. You have to choose UNSET to keep the setting the same. One of them needs to change to match the other. My thought is that in both places it should be "unset" or "not set" -- lowercase and italicized.
On the Plugins page under the core: You can't open more than one of the dropdown items at once, and you can't close a dropdown once it's open. It's very helpful for me to be able to see more than one set of cache statistics at the same time. If you can open more than one of them, you need to be able to close them as well.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264270#comment-13264270 ]
Stefan Matheis (steffkes) commented on SOLR-3238:
-------------------------------------------------
{quote}I'm not sure what issue to attach this to, so it may make sense to make a new issue. Here is general wishlist of things I think would help...
* From the analysis page, can there be a link to the relevant field/fieldType in schema-browser?
* From the schema-browser, can there be a link to the analysis page (with the right field selected?) Perhaps the text "Index Analyzer" and "Query Analyzer" could be links
* In the schema-browser, when you click on a term, it loads in the query window, it should also execute the query!
* Why does Autoload™ have a tm?
* I assume Autoload is writing a cookie... can it also keep the number of terms? Perhaps also the checked state on analysis verbose output?
* On the schema-browser page, the text "Index Analyzer" shows up on one line, but "Query Analyzer" gets broken into two lines.
* When showing the number of matching Docs for a field, can the number be a link to a query? For example with the field "id", the link can be to: q=id:[* TO *]
* The plural names in schema-browser are inappropriate at times – not a big deal, but if we replaced "Fields/Types" with "Field:/Type:" I think it works OK in both singular and plural cases
* In the plugin page, there are lots of URLs that would be great if they were actually URLS. When we show a link to "http://wiki.apache.org/solr/StandardRequestHandler" that should be a real URL{quote}
All of them changed.
{quote}* I assume Autoload is writing a cookie... can it also keep the number of terms? Perhaps also the checked state on analysis verbose output?
* When showing the number of matching Docs for a field, can the number be a link to a query? For example with the field "id", the link can be to: q=id:[* TO *]{quote}
Schema-Browser/Autoload was already using a cookie, Analysis/Verbose now too. Schema-Browser got a separate "Query"-Link in the TopTerms-Section. In the first row "[NN]/NN Top-Terms" the second Number is already a link to load _all_ Top-Terms, therefore i couldn't change this one into a link to the Query.
If we'd like to have a possibility to load every time all available Top-Terms, we could add another checkbox (right below the "[_] Autoload" one?
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Matheis (steffkes) updated SOLR-3238:
--------------------------------------------
Attachment: SOLR-3238.patch
Updated Patch, will commit soon
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232437#comment-13232437 ]
Ryan McKinley commented on SOLR-3238:
-------------------------------------
+1
Stefan -- go ahead and commit!
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Uwe Schindler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230043#comment-13230043 ]
Uwe Schindler commented on SOLR-3238:
-------------------------------------
I got this error with trunk checkout using "ant run-example", too. But only on the first run, later runs work.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3238) Sequel of Admin UI
Posted by "Vadim Kisselmann (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230056#comment-13230056 ]
Vadim Kisselmann edited comment on SOLR-3238 at 3/15/12 11:02 AM:
------------------------------------------------------------------
It's weird:)
"ant run-example" starts server with jetty, and it works.
As next step i build it one more time with "ant example" and start my tomcat, and it works, too.
When i update to new Solr version from trunk, and build it with "ant example", i get this error again.
EDIT: no errors at this time in my log files.
was (Author: ldb):
It's weird:)
"ant run-example" starts server with jetty, and it works.
As next step i build it one more time with "ant example" and start my tomcat, and it works, too.
When i update to new Solr version from trunk, and build it with "ant example", i get this error again.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Shawn Heisey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264361#comment-13264361 ]
Shawn Heisey commented on SOLR-3238:
------------------------------------
Being used to the 3x gui, I was initially looking for statistics but didn't find it. I was a little bit surprised to find it under Plugins. I would have expected that section to be called Statistics. If having "plugin" in the name is something you find to be important, perhaps it should be called "Plugin Stats" or "Plugins/Statistics" or something else that makes it clear?
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276662#comment-13276662 ]
Stefan Matheis (steffkes) commented on SOLR-3238:
-------------------------------------------------
bq. There's a small issue on the analysis page. After submitting the form with whitespace in the fields they are printed again still being url encoded with + for whitespace.
Thanks Markus, should be fixed in r1339114
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "David Smiley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262140#comment-13262140 ]
David Smiley commented on SOLR-3238:
------------------------------------
Jetty's "DefaultServlet" serves *static content*, such as the CSS, Solr logo, and all the page templates. Any dynamically generated data, such as what comes from Solr itself via its request handlers, don't apply to what I propose.
You should know that the "load term info" information is *not* cached by the browser; it re-requests it every time it is asked for, just like any other request to Solr itself, given Solr's default HTTP cache settings (which is not to cache). There might be caching on the Solr side but I doubt it.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Aliaksandr Zhuhrou (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231527#comment-13231527 ]
Aliaksandr Zhuhrou commented on SOLR-3238:
------------------------------------------
As a suggestion can we allow specify default Query Response Writer. I am using a custom writer which is default response writer and I can't select it using an admin interface. Can we add a option "default" to the WT select on query tab which forces Solr to use the default one. Also I think we can build a select list directly from the current solr configuration.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234226#comment-13234226 ]
Stefan Matheis (steffkes) commented on SOLR-3238:
-------------------------------------------------
Committed in revision 1303326
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "David Smiley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262168#comment-13262168 ]
David Smiley commented on SOLR-3238:
------------------------------------
I didn't know Firebug could do that, although this doesn't completely address the issue. I didn't set out to do Solr development today, I merely wanted to see the latest UI so I could do a screen capture. Looking at Firebug when I was diagnosing this, showed that it decided to cache the stuff for a few days on me -- I forget how long exactly.
Another option to solve this well-known problem (this is hardly specific to Solr) is to attach a nonce query parameter to the static resources. This nonce could be the Solr build release string seen on the front string. Essentially when a template is requested, it would request /solr/tpl/query.html?nonce=4.0.0.2012.04.25.16.10.30
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3238) Sequel of Admin UI
Posted by "Uwe Schindler (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230043#comment-13230043 ]
Uwe Schindler edited comment on SOLR-3238 at 3/15/12 10:43 AM:
---------------------------------------------------------------
I got this error with trunk checkout using "ant run-example", too. But only on the first run, later runs work.
EDIT: I think this has nothing to do with the admin UI. When this happened, I got some Exceptions in the startup of Solr. Can you check for them in the logs? Unfortunately I cannot reproduce at the moment.
was (Author: thetaphi):
I got this error with trunk checkout using "ant run-example", too. But only on the first run, later runs work.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Matheis (steffkes) updated SOLR-3238:
--------------------------------------------
Attachment: SOLR-3238.patch
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Erick Erickson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253299#comment-13253299 ]
Erick Erickson commented on SOLR-3238:
--------------------------------------
dylan:
How are you looking at your log? Because when I try cut/paste of your string in the admin analysis page, the return display in the admin UI has the characters correctly displayed, identified as IDEOGRAPHIC with raw byte sequences like: 'e4 b8 ad' and 'e6 96 87' (which I admit I haven't a clue whether they're correct or not). But the log shows gibberish (Jetty).
So my assumption here would be that the admin UI is fine, but the characters are being munged somewhere else, perhaps logging? Perhaps settings for your display in your editor or terminal session?
Of course I could be all wet here.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246938#comment-13246938 ]
Ryan McKinley commented on SOLR-3238:
-------------------------------------
I'm not sure what issue to attach this to, so it may make sense to make a new issue. Here is general wishlist of things I think would help...
* From the analysis page, can there be a link to the relevant field/fieldType in schema-browser?
* From the schema-browser, can there be a link to the analysis page (with the right field selected?) Perhaps the text "Index Analyzer" and "Query Analyzer" could be links
* In the schema-browser, when you click on a term, it loads in the query window, it should also execute the query!
* Why does Autoload™ have a tm?
* I assume Autoload is writing a cookie... can it also keep the number of terms? Perhaps also the checked state on analysis verbose output?
* On the schema-browser page, the text "Index Analyzer" shows up on one line, but "Query Analyzer" gets broken into two lines.
* When showing the number of matching Docs for a field, can the number be a link to a query? For example with the field "id", the link can be to: q=id:[* TO *]
* The plural names in schema-browser are inappropriate at times -- not a big deal, but if we replaced "Fields/Types" with "Field:/Type:" I think it works OK in both singular and plural cases
* In the plugin page, there are lots of URLs that would be great if they were actually URLS. When we show a link to "http://wiki.apache.org/solr/StandardRequestHandler" that should be a real URL
Things are really looking great!
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Chris Male (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246941#comment-13246941 ]
Chris Male commented on SOLR-3238:
----------------------------------
Perhaps its useful to have a few sub-tasks for each of these? Then we don't have a single issue with lots of disconnected patches and comments.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Chen Chun (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231912#comment-13231912 ]
Chen Chun commented on SOLR-3238:
---------------------------------
Have a look at "solradminbug.png".
I have no idea what's wrong with it. Are the "start" or "rows" parameters essential?
but if i use "curl http://dog:8983/solr/dataimport?command=full-import", that is ok.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3238) Sequel of Admin UI
Posted by "Vadim Kisselmann (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230104#comment-13230104 ]
Vadim Kisselmann edited comment on SOLR-3238 at 3/15/12 12:53 PM:
------------------------------------------------------------------
Now i have error messages:
SCHWERWIEGEND: The web application [/solr2] appears to have started a thread named [main-SendThread(zookeeper:2181)] but has failed to stop it. This is very likely to create a memory leak.
Exception in thread "Thread-2" java.lang.NullPointerException
at org.apache.solr.cloud.Overseer$CloudStateUpdater.amILeader(Overseer.java:179)
at org.apache.solr.cloud.Overseer$CloudStateUpdater.run(Overseer.java:104)
at java.lang.Thread.run(Thread.java:662)
15.03.2012 13:25:17 org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.zookeeper.server.ZooTrace. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1531)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1196)
15.03.2012 13:25:17 org.apache.coyote.http11.Http11Protocol destroy
SLF4J: The requested version 1.5.8 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
log4j:WARN No appenders could be found for logger (org.apache.solr.core.SolrResourceLoader).
log4j:WARN Please initialize the log4j system properly.
Steps:
I deleted the one default core in solr.xml, because i would create new cores with CoreAdminHandler.
I started tomcat.
Now it's completely broken. Rebuild and restart, whether jetty or tomcat, change nothing.
EDIT:
i get the same problem on another server(tomcat, sharded, without ZK). With an old revision from Feb. it works,
with new checkout from trunk not.
was (Author: ldb):
Now i have error messages:
SCHWERWIEGEND: The web application [/solr2] appears to have started a thread named [main-SendThread(zookeeper:2181)] but has failed to stop it. This is very likely to create a memory leak.
Exception in thread "Thread-2" java.lang.NullPointerException
at org.apache.solr.cloud.Overseer$CloudStateUpdater.amILeader(Overseer.java:179)
at org.apache.solr.cloud.Overseer$CloudStateUpdater.run(Overseer.java:104)
at java.lang.Thread.run(Thread.java:662)
15.03.2012 13:25:17 org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.zookeeper.server.ZooTrace. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1531)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1196)
15.03.2012 13:25:17 org.apache.coyote.http11.Http11Protocol destroy
SLF4J: The requested version 1.5.8 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
log4j:WARN No appenders could be found for logger (org.apache.solr.core.SolrResourceLoader).
log4j:WARN Please initialize the log4j system properly.
Steps:
I deleted the one default core in solr.xml, because i would create new cores with CoreAdminHandler.
I started tomcat.
Now it's completely broken. Rebuild and restart, whether jetty or tomcat, change nothing.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3238) Sequel of Admin UI
Posted by "Chen Chun (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chen Chun updated SOLR-3238:
----------------------------
Attachment: solradminbug.png
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Emma Bo Liu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246536#comment-13246536 ]
Emma Bo Liu commented on SOLR-3238:
-----------------------------------
when accessing the solr new admin UI http://localhost:8983/solr/#/cloud, the error message window pop up saying ' 500 error get#/cloud cannot call method 'attr' of undefined
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Emma Bo Liu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246521#comment-13246521 ]
Emma Bo Liu commented on SOLR-3238:
-----------------------------------
cloud/zookeeper-data cannot show the node tree as the previous version.It says 'Fetch zookeeper data'without showing anything of the solr node.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291429#comment-13291429 ]
Ryan McKinley commented on SOLR-3238:
-------------------------------------
bq. My scripts currently use the stats.jsp
A big goal was to drop the totally untested jsp files and make sure all the logic is in standard request handlers.
bq. do you know of any documentation that covers everything that's available?
not really -- i suggest looking at the requests with firebug. There are docs on the wiki, but it far from *everything*
bq. SolrJ might need a new way to specify the base URL path.
you should be able to get to anything with existing solrj API, just use solr.setQueryType( "/admin/mbeans" )
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281607#comment-13281607 ]
Markus Jelsma commented on SOLR-3238:
-------------------------------------
I think it would also be useful to display the shard information in the core overview page such as its ID and whether it is a leader.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3238) Sequel of Admin UI
Posted by "Aliaksandr Zhuhrou (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231527#comment-13231527 ]
Aliaksandr Zhuhrou edited comment on SOLR-3238 at 3/16/12 7:04 PM:
-------------------------------------------------------------------
As a suggestion can we allow specify default Query Response Writer. I am using a custom writer which is default response writer and I can't select it using an admin interface. Can we add a option "default" to the WT select on query tab which forces Solr to use the default one? Also I think we can build a select list directly from the current solr configuration.
was (Author: zhygr):
As a suggestion can we allow specify default Query Response Writer. I am using a custom writer which is default response writer and I can't select it using an admin interface. Can we add a option "default" to the WT select on query tab which forces Solr to use the default one. Also I think we can build a select list directly from the current solr configuration.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3238) Sequel of Admin UI
Posted by "Vadim Kisselmann (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230104#comment-13230104 ]
Vadim Kisselmann edited comment on SOLR-3238 at 3/15/12 12:44 PM:
------------------------------------------------------------------
Now i have error messages:
SCHWERWIEGEND: The web application [/solr2] appears to have started a thread named [main-SendThread(zookeeper:2181)] but has failed to stop it. This is very likely to create a memory leak.
Exception in thread "Thread-2" java.lang.NullPointerException
at org.apache.solr.cloud.Overseer$CloudStateUpdater.amILeader(Overseer.java:179)
at org.apache.solr.cloud.Overseer$CloudStateUpdater.run(Overseer.java:104)
at java.lang.Thread.run(Thread.java:662)
15.03.2012 13:25:17 org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.zookeeper.server.ZooTrace. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1531)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1196)
15.03.2012 13:25:17 org.apache.coyote.http11.Http11Protocol destroy
SLF4J: The requested version 1.5.8 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
log4j:WARN No appenders could be found for logger (org.apache.solr.core.SolrResourceLoader).
log4j:WARN Please initialize the log4j system properly.
Steps:
I deleted the one default core in solr.xml, because i would create new cores with CoreAdminHandler.
I started tomcat.
Now it's completely broken. Rebuild and restart, whether jetty or tomcat, change nothing.
was (Author: ldb):
Now i have error messages:
SCHWERWIEGEND: The web application [/solr2] appears to have started a thread named [main-SendThread(zookeeper:2181)] but has failed to stop it. This is very likely to create a memory leak.
Exception in thread "Thread-2" java.lang.NullPointerException
at org.apache.solr.cloud.Overseer$CloudStateUpdater.amILeader(Overseer.java:179)
at org.apache.solr.cloud.Overseer$CloudStateUpdater.run(Overseer.java:104)
at java.lang.Thread.run(Thread.java:662)
15.03.2012 13:25:17 org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.zookeeper.server.ZooTrace. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1531)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1196)
15.03.2012 13:25:17 org.apache.coyote.http11.Http11Protocol destroy
SLF4J: The requested version 1.5.8 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
log4j:WARN No appenders could be found for logger (org.apache.solr.core.SolrResourceLoader).
log4j:WARN Please initialize the log4j system properly.
Steps:
I deleted the one default core in solr.xml, because i would create new cores with CoreAdminHandler.
I started tomcat.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Shawn Heisey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291374#comment-13291374 ]
Shawn Heisey commented on SOLR-3238:
------------------------------------
I fired up the example from branch_4x today so I could check something in the new admin GUI, and found a couple of things I thought were worth mentioning.
What I needed to check was whether the pages were machine-readable. I've currently got an index status page written in Perl that parses the XML output from the current admin GUI on four Solr servers. The new GUI is absolutely beautiful from a human perspective, but I need to be able to pull the displayed information out in a machine-readable form as well. Is there any way to do that?
The next version of my status page will be written in Java. What kind of options will I have available for retrieving statistical information from a remote Solr instance?
When I fired up the multicore example, I found that the cache statistics pages for both cores only had fieldCache and fieldValueCache. The documentCache, filterCache, and queryResultCache were not present. If there were other things missing, I didn't notice.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "David Smiley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262084#comment-13262084 ]
David Smiley commented on SOLR-3238:
------------------------------------
Given how easy it is to stop Solr and potentially bring up a different Solr version at the same URL in very little time, perhaps max-age should be 10 seconds.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276647#comment-13276647 ]
Markus Jelsma commented on SOLR-3238:
-------------------------------------
There's a small issue on the analysis page. After submitting the form with whitespace in the fields they are printed again still being url encoded with + for whitespace.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276669#comment-13276669 ]
Stefan Matheis (steffkes) commented on SOLR-3238:
-------------------------------------------------
bq. Being used to the 3x gui, I was initially looking for statistics but didn't find it. I was a little bit surprised to find it under Plugins. I would have expected that section to be called Statistics. If having "plugin" in the name is something you find to be important, perhaps it should be called "Plugin Stats" or "Plugins/Statistics" or something else that makes it clear?
I don't remember why i started with naming it "Plugins" ;o But i don't mind if we change names, so committed in r1339120 new Name "Plugins / Stats", Statistics is a bit too long and would result in a Two-Liner
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291407#comment-13291407 ]
Ryan McKinley commented on SOLR-3238:
-------------------------------------
bq. What I needed to check was whether the pages were machine-readable
The new javascript gets all its data from normal request handlers
bq. but I need to be able to pull the displayed information out in a machine-readable form as well. Is there any way to do that?
Yes, use normal solr requests. If you turn on firebug (or equivalent) you can see what the UI is actually calling to get out the machine readable values. For cache stats, that will be something like:
http://localhost:8983/solr/admin/mbeans?stats=true&wt=json
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Vadim Kisselmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230104#comment-13230104 ]
Vadim Kisselmann commented on SOLR-3238:
----------------------------------------
Now i have error messages:
SCHWERWIEGEND: The web application [/solr2] appears to have started a thread named [main-SendThread(zookeeper:2181)] but has failed to stop it. This is very likely to create a memory leak.
Exception in thread "Thread-2" java.lang.NullPointerException
at org.apache.solr.cloud.Overseer$CloudStateUpdater.amILeader(Overseer.java:179)
at org.apache.solr.cloud.Overseer$CloudStateUpdater.run(Overseer.java:104)
at java.lang.Thread.run(Thread.java:662)
15.03.2012 13:25:17 org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.zookeeper.server.ZooTrace. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1531)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1196)
15.03.2012 13:25:17 org.apache.coyote.http11.Http11Protocol destroy
SLF4J: The requested version 1.5.8 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
log4j:WARN No appenders could be found for logger (org.apache.solr.core.SolrResourceLoader).
log4j:WARN Please initialize the log4j system properly.
Steps:
I deleted the one default core in solr.xml, because i would create new cores with CoreAdminHandler.
I started tomcat.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "David Smiley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262074#comment-13262074 ]
David Smiley commented on SOLR-3238:
------------------------------------
Since more of the UI is now actually loaded asynchronously, it is subject to the jetty's DefaultServlet cacheing headers, which are non-existent by default. I found it highly annoying today when I updated Solr to find that the UI wasn't updated, even when I told my browser to force-reload. I had to clear my browser cache. I looked into this a bit and I propose that example/etc/webdefault.xml has the "cacheControl" piece of it be un-commented, and set the max-age to 60 (in seconds). It is unlikely the timespan between a browser requesting it and Solr being shut down, updated, redeployed, and the browser fetches it again. Possible but unlikely. When this time span is exceeded, a browser would re-request the resources but it would get back a small 304 status to indicate the file hasn't changed, assuming it hasn't. To be clear, this applies to the admin UI in the out-of-the-box jetty configuration, and doesn't apply to searches. Sound good? I can commit it trivially.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3238) Sequel of Admin UI
Posted by "Erick Erickson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262106#comment-13262106 ]
Erick Erickson commented on SOLR-3238:
--------------------------------------
My only concern is that the schema browser page. The calls to calculate some of the stats, particularly the "load term info" button can be quite expensive on large systems; to get the top terms you have to spin through all the terms in the field. But otherwise, I'd call a fast age-out a feature,
Now, I know very little about jetty configuration so this may be all wet, but aging out that information quickly would make the schema-browser part of the UI quite hard to use.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org