[jira] Issue Comment Edited: (SOLR-1163) Solr Explorer - A generic GWT client for Solr

["Lance Norskog (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864006#action_12864006 ] 

Lance Norskog edited comment on SOLR-1163 at 5/4/10 5:23 PM:
-------------------------------------------------------------

bq. 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).
Ok, I see the problem. If there is any way to make this more flexible? For example, a list of places to look?

bq. 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?
Yes. Most multicore sites use the same schema etc. for all of their cores, so a default template would be very useful.

bq. 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?
Creating facets works. I edited an existing facet with the left-button pulldown. I changed the query. When I saved it, I got this popup error:
{noformat}
Error occured: (TypeError): h is undefined
 stack: hLb([object Object],[object Object],[object Object])@http://localhost:9963/solr-explorer/explorer/558095973C1D0840259C75524EE8A354.cache.html:4251
$Kb([object Object],[object Object])@http://localhost:9963/solr-explorer/explorer/558095973C1D0840259C75524EE8A354.cache.html:2487
([object Object])@http://localhost:9963/solr-explorer/explorer/558095973C1D0840259C75524EE8A354.cache.html:4293
@http://localhost:9963/solr/errors/select?version=2.2&q=*:*&start=0&facet=on&facet.query=stamp_dt:%5B*%20TO%20*%5D&wt=json&indent=true&json.wrf=callback7:104
 fileName: http://localhost:9963/solr-explorer/explorer/558095973C1D0840259C75524EE8A354.cache.html
 lineNumber: 4251
{noformat}

      was (Author: lancenorskog):
    bq. 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).
Ok, I see the problem. If there is any way to make this more flexible? For example, a list of places to look?

bq. 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?
Yes. Most multicore sites use the same schema etc. for all of their cores, so a default template would be very useful.

bq. 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?
Creating facets works. I edited an existing facet with the left-button pulldown. I changed the query. When I saved it, I got this popup error:
{norformat}
Error occured: (TypeError): h is undefined
 stack: hLb([object Object],[object Object],[object Object])@http://localhost:9963/solr-explorer/explorer/558095973C1D0840259C75524EE8A354.cache.html:4251
$Kb([object Object],[object Object])@http://localhost:9963/solr-explorer/explorer/558095973C1D0840259C75524EE8A354.cache.html:2487
([object Object])@http://localhost:9963/solr-explorer/explorer/558095973C1D0840259C75524EE8A354.cache.html:4293
@http://localhost:9963/solr/errors/select?version=2.2&q=*:*&start=0&facet=on&facet.query=stamp_dt:%5B*%20TO%20*%5D&wt=json&indent=true&json.wrf=callback7:104
 fileName: http://localhost:9963/solr-explorer/explorer/558095973C1D0840259C75524EE8A354.cache.html
 lineNumber: 4251
{noformat}
  
> Solr Explorer - A generic GWT client for Solr
> ---------------------------------------------
>
>                 Key: SOLR-1163
>                 URL: https://issues.apache.org/jira/browse/SOLR-1163
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>    Affects Versions: 1.3
>            Reporter: Uri Boness
>         Attachments: graphics.zip, SOLR-1163.zip, 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: http://search.jteam.nl/explorer. 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: http://search.jteam.nl/help
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org