[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010318#comment-13010318
]
Stefan Matheis (steffkes) edited comment on SOLR-2399 at 3/23/11 8:15 PM:
--------------------------------------------------------------------------
Ryan: ty, will take your points on my list - pretty sure, that it should be
possible to integrate them
Mark: ty! :)
For today, it's about *Logging*. Talked about that with Hoss on #solr the last
days, so already changed a few things .. on the way, but not finished:
http://files.mathe.is/solr-admin/07_logging.png
Actually thinking about the following points:
* Tree Structure good way to solve it?
* Do we need the possibitly to collapse/expand the three/the childrens? The
List could be longer (the screenshot is cropped, just for layout reasons)
especially while using SolrCloud which adds about 30 Loggers
* In the current er .. "Interface" you are able to see that the row you're
looking at has a level set and in the end (at the right) which is the effective
level - for me, that does not matter. if a row/logger, has level-x - that's
enough to know. don't need to see if this level is set or inherited.
* just a quick idea: if you change f.e. {{org.apache.solr}} then the interface
will automatically update all childrens in realtime, affects all nested/sub
loggers w/o a assigned level.
Thoughts on these points? anyone? :>
Short Note: i moved Logging to a global level, because it's not configurable on
a per-core basis.
# Edit
What i forgot to mention .. actually it's based on a [static
logging.json-file|https://github.com/steffkes/solr-admin/blob/master/logging.json]
but will try to change the {{LogLevelSection}} Servlet so that it outputs the
needed json-structure
was (Author: steffkes):
Ryan: ty, will take your points on my list - pretty sure, that it should be
possible to integrate them
Mark: ty! :)
For today, it's about *Logging*. Talked about that with Hoss on #solr the last
days, so already changed a few things .. on the way, but not finished:
http://files.mathe.is/solr-admin/07_logging.png
Actually thinking about the following points:
* Tree Structure good way to solve it?
* Do we need the possibitly to collapse/expand the three/the childrens? The
List could be longer (the screenshot is cropped, just for layout reasons)
especially while using SolrCloud which adds about 30 Loggers
* In the current er .. "Interface" you are able to see that the row you're
looking at has a level set and in the end (at the right) which is the effective
level - for me, that does not matter. if a row/logger, has level-x - that's
enough to know. don't need to see if this level is set or inherited.
* just a quick idea: if you change f.e. {{org.apache.solr}} then the interface
will automatically update all childrens in realtime, affects all nested/sub
loggers w/o a assigned level.
Thoughts on these points? anyone? :>
Short Note: i moved Logging to a global level, because it's not configurable on
a per-core basis.
> Solr Admin Interface, reworked
> ------------------------------
>
> Key: SOLR-2399
> URL: https://issues.apache.org/jira/browse/SOLR-2399
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Reporter: Stefan Matheis (steffkes)
> Priority: Minor
> Fix For: 4.0
>
>
> *The idea was to create a new, fresh (and hopefully clean) Solr Admin
> Interface.* [Based on this
> [ML-Thread|http://www.lucidimagination.com/search/document/ae35e236d29d225e/solr_admin_interface_reworked_go_on_go_away]]
> I've quickly created a Github-Repository (Just for me, to keep track of the
> changes)
> ยป https://github.com/steffkes/solr-admin
> [This commit shows the
> differences|https://github.com/steffkes/solr-admin/commit/5f80bb0ea9deb4b94162632912fe63386f869e0d]
> between old/existing index.jsp and my new one (which is could
> copy-cut/paste'd from the existing one).
> Main Action takes place in
> [js/script.js|https://github.com/steffkes/solr-admin/blob/master/js/script.js]
> which is actually neither clean nor pretty .. just work-in-progress.
> Actually it's Work in Progress, so ... give it a try. It's developed with
> Firefox as Browser, so, for a first impression .. please don't use _things_
> like Internet Explorer or so ;o
> Jan already suggested a bunch of good things, i'm sure there are more ideas
> over there :)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
