Created: (SOLR-162) lucene index browser / admin helpers (Luke)

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

Created: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
lucene index browser / admin helpers (Luke)
-------------------------------------------

                 Key: SOLR-162
                 URL: https://issues.apache.org/jira/browse/SOLR-162
             Project: Solr
          Issue Type: New Feature
          Components: web gui
            Reporter: Ryan McKinley
            Priority: Minor


Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.

Solr already does a lot of what luke does... but it could do a bit more.  Specifically:

* browse top terms across all fields (similar to faceting)
* browse lucene documents / properties directly


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Updated: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley updated SOLR-162:
-------------------------------

    Attachment: SOLR-162-Admin-XML-luke.patch


This patch moves a lot of the /admin jsp pages to SolrRequestHandlers and adds a LukeRequestHandler to let you browse a lucene index (even if it does not match the solr schema).  I don't know XSLT well enough to make anything look good yet, but with an ok XSLT file, we could replace many of the .jsp files.

pages of interest:

http://localhost:8983/solr/admin/

http://localhost:8983/solr/admin/file
http://localhost:8983/solr/admin/file?file=solrconfig.xml
http://localhost:8983/solr/admin/threads
http://localhost:8983/solr/admin/registry
http://localhost:8983/solr/admin/registry?wt=json&indent=true
http://localhost:8983/solr/admin/stats
http://localhost:8983/solr/admin/ping
http://localhost:8983/solr/admin/properties
http://localhost:8983/solr/admin/properties?name=java.home
http://localhost:8983/solr/admin/logging
http://localhost:8983/solr/admin/logging?set=FINE 

http://localhost:8983/solr/admin/luke (field info + top fields)
http://localhost:8983/solr/admin/luke?field=cat (like faceting)
http://localhost:8983/solr/admin/luke?docID=10 (lucene doc + solr doc)
http://localhost:8983/solr/admin/luke?id=10 (lucene doc + solr doc)
http://localhost:8983/solr/admin/luke?id=MA147LL/A


> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473849 ]

Yonik Seeley commented on SOLR-162:
-----------------------------------

Wow, what can I say... you continue to out pace us committers, Ryan.
I'll try and look at at least *one* of the open issues this weekend.

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Re: Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

Erik Hatcher
Wow indeed!   Go Ryan.

On Feb 16, 2007, at 6:07 PM, Yonik Seeley (JIRA) wrote:

>
>     [ https://issues.apache.org/jira/browse/SOLR-162?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel#action_12473849 ]
>
> Yonik Seeley commented on SOLR-162:
> -----------------------------------
>
> Wow, what can I say... you continue to out pace us committers, Ryan.
> I'll try and look at at least *one* of the open issues this weekend.
>
>> lucene index browser / admin helpers (Luke)
>> -------------------------------------------
>>
>>                 Key: SOLR-162
>>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>>             Project: Solr
>>          Issue Type: New Feature
>>          Components: web gui
>>            Reporter: Ryan McKinley
>>            Priority: Minor
>>         Attachments: SOLR-162-Admin-XML-luke.patch
>>
>>
>> Luke (http://www.getopt.org/luke/) is a great tool to help learn /  
>> understand / debug lucene indexes.
>> Solr already does a lot of what luke does... but it could do a bit  
>> more.  Specifically:
>> * browse top terms across all fields (similar to faceting)
>> * browse lucene documents / properties directly
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473865 ]

Erik Hatcher commented on SOLR-162:
-----------------------------------

This is truly great stuff, Ryan!  *whew* I can't keep up.

I did however become really intrigued by this particular patch and tried it out.  I like all these details and Flare will certainly leverage this stuff deeply.  

One comment.  for this request http://localhost:8888/solr/admin/ping?wt=ruby&indent=on all that was logged was this:

Feb 16, 2007 8:59:22 PM org.apache.solr.core.SolrCore execute
INFO: wt=ruby&indent=on 0 8

I realize this is tangentially related to this issue, and nothing introduced with this patch, but I'd like to see the path (admin/ping, in this case) in the log as well so that requests could be recreated easily.  I'm used to the solr/select? stuff and tacking on what I get in the log file, but with the newly revamped mega flexible paths, it'd be handy to see the path here.

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473874 ]

Ryan McKinley commented on SOLR-162:
------------------------------------

check SOLR-149.  it adds the path to a request and prints it out with the log.  

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473920 ]

Erik Hatcher commented on SOLR-162:
-----------------------------------

Ryan - I would like to see the Maps used instead of NamedLists for things that truly don't need to be lists.  For example, /admin/file?wt=ruby returns this:

'files'=>[
  'admin-extra.html',[
        'size',1094,
        'modified','2006-12-05T02:30:56Z'],...

'size' and 'modified' should be keys in a hash instead of in a list.  Should be no big deal to switch over things where order doesn't matter to maps though.  Likewise for /admin/threads and /admin/registry, and maybe others.


> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473932 ]

Bertrand Delacretaz commented on SOLR-162:
------------------------------------------

I briefly tested this, it looks very useful, and the different RequestHandlers make the code very modular, way to go!

One nitpick: I'd use "system.properties" instead of "properties", it's more precise.

And two suggestions related to XSLT transformations for presentation:

1) It'd be good to systematically include in the output XML the class name of the SolrRequestHandler used. XSLT transforms can then use this info to adapt themselves to the information being output.

2) It'd be good to name <lst> elements, as much as possible, also to allow XSLT transforms to adapt themselves to the content.

For example, using a NamedList instead of an ArralyList in the "Now show all the threads" loop in ThreadDumpRequestHandler:

    NamedList<NamedList<Object>> lst = new NamedList<NamedList<Object>>();
    for (ThreadInfo ti : tinfos) {
      lst.add( "thread", getThreadInfo( ti ) );
    }

Outputs this:

<lst name="thread">
  <long name="id">35</long>
  <str name="name">P1-19</str>
  <str name="state">RUNNABLE</str>...

where the name="thread" attribute can be used to decide how to present the contents of the <lst> element.

Thinking about it, we might want to add a "datatype" attribute to these lists, to use when presenting them?

<lst datatype="java.lang.Thread">

would help present all Thread info in a consistent way, no matter where it comes from.



> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Updated: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley updated SOLR-162:
-------------------------------

    Attachment: SOLR-162-Admin-XML-luke.patch

Thanks for your feedback, here is an updated version that:

1. replaces NamedList<> with Map<String,> wherever possible.  This makes the direct XML output look funny (the stack trace is displayed before the thread name), but it is probably a good idea so clients can easily access stuff by name.

2. I added a parameter "echoHandler" that behaves just like "echoParams" - it writes the handler name to the responseHeader.  

3. I added the default params echoHandler=true and echoParams=explicit to all the /admin/* handlers.  This gets a bit verbose and will be helped by

4. I moved the responseHeader writing from SolrCore to RequestBaseHandler.  This is good because RequestHandler authors control the header more explicitly if necessary.

5. added a name to each thread in the thread list.  I don't see any other lists without names, but i could be missing something.

6. changed the output in PropertiesRequestHandler from "properties" to "system.properties"




> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473950 ]

Ryan McKinley commented on SOLR-162:
------------------------------------

3. ... will be helped by SOLR-112


> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473975 ]

Yonik Seeley commented on SOLR-162:
-----------------------------------

> 1. replaces NamedList<> with Map<String,> wherever possible. This makes the direct XML output look funny (the stack > trace is displayed before the thread name), but it is probably a good idea so clients can easily access stuff by name.

If you want map output semantics (important distinction for other formats like JSON), but the ability to control order w/o the overhead of LinkedHashMap, see SimpleOrderedMap.
It subclasses NamedList, so it's easy to convert code that previously used NamedList.


> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Updated: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley updated SOLR-162:
-------------------------------

    Attachment: SOLR-162-Admin-XML-luke.patch

using SimpleOrderedMap - this keeps nice ordering for XML and uses map syntax for JSON/ruby.

thanks Yonik!

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474333 ]

Hoss Man commented on SOLR-162:
-------------------------------

i barely started to scratch the surface looking at this patch while checking something for SOLR-142, but before i forget i wanted to raise one red flag...

this patch removes the call to setResponseHeaderValues from SolrCore and moves it to RequestHandlerBase with the assumption that RequestHandlers can take care of it ... this is a bad idea since there is no requirement that RequestHandler extend that class -- any solr1.1 users who have written their own request handlers will be screwed.

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Commented: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474335 ]

Ryan McKinley commented on SOLR-162:
------------------------------------

yes, that is a problem!

I'll wait till SOLR-142 gets checked in, then post an update that puts the header stuff back in SolrCore

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Updated: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley updated SOLR-162:
-------------------------------

    Attachment: SOLR-162-Admin-XML-luke.patch

I put setResponseHeaderValues from SolrCore.

Uses the automatic configuration and utility classes from SOLR-85

<admin>
  <registerStandardHandlers>/admin</registerStandardHandlers>
  ...
</admin>

(perhaps this and SOLR-85 should be combined?)

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

Updated: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley updated SOLR-162:
-------------------------------

    Attachment: SOLR-162-Admin-XML-luke.patch

Updated to:
 * use SOLR-182 rather then implement its own dynamic loading at startup
 * apply without conflicts
 * use Luke 0.7 style to represent more field properties:

"key":{
  "I":"Indexed",
  "T":"Tokenized",
  "S":"Stored",
  "M":"Multivalued",
  "V":"TermVector Stored",
  "o":"Store Offset With TermVector",
  "p":"Store Position With TermVector",
  "O":"Omit Norms",
  "L":"Lazy",
  "B":"Binary",
  "C":"Compressed",
  "f":"Sort Missing First",
  "l":"Sort Missing Last"},
"fields":{
 "id":{
        "type":"string",
        "schema":"I-S----O----l",
        "flags":"I-S----O-----",
        ...
       

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley updated SOLR-162:
-------------------------------

    Attachment: SOLR-162-Admin-XML-luke.patch

Major updates to the 'luke' part.  It is getting really good!

I removed everything that complicated integration - rather then try to replace exiting /admin/xxx.jsp, this will sit next to it until someone wants to make a nice XSLT thing so we can remove the jsp/jdk requirement.

This includes request handlers for:

  <requestHandler name="/admin/luke"       class="org.apache.solr.handler.admin.LukeRequestHandler" />
  <requestHandler name="/admin/system"     class="org.apache.solr.handler.admin.SystemInfoHandler" />
  <requestHandler name="/admin/plugins"    class="org.apache.solr.handler.admin.PluginInfoHandler" />
  <requestHandler name="/admin/threads"    class="org.apache.solr.handler.admin.ThreadDumpHandler" />
  <requestHandler name="/admin/properties" class="org.apache.solr.handler.admin.PropertiesRequestHandler" />

The only two i really care about are:
 LukeRequestHandler and SystemInfoHandler
If removing the others makes anyone happier, its fine with me.

I also started a wiki page for documentation:
http://wiki.apache.org/solr/LukeRequestHandler

I *think* this is almost ready to commit.



> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley reassigned SOLR-162:
----------------------------------

    Assignee: Ryan McKinley

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>         Assigned To: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (SOLR-162) lucene index browser / admin helpers (Luke)

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley resolved SOLR-162.
--------------------------------

    Resolution: Fixed

commited

> lucene index browser / admin helpers (Luke)
> -------------------------------------------
>
>                 Key: SOLR-162
>                 URL: https://issues.apache.org/jira/browse/SOLR-162
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>            Reporter: Ryan McKinley
>         Assigned To: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.  Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.