lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uri Boness (JIRA)" <>
Subject [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr
Date Tue, 04 May 2010 17:08:59 GMT


Uri Boness commented on SOLR-1163:

Hi Lance,

bq. How do you set the directory for solr-explorer.xml file?
The solr-explorer.xml is configured in the host html file SolrExplorer.html as a gwtoolbox:property
<meta> tag. Currently the value needs to be relative to SolrExplorer.html, though I'm
planning to make it more flexible so when deploying on a web server it'd be possible to put
it anywhere on that server (it will not be possible to load it from external server due to
XSS limitations).

bq. Also, an improvement: for multicore, one common configuration for many cores would help
 And some default core, or name wildcarding.
As I understand, you basically want to be able to define default config template which you
can base your specific configurations on. Did I get it right?

bq. Also, it still has the bug in editing query facets 
Can you elaborate on this one... I didn't experience problems when defining query facets.
How do you define them? Can you give an example of a facet that failed?

> Solr Explorer - A generic GWT client for Solr
> ---------------------------------------------
>                 Key: SOLR-1163
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>    Affects Versions: 1.3
>            Reporter: Uri Boness
>         Attachments:,, solr-explorer.patch, solr-explorer.patch
> The attached patch is a GWT generic client for solr. It is currently standalone, meaning
that once built, one can open the generated HTML file in a browser and communicate with any
deployed solr. It is configured with it's own configuration file, where one can configure
the solr instance/core to connect to. Since it's currently standalone and completely client
side based, it uses JSON with padding (cross-side scripting) to connect to remote solr servers.
Some of the supported features:
> - Simple query search
> - Sorting - one can dynamically define new sort criterias
> - Search results are rendered very much like Google search results are rendered. It is
also possible to view all stored field values for every hit. 
> - Custom hit rendering - It is possible to show thumbnails (images) per hit and also
customize a view for a hit based on html templates
> - Faceting - one can dynamically define field and query facets via the UI. it is also
possible to pre-configure these facets in the configuration file.
> - Highlighting - you can dynamically configure highlighting. it can also be pre-configured
in the configuration file
> - Spellchecking - you can dynamically configure spell checking. Can also be done in the
configuration file. Supports collation. It is also possible to send "build" and "reload" commands.
> - Data import handler - if used, it is possible to send a "full-import" and "status"
command ("delta-import" is not implemented yet, but it's easy to add)
> - Console - For development time, there's a small console which can help to better understand
what's going on behind the scenes. One can use it to:
> ** view the client logs
> ** browse the solr scheme
> ** View a break down of the current search context
> ** View a break down of the query URL that is sent to solr
> ** View the raw JSON response returning from Solr
> This client is actually a platform that can be greatly extended for more things. The
goal is to have a client where the explorer part is just one view of it. Other future views
include: Monitoring, Administration, Query Builder, DataImportHandler configuration, and more...
> To get a better view of what's currently possible. We've set up a public version of this
client at: This client is configured with one solr instance
where crawled YouTube movies where indexed. You can also check out a screencast for this deployed
> The patch created a new folder in the contrib. directory. Since the patch doesn't contain
binaries, an additional zip file is provides that needs to be extract to add all the required
graphics. This module is maven2 based and is configured in such a way that all GWT related
tools/libraries are automatically downloaded when the modules is compiled. One of the artifacts
of the build is a war file which can be deployed in any servlet container.
> NOTE: this client works best on WebKit based browsers (for performance reason) but also
works on firefox and ie 7+. That said, it should be taken into account that it is still under

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message