Re: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr

Pradeep Pujari-4
Is this now a part of Solr/examples or Solr/client? I played with the first version which was contrib/SolrExplorer. I do not see the directory anymore?


--- On Wed, 4/7/10, Uri Boness (JIRA) <[hidden email]> wrote:

> From: Uri Boness (JIRA) <[hidden email]>
> Subject: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr
> To: [hidden email]
> Date: Wednesday, April 7, 2010, 12:44 PM
>     [
> ]
> Uri Boness commented on SOLR-1163:
> ----------------------------------
> The only downside to this is that it requires extra setup.
> A lot of people (incl. myself) like to use the bundled jetty
> instance for development and only deploy solr in a different
> servlet container in production. In that sense, it would be
> nice to get something ready out of the box with solr
> distribution (or at least that it would be easy to set it up
> with the examples directory).
> > 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 client:
> > 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 development.
> --
> 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: [hidden email]
For additional commands, e-mail: [hidden email]