Hi all,

After having managed to create a query parser plugin for Solr I'd like to know whether it has been loaded. Actually I do know that it has been loaded and is working. I need to be able to get this information from a remote client though to warn users about missing plugins.

http://host/solr/admin/registry.jsp and http://host/solr/admin/plugins provide quite a lot of useful information already, however, information on loaded (query parser) plugins is missing.

Is there any other URL I could query or am I missing something in my plugin to make it show up there?
best
Ingo

--
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2, Admin Google Summer of Code

TYPO3 - Open Source Enterprise Content Management System
http://typo3.org

Apache Solr for TYPO3 - Enterprise Search meets Enterprise Content Management
http://www.typo3-solr.com

Am 21.09.2010 um 21:58 schrieb Ingo Renner:

Hi there,

for the sake of documenting how to do this for those interested in the same stuff...

> Is there any other URL I could query or am I missing something in my plugin to make it show up there?

in your QParserPlugin class simply implement interface SolrInfoMBean. My getCategory() method is like this:

  public Category getCategory() {
    return SolrInfoMBean.Category.OTHER;
  }

then in method createParser() add the following:

req.getCore().getInfoRegistry().put(getName(), this);

this will make your plugin show up at http://host/solr/admin/plugins under the "OTHER" category.
I wonder though whether it'd be useful if Solr QParserPlugin did implement SolrInfoMBean by default already...
best
Ingo

--
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2, Admin Google Summer of Code

TYPO3 Enterprise Content Management System
http://typo3.org

: then in method createParser() add the following:
:
: req.getCore().getInfoRegistry().put(getName(), this);

that doesn't seem like a good idea -- createParser will be called every
time a string needs to be parsed, you're overwriting the same entry in the
infoRegistry over and over and over again.

I would just put that logic in your init() method (make sure to put the
QParserPlugin in the registry, not the individual QParser instances)

: I wonder though whether it'd be useful if Solr QParserPlugin did
: implement SolrInfoMBean by default already...

I agree ... i think that was an oversight when QParser was added.

There's an open issue for it, but no one has had a chance to get arround
to it yet...

https://issues.apache.org/jira/browse/SOLR-1428

-Hoss

--
http://lucenerevolution.org/  ...  October 7-8, Boston
http://bit.ly/stump-hoss      ...  Stump The Chump!