You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Uri Boness (JIRA)" <ji...@apache.org> on 2009/05/13 17:43:45 UTC
[jira] Created: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
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
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.
Re: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr
Posted by Pradeep Pujari <Pr...@rocketmail.com>.
Hi Uri,
This is very good App. I applied the patch into my contrib directory in my machine. I am using Eclipse, I do not know how to compile. Is there any libs to be in the classpath. Please explain in detail about how to set up using eclipse IDE.
Thanks in advance,
Pradeep.
--- On Wed, 2/3/10, Uri Boness <ub...@gmail.com> wrote:
> From: Uri Boness <ub...@gmail.com>
> Subject: Re: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr
> To: solr-dev@lucene.apache.org
> Date: Wednesday, February 3, 2010, 4:36 PM
> If you're looking for the new
> version, then no, I haven't created a patch for it yet. The
> old one you can find in JIRA and applying it will create the
> contrib folder for it.
>
> Uri
>
> Pradeep Pujari wrote:
> > I checked contrib directory. I did not find this
> patch. Do you have commited this code?
> >
> > Pradeep.
> >
> > --- On Wed, 1/27/10, Uri Boness (JIRA) <ji...@apache.org>
> wrote:
> >
> >
> >> From: Uri Boness (JIRA) <ji...@apache.org>
> >> Subject: [jira] Commented: (SOLR-1163) Solr
> Explorer - A generic GWT client for Solr
> >> To: solr-dev@lucene.apache.org
> >> Date: Wednesday, January 27, 2010, 10:22 AM
> >>
> >> [ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805601#action_12805601
> >> ]
> >> Uri Boness commented on SOLR-1163:
> >> ----------------------------------
> >>
> >> Actually I've been working on a new version for
> the
> >> explorer which I plan to put soon as a patch
> here.
> >>
> >>
> >>> 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-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.
> >>
> >>
> >>
> >
> >
> >
Re: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by Uri Boness <ub...@gmail.com>.
If you're looking for the new version, then no, I haven't created a
patch for it yet. The old one you can find in JIRA and applying it will
create the contrib folder for it.
Uri
Pradeep Pujari wrote:
> I checked contrib directory. I did not find this patch. Do you have commited this code?
>
> Pradeep.
>
> --- On Wed, 1/27/10, Uri Boness (JIRA) <ji...@apache.org> wrote:
>
>
>> From: Uri Boness (JIRA) <ji...@apache.org>
>> Subject: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr
>> To: solr-dev@lucene.apache.org
>> Date: Wednesday, January 27, 2010, 10:22 AM
>>
>> [ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805601#action_12805601
>> ]
>>
>> Uri Boness commented on SOLR-1163:
>> ----------------------------------
>>
>> Actually I've been working on a new version for the
>> explorer which I plan to put soon as a patch here.
>>
>>
>>> 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-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.
>>
>>
>>
>
>
>
Re: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr
Posted by Pradeep Pujari <Pr...@rocketmail.com>.
I checked contrib directory. I did not find this patch. Do you have commited this code?
Pradeep.
--- On Wed, 1/27/10, Uri Boness (JIRA) <ji...@apache.org> wrote:
> From: Uri Boness (JIRA) <ji...@apache.org>
> Subject: [jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr
> To: solr-dev@lucene.apache.org
> Date: Wednesday, January 27, 2010, 10:22 AM
>
> [ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805601#action_12805601
> ]
>
> Uri Boness commented on SOLR-1163:
> ----------------------------------
>
> Actually I've been working on a new version for the
> explorer which I plan to put soon as a patch here.
>
> > 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-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.
>
>
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Uri Boness (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805601#action_12805601 ]
Uri Boness commented on SOLR-1163:
----------------------------------
Actually I've been working on a new version for the explorer which I plan to put soon as a patch here.
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805511#action_12805511 ]
Grant Ingersoll commented on SOLR-1163:
---------------------------------------
Uri,
Is this patch still up to date? Is it a contrib?
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722748#action_12722748 ]
Yonik Seeley commented on SOLR-1163:
------------------------------------
I just got a chance to check out your demo site... cool stuff Uri!
Is the Console on that demo site somewhere, or is it command line?
I'll have to leave other technical comments to people who know more about GUIs.... but where do you see this fitting? Default search screen when you hit http://localhost:8983/solr/??? or something else?
> 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-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.
[jira] Updated: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Uri Boness (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uri Boness updated SOLR-1163:
-----------------------------
Attachment: graphics.zip
solr-explorer.patch
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Uri Boness (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722763#action_12722763 ]
Uri Boness commented on SOLR-1163:
----------------------------------
Thanks Yonik.
The console is in the application. If you look down at the lower right corner, you'll find a small console icon (a la FireBug), click on it and the console will open up.
Where do I see it fitting? Well, if http://localhost:8983/solr/admin is for the admin page, then I guess http://localhost:8983/solr/explorer can be for the explorer. I don't know, what do you think?
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Lance Norskog (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746528#action_12746528 ]
Lance Norskog commented on SOLR-1163:
-------------------------------------
Voted! I'm an American, so no democracy jokes, please.
About licensing - does Google put any license restrictions on distributed code?
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "kaoul kae (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749256#action_12749256 ]
kaoul kae commented on SOLR-1163:
---------------------------------
I'm new to GWT and would like to know how to setup this application for solr. Could you make a little step by step how-to as I don't know what to do with the patch. Does it go in solr src ? In a gwt project ? Where do I need to patch ?
In advance, thank you.
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Uri Boness (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749693#action_12749693 ]
Uri Boness commented on SOLR-1163:
----------------------------------
Hi Lance,
Great feedback, thanks!
bq.You did not mention the console button at the lower right corner. This is very very useful!
(well, you always have to leave some room for surprises ;-))
Obviously the two issues are bugs. I'll try to find some time this week to fix them and upload a new patch.
Cheers,
Uri
> 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-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.
[jira] Updated: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Uri Boness (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uri Boness updated SOLR-1163:
-----------------------------
Attachment: solr-explorer.patch
fixed the groupId in the pom
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Lance Norskog (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749691#action_12749691 ]
Lance Norskog commented on SOLR-1163:
-------------------------------------
Also, spellcheck build gets an error in the Solr servlet. It needs a query string; what for, I don't know.
{code}
INFO: [] webapp=/solr path=/select params={spellcheck=true&json.wrf=callback21&i
ndent=true&start=0&q=&wt=json&spellcheck.build=true} status=500 QTime=23
Aug 31, 2009 5:00:05 PM org.apache.solr.common.SolrException log
SEVERE: java.lang.NullPointerException
at java.io.StringReader.<init>(StringReader.java:33)
at org.apache.lucene.queryParser.QueryParser.parse(QueryParser.java:173)
at org.apache.solr.search.LuceneQParser.parse(LuceneQParserPlugin.java:7
8)
at org.apache.solr.search.QParser.getQuery(QParser.java:131)
at org.apache.solr.handler.component.QueryComponent.prepare(QueryCompone
nt.java:89)
at org.apache.solr.handler.component.SearchHandler.handleRequestBody(Sea
rchHandler.java:174)
at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandl
erBase.java:131)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1299)
at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter
.java:338)
at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilte
r.java:241)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet
Handler.java:1089)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:3
65)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.jav
a:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:1
81)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:7
12)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHand
lerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.
java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:1
39)
at org.mortbay.jetty.Server.handle(Server.java:285)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:50
2)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpCo
nnection.java:821)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.
java:226)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool
.java:442)
{code}
> 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-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.
[jira] Issue Comment Edited: (SOLR-1163) Solr Explorer - A generic
GWT client for Solr
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805511#action_12805511 ]
Grant Ingersoll edited comment on SOLR-1163 at 1/27/10 2:06 PM:
----------------------------------------------------------------
Uri,
Is this patch still up to date?
was (Author: gsingers):
Uri,
Is this patch still up to date? Is it a contrib?
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Lance Norskog (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749686#action_12749686 ]
Lance Norskog commented on SOLR-1163:
-------------------------------------
Hi Uri-
(You did not mention the console button at the lower right corner. This is very very useful!)
Editing a query facet did not work for me. After I made one with 'New Facet' plus-sign, I tried to edit it. I got this message:
{code}
Error occured: (TypeError): h is undefined
fileName: http://localhost:8983/solr-explorer/org.apache.solr.explorer.SolrExplorer/D95BC0B1FD429F7CB277268102D19B3E.cache.html
lineNumber: 2057
stack: vVc([object Object],[object Object],[object Object])@http://localhost:8983/solr-explorer/org.apache.solr.explorer.SolrExplorer/D95BC0B1FD429F7CB277268102D19B3E.cache.html:2057
zVc([object Object],[object Object])@http://localhost:8983/solr-explorer/org.apache.solr.explorer.SolrExplorer/D95BC0B1FD429F7CB277268102D19B3E.cache.html:2049
([object Object])@http://localhost:8983/solr-explorer/org.apache.solr.explorer.SolrExplorer/D95BC0B1FD429F7CB277268102D19B3E.cache.html:2993
@http://localhost:8983/solr/select?version=2.2&q=*:*&start=0&facet=on&facet.query=samsung&wt=json&indent=true&json.wrf=callback6:160
{code}
> 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-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.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client
for Solr
Posted by "Uri Boness (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749259#action_12749259 ]
Uri Boness commented on SOLR-1163:
----------------------------------
Hi Kaoul,
The solr explorer is a maven project. This patch adds a new folder in the contrib director. Once patched, you can go to the _contrib/solrexplorer_ directory and build the maven project (_ie. mvn clean package_). One of the artifacts of the build is the directory where the application sits in.
It's a stand-alone application that runs in the browser. As such, to run the application all you need to do is to open the SolrExplorer.html file in your browser.
To configure the application you can customize the solr-explorer.xml which sits in the same directory.
The main reason I made this patch is to contribute this whole code base to the Solr project and hopefully make it an integral part of Solr. If you want to use this tool without concerning yourself with the patch, you can also download it from:
http://www.jteam.nl/news/solrexplorer
I'm still working on the user documentation there, but it's a working version nonetheless.
> 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-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.