Re: solr UI collection dropdown sorting order
i had not idea this can be done, i'm not very web-savvy, just know some python.. On Mon, Oct 21, 2019 at 2:56 PM Erick Erickson wrote: > This is all web-kind of code, html/js/angular-or-whatever…. > > > On Oct 21, 2019, at 5:38 AM, Sotiris Fragkiskos > wrote: > > > > this is excellent!! THANKS!! > > > > On Mon, Oct 21, 2019 at 10:29 AM Charlie Hull > wrote: > > > >> I think we looked at this at our recent Hackday in DC - check out the > >> first part of this blog: > >> > >> > https://opensourceconnections.com/blog/2019/09/23/what-happens-at-a-lucene-solr-hackday/ > >> - hopefully a pointer towards getting this fixed. > >> > >> Best > >> > >> Charlie > >> > >> On 20/10/2019 09:06, Sotiris Fragkiskos wrote: > >>> Hi everyone! > >>> > >>> is there any way the collections available on the left-hand side of the > >>> solr UI can be sorted? I'm referring to the "collection selector" > >> dropdown. > >>> But the same applies to the Collections button. > >>> The sorting seems kind of..random? > >>> > >>> Thanks in advance! > >>> > >>> Sotir > >>> > >> > >> -- > >> Charlie Hull > >> Flax - Open Source Enterprise Search > >> > >> tel/fax: +44 (0)8700 118334 > >> mobile: +44 (0)7767 825828 > >> web: www.flax.co.uk > >> > >> > >
Re: solr UI collection dropdown sorting order
This is all web-kind of code, html/js/angular-or-whatever…. > On Oct 21, 2019, at 5:38 AM, Sotiris Fragkiskos wrote: > > this is excellent!! THANKS!! > > On Mon, Oct 21, 2019 at 10:29 AM Charlie Hull wrote: > >> I think we looked at this at our recent Hackday in DC - check out the >> first part of this blog: >> >> https://opensourceconnections.com/blog/2019/09/23/what-happens-at-a-lucene-solr-hackday/ >> - hopefully a pointer towards getting this fixed. >> >> Best >> >> Charlie >> >> On 20/10/2019 09:06, Sotiris Fragkiskos wrote: >>> Hi everyone! >>> >>> is there any way the collections available on the left-hand side of the >>> solr UI can be sorted? I'm referring to the "collection selector" >> dropdown. >>> But the same applies to the Collections button. >>> The sorting seems kind of..random? >>> >>> Thanks in advance! >>> >>> Sotir >>> >> >> -- >> Charlie Hull >> Flax - Open Source Enterprise Search >> >> tel/fax: +44 (0)8700 118334 >> mobile: +44 (0)7767 825828 >> web: www.flax.co.uk >> >>
Re: solr UI collection dropdown sorting order
this is excellent!! THANKS!! On Mon, Oct 21, 2019 at 10:29 AM Charlie Hull wrote: > I think we looked at this at our recent Hackday in DC - check out the > first part of this blog: > > https://opensourceconnections.com/blog/2019/09/23/what-happens-at-a-lucene-solr-hackday/ > - hopefully a pointer towards getting this fixed. > > Best > > Charlie > > On 20/10/2019 09:06, Sotiris Fragkiskos wrote: > > Hi everyone! > > > > is there any way the collections available on the left-hand side of the > > solr UI can be sorted? I'm referring to the "collection selector" > dropdown. > > But the same applies to the Collections button. > > The sorting seems kind of..random? > > > > Thanks in advance! > > > > Sotir > > > > -- > Charlie Hull > Flax - Open Source Enterprise Search > > tel/fax: +44 (0)8700 118334 > mobile: +44 (0)7767 825828 > web: www.flax.co.uk > >
Re: solr UI collection dropdown sorting order
I think we looked at this at our recent Hackday in DC - check out the first part of this blog: https://opensourceconnections.com/blog/2019/09/23/what-happens-at-a-lucene-solr-hackday/ - hopefully a pointer towards getting this fixed. Best Charlie On 20/10/2019 09:06, Sotiris Fragkiskos wrote: Hi everyone! is there any way the collections available on the left-hand side of the solr UI can be sorted? I'm referring to the "collection selector" dropdown. But the same applies to the Collections button. The sorting seems kind of..random? Thanks in advance! Sotir -- Charlie Hull Flax - Open Source Enterprise Search tel/fax: +44 (0)8700 118334 mobile: +44 (0)7767 825828 web: www.flax.co.uk
Re: solr UI collection dropdown sorting order
My java knowledge is very weak to say the least, so I can't help there unfortunately... Thanks for the reply, I have been meaning to ask for at least a year!! kind regards, Sotiri On Mon, Oct 21, 2019 at 1:54 AM Erick Erickson wrote: > Unfortunately not, although if you’d like to add that functionality to the > admin UI that’d be great. > > If you know the name, you can just start typing and not have to scroll. > > Best, > Erick > > > On Oct 20, 2019, at 4:06 AM, Sotiris Fragkiskos > wrote: > > > > Hi everyone! > > > > is there any way the collections available on the left-hand side of the > > solr UI can be sorted? I'm referring to the "collection selector" > dropdown. > > But the same applies to the Collections button. > > The sorting seems kind of..random? > > > > Thanks in advance! > > > > Sotir > >
Re: solr UI collection dropdown sorting order
Unfortunately not, although if you’d like to add that functionality to the admin UI that’d be great. If you know the name, you can just start typing and not have to scroll. Best, Erick > On Oct 20, 2019, at 4:06 AM, Sotiris Fragkiskos wrote: > > Hi everyone! > > is there any way the collections available on the left-hand side of the > solr UI can be sorted? I'm referring to the "collection selector" dropdown. > But the same applies to the Collections button. > The sorting seems kind of..random? > > Thanks in advance! > > Sotir
solr UI collection dropdown sorting order
Hi everyone! is there any way the collections available on the left-hand side of the solr UI can be sorted? I'm referring to the "collection selector" dropdown. But the same applies to the Collections button. The sorting seems kind of..random? Thanks in advance! Sotir
Re: what`s the pink segment on solr UI meaning?
On 3/8/2018 3:48 AM, 胡一博 wrote: I run solr 5.5.1. I was found some pink segments on the "Segment Info" tag of solr UI. What`s that meaning ? Is my cluster not healthy? I found the pink color (#FFC9F9) in a css file: server\solr-webapp\webapp\css\angular\segments.css It was in a definition with the name "merge-candidate". Backtracking that to HTML code, I was then able to trace further to find the Java code in the segment info handler that actually turns the segments pink. Based on what I found, I think that pink segments are those segments which the system thinks are most likely to be chosen for automatic merging, according to whatever merge policy you have active. Most likely the merge policy is TieredMergePolicy. The pink color is not an indication of a problem. Sounds like the admin UI needs a color legend for the segments display, so that users can instantly know what they are looking at. It also needs to be mentioned in the documentation, where I cannot find "pink" mentioned anywhere other than the page about the classic query parser, which is completely unrelated. Thanks, Shawn
what`s the pink segment on solr UI meaning?
hello, I run solr 5.5.1. I was found some pink segments on the "Segment Info" tag of solr UI. What`s that meaning ? Is my cluster not healthy?
Re: Regarding Solr UI authentication
On 8/11/2016 11:12 PM, Pradeep Chandra wrote: > I am running solr using the command *bin/solr start *in Ubuntu. Now I > want to give UI authentication to secure my Solr. Can you tell me how > to make Solr password protected. I am not using Zookeeper/SolrCloud. For what I would call "typical" authentication setups, the first step will be to switch to SolrCloud and use zookeeper. The basic authentication support only works from zookeeper. https://cwiki.apache.org/confluence/display/solr/Basic+Authentication+Plugin If you have an existing kerberos infrastructure, then you can enable authenticating to your kerberos server without zookeeper. This page talks about how to enable it if you're running standalone mode rather than SolrCloud: https://cwiki.apache.org/confluence/display/solr/Kerberos+Authentication+Plugin Switching to SolrCloud is probably the best option. It is likely that more and more features will require it in the future. Note: If you're adding authentication because untrustworthy people have access to your Solr server ... you really should put it someplace where those people can't reach it -- where it won't need authentication. You asked about authenticating the UI ... but it isn't actually the UI that gets authenticated. The UI is just a bunch of static html, css, and javascript that can't do much of anything on its own. Authentication happens for all the API calls that the UI uses, which are the same API calls that are used to query/update Solr from your search-enabled application. Typically *all* clients that use Solr will need to provide credentials once you enable authentication. Thanks, Shawn
Regarding Solr UI authentication
Hi I am running solr using the command *bin/solr start *in Ubuntu. Now I want to give UI authentication to secure my Solr. Can you tell me how to make Solr password protected. I am not using Zookeeper/SolrCloud. Thanks and Regards, M Pradeep Chandra
Solr UI to Display Hyperlinks
Hi All, I have nutch configured with Solr. Previous versions of Nutch has a search screen which returns Hyperlinks. How do I get the same functionality using Solr? Can someone point me to the documentations which discusses how to modify the Solr UI and returns links? sheon
Solr UI open source
Hi all, I want to build UI for Solr that get result to the user and also update the solr back (set for specific field) I start using ajax-solr because there is good tutorial and it's easy to use, but I didn't saw an example for update, and also I'm not sure the code is stable (no release in GIT) I saw also banana but it's more complicated and more relevant for time series (my data doesn't have date field) What's better for basic solr UI? Ajax-solr or banana? There is another option? Something that also update the solr and not only one way requests? Thanks, Shani - Intel Electronics Ltd. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
Re: Solr UI open source
You should not be exposing Solr directly to the user, that's like giving them a database admin account. Unless you REALLY know what you are doing. So, the Javascript UIs are mostly for internal purposes and for people to play with Solr. Therefore, usually, there is a server-side component that talks to the client and to the Solr and does the conversion of parameters, etc. If your data model not terribly complex, you could look into something like Spring, which has Spring Data Solr integration component. http://spring.io/ You'll need to code the logic of course, but it makes it simpler. If you want something more features out of the box, you could look at Hue from Cloudera http://gethue.com/ . It is mostly for big data, but has quite a number of features for Solr as well. It has some live editing too in the most recent versions, so I am not sure if it goes back into Solr or into a database that Solr is synchronized to. Regards, Alex. Newsletter and resources for Solr beginners and intermediates: http://www.solr-start.com/ On 26 November 2015 at 08:59, Chaushu, Shani <shani.chau...@intel.com> wrote: > Hi all, > I want to build UI for Solr that get result to the user and also update the > solr back (set for specific field) > I start using ajax-solr because there is good tutorial and it's easy to use, > but I didn't saw an example for update, and also I'm not sure the code is > stable (no release in GIT) > I saw also banana but it's more complicated and more relevant for time series > (my data doesn't have date field) > > What's better for basic solr UI? Ajax-solr or banana? > There is another option? Something that also update the solr and not only one > way requests? > > Thanks, > Shani > > > > - > Intel Electronics Ltd. > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies.
Re: Solr UI open source
Actually I disagree Alex. We build JS apps that talk straight to Solr all the time. However, we are sure to lock it down pretty heavily. Moreover, these cases almost never have sensitive information. You need to think through the worst case. As search is often a secondary artifact of a primary database, you can often rebuild the data in the worst case. So to me it's not like giving users access to your database. The risk is (usually) pretty low. We have a sample solr nginx proxy that disallows problematic parameters and white lists the search endpoint https://github.com/o19s/solr_nginx We also have a framework Spyglass if you are interested in Ember https://github.com/o19s/spyglass -Doug On Thu, Nov 26, 2015 at 9:30 AM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > You should not be exposing Solr directly to the user, that's like > giving them a database admin account. Unless you REALLY know what you > are doing. So, the Javascript UIs are mostly for internal purposes and > for people to play with Solr. > > Therefore, usually, there is a server-side component that talks to the > client and to the Solr and does the conversion of parameters, etc. > > If your data model not terribly complex, you could look into something > like Spring, which has Spring Data Solr integration component. > http://spring.io/ You'll need to code the logic of course, but it > makes it simpler. > > If you want something more features out of the box, you could look at > Hue from Cloudera http://gethue.com/ . It is mostly for big data, but > has quite a number of features for Solr as well. It has some live > editing too in the most recent versions, so I am not sure if it goes > back into Solr or into a database that Solr is synchronized to. > > Regards, > Alex. > > Newsletter and resources for Solr beginners and intermediates: > http://www.solr-start.com/ > > > On 26 November 2015 at 08:59, Chaushu, Shani <shani.chau...@intel.com> > wrote: > > Hi all, > > I want to build UI for Solr that get result to the user and also update > the solr back (set for specific field) > > I start using ajax-solr because there is good tutorial and it's easy to > use, but I didn't saw an example for update, and also I'm not sure the code > is stable (no release in GIT) > > I saw also banana but it's more complicated and more relevant for time > series (my data doesn't have date field) > > > > What's better for basic solr UI? Ajax-solr or banana? > > There is another option? Something that also update the solr and not > only one way requests? > > > > Thanks, > > Shani > > > > > > > > - > > Intel Electronics Ltd. > > > > This e-mail and any attachments may contain confidential material for > > the sole use of the intended recipient(s). Any review or distribution > > by others is strictly prohibited. If you are not the intended > > recipient, please contact the sender and delete all copies. > -- *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections <http://opensourceconnections.com>, LLC | 240.476.9983 Author: Relevant Search <http://manning.com/turnbull> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
Re: Solr UI open source
I am happy to be corrected, but that repository says "This repository
gives a basic outline to creating a functional reverse proxy with
Nginx" as well as the famous last words ("e.t.c.") . Which is why I
feel it is not exactly a turnkey solution I can recommend to a new
Solr user. Is there an example of a full production config anywhere?
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 26 November 2015 at 10:51, Doug Turnbull
<dturnb...@opensourceconnections.com> wrote:
> Actually I disagree Alex. We build JS apps that talk straight to Solr all
> the time.
>
> However, we are sure to lock it down pretty heavily. Moreover, these cases
> almost never have sensitive information. You need to think through the
> worst case. As search is often a secondary artifact of a primary database,
> you can often rebuild the data in the worst case. So to me it's not like
> giving users access to your database. The risk is (usually) pretty low.
>
> We have a sample solr nginx proxy that disallows problematic parameters and
> white lists the search endpoint
> https://github.com/o19s/solr_nginx
>
> We also have a framework Spyglass if you are interested in Ember
> https://github.com/o19s/spyglass
>
> -Doug
>
>
> On Thu, Nov 26, 2015 at 9:30 AM, Alexandre Rafalovitch <arafa...@gmail.com>
> wrote:
>
>> You should not be exposing Solr directly to the user, that's like
>> giving them a database admin account. Unless you REALLY know what you
>> are doing. So, the Javascript UIs are mostly for internal purposes and
>> for people to play with Solr.
>>
>> Therefore, usually, there is a server-side component that talks to the
>> client and to the Solr and does the conversion of parameters, etc.
>>
>> If your data model not terribly complex, you could look into something
>> like Spring, which has Spring Data Solr integration component.
>> http://spring.io/ You'll need to code the logic of course, but it
>> makes it simpler.
>>
>> If you want something more features out of the box, you could look at
>> Hue from Cloudera http://gethue.com/ . It is mostly for big data, but
>> has quite a number of features for Solr as well. It has some live
>> editing too in the most recent versions, so I am not sure if it goes
>> back into Solr or into a database that Solr is synchronized to.
>>
>> Regards,
>> Alex.
>>
>> Newsletter and resources for Solr beginners and intermediates:
>> http://www.solr-start.com/
>>
>>
>> On 26 November 2015 at 08:59, Chaushu, Shani <shani.chau...@intel.com>
>> wrote:
>> > Hi all,
>> > I want to build UI for Solr that get result to the user and also update
>> the solr back (set for specific field)
>> > I start using ajax-solr because there is good tutorial and it's easy to
>> use, but I didn't saw an example for update, and also I'm not sure the code
>> is stable (no release in GIT)
>> > I saw also banana but it's more complicated and more relevant for time
>> series (my data doesn't have date field)
>> >
>> > What's better for basic solr UI? Ajax-solr or banana?
>> > There is another option? Something that also update the solr and not
>> only one way requests?
>> >
>> > Thanks,
>> > Shani
>> >
>> >
>> >
>> > -
>> > Intel Electronics Ltd.
>> >
>> > This e-mail and any attachments may contain confidential material for
>> > the sole use of the intended recipient(s). Any review or distribution
>> > by others is strictly prohibited. If you are not the intended
>> > recipient, please contact the sender and delete all copies.
>>
>
>
>
> --
> *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections
> <http://opensourceconnections.com>, LLC | 240.476.9983
> Author: Relevant Search <http://manning.com/turnbull>
> This e-mail and all contents, including attachments, is considered to be
> Company Confidential unless explicitly stated otherwise, regardless
> of whether attachments are marked as such.
Re: Solr UI open source
Nope, it's more of a template. But I still think its simpler than coding up
and deploying an API that acts as a relay to a search endpoint. Again, I
don't think this is right for every use case. But we use it for
http://solr.quepid.com
In the nginx.conf, you need to basically update two spots
# Replace this with your Solr host, ie solr.quepid.com
server_name YOUR.SOLR.HOST;
And then copy the block for every search endpoint you want to support,
replacing with your collection name/
# Create a location block for each handler you'd like to whitelist
location /solr/collection1/select {
On Thu, Nov 26, 2015 at 11:14 AM, Alexandre Rafalovitch <arafa...@gmail.com>
wrote:
> I am happy to be corrected, but that repository says "This repository
> gives a basic outline to creating a functional reverse proxy with
> Nginx" as well as the famous last words ("e.t.c.") . Which is why I
> feel it is not exactly a turnkey solution I can recommend to a new
> Solr user. Is there an example of a full production config anywhere?
>
> Regards,
>Alex.
>
> Newsletter and resources for Solr beginners and intermediates:
> http://www.solr-start.com/
>
>
> On 26 November 2015 at 10:51, Doug Turnbull
> <dturnb...@opensourceconnections.com> wrote:
> > Actually I disagree Alex. We build JS apps that talk straight to Solr all
> > the time.
> >
> > However, we are sure to lock it down pretty heavily. Moreover, these
> cases
> > almost never have sensitive information. You need to think through the
> > worst case. As search is often a secondary artifact of a primary
> database,
> > you can often rebuild the data in the worst case. So to me it's not like
> > giving users access to your database. The risk is (usually) pretty low.
> >
> > We have a sample solr nginx proxy that disallows problematic parameters
> and
> > white lists the search endpoint
> > https://github.com/o19s/solr_nginx
> >
> > We also have a framework Spyglass if you are interested in Ember
> > https://github.com/o19s/spyglass
> >
> > -Doug
> >
> >
> > On Thu, Nov 26, 2015 at 9:30 AM, Alexandre Rafalovitch <
> arafa...@gmail.com>
> > wrote:
> >
> >> You should not be exposing Solr directly to the user, that's like
> >> giving them a database admin account. Unless you REALLY know what you
> >> are doing. So, the Javascript UIs are mostly for internal purposes and
> >> for people to play with Solr.
> >>
> >> Therefore, usually, there is a server-side component that talks to the
> >> client and to the Solr and does the conversion of parameters, etc.
> >>
> >> If your data model not terribly complex, you could look into something
> >> like Spring, which has Spring Data Solr integration component.
> >> http://spring.io/ You'll need to code the logic of course, but it
> >> makes it simpler.
> >>
> >> If you want something more features out of the box, you could look at
> >> Hue from Cloudera http://gethue.com/ . It is mostly for big data, but
> >> has quite a number of features for Solr as well. It has some live
> >> editing too in the most recent versions, so I am not sure if it goes
> >> back into Solr or into a database that Solr is synchronized to.
> >>
> >> Regards,
> >> Alex.
> >>
> >> Newsletter and resources for Solr beginners and intermediates:
> >> http://www.solr-start.com/
> >>
> >>
> >> On 26 November 2015 at 08:59, Chaushu, Shani <shani.chau...@intel.com>
> >> wrote:
> >> > Hi all,
> >> > I want to build UI for Solr that get result to the user and also
> update
> >> the solr back (set for specific field)
> >> > I start using ajax-solr because there is good tutorial and it's easy
> to
> >> use, but I didn't saw an example for update, and also I'm not sure the
> code
> >> is stable (no release in GIT)
> >> > I saw also banana but it's more complicated and more relevant for time
> >> series (my data doesn't have date field)
> >> >
> >> > What's better for basic solr UI? Ajax-solr or banana?
> >> > There is another option? Something that also update the solr and not
> >> only one way requests?
> >> >
> >> > Thanks,
> >> > Shani
> >> >
> >> >
> >> >
> >> > -
> >> > Intel Electronics Ltd.
> >> >
> >> > This e-mail and any attachments may conta
Re: Solr UI open source
That sounded defensive :) Just sharing our experience. I also don't mind
being corrected, especially if there's an issue with the config here.
Cheers
-Doug
On Thu, Nov 26, 2015 at 11:28 AM, Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> Nope, it's more of a template. But I still think its simpler than coding
> up and deploying an API that acts as a relay to a search endpoint. Again, I
> don't think this is right for every use case. But we use it for
> http://solr.quepid.com
>
> In the nginx.conf, you need to basically update two spots
>
> # Replace this with your Solr host, ie solr.quepid.com
> server_name YOUR.SOLR.HOST;
>
> And then copy the block for every search endpoint you want to support,
> replacing with your collection name/
>
> # Create a location block for each handler you'd like to whitelist
> location /solr/collection1/select {
>
>
> On Thu, Nov 26, 2015 at 11:14 AM, Alexandre Rafalovitch <
> arafa...@gmail.com> wrote:
>
>> I am happy to be corrected, but that repository says "This repository
>> gives a basic outline to creating a functional reverse proxy with
>> Nginx" as well as the famous last words ("e.t.c.") . Which is why I
>> feel it is not exactly a turnkey solution I can recommend to a new
>> Solr user. Is there an example of a full production config anywhere?
>>
>> Regards,
>>Alex.
>>
>> Newsletter and resources for Solr beginners and intermediates:
>> http://www.solr-start.com/
>>
>>
>> On 26 November 2015 at 10:51, Doug Turnbull
>> <dturnb...@opensourceconnections.com> wrote:
>> > Actually I disagree Alex. We build JS apps that talk straight to Solr
>> all
>> > the time.
>> >
>> > However, we are sure to lock it down pretty heavily. Moreover, these
>> cases
>> > almost never have sensitive information. You need to think through the
>> > worst case. As search is often a secondary artifact of a primary
>> database,
>> > you can often rebuild the data in the worst case. So to me it's not like
>> > giving users access to your database. The risk is (usually) pretty low.
>> >
>> > We have a sample solr nginx proxy that disallows problematic parameters
>> and
>> > white lists the search endpoint
>> > https://github.com/o19s/solr_nginx
>> >
>> > We also have a framework Spyglass if you are interested in Ember
>> > https://github.com/o19s/spyglass
>> >
>> > -Doug
>> >
>> >
>> > On Thu, Nov 26, 2015 at 9:30 AM, Alexandre Rafalovitch <
>> arafa...@gmail.com>
>> > wrote:
>> >
>> >> You should not be exposing Solr directly to the user, that's like
>> >> giving them a database admin account. Unless you REALLY know what you
>> >> are doing. So, the Javascript UIs are mostly for internal purposes and
>> >> for people to play with Solr.
>> >>
>> >> Therefore, usually, there is a server-side component that talks to the
>> >> client and to the Solr and does the conversion of parameters, etc.
>> >>
>> >> If your data model not terribly complex, you could look into something
>> >> like Spring, which has Spring Data Solr integration component.
>> >> http://spring.io/ You'll need to code the logic of course, but it
>> >> makes it simpler.
>> >>
>> >> If you want something more features out of the box, you could look at
>> >> Hue from Cloudera http://gethue.com/ . It is mostly for big data, but
>> >> has quite a number of features for Solr as well. It has some live
>> >> editing too in the most recent versions, so I am not sure if it goes
>> >> back into Solr or into a database that Solr is synchronized to.
>> >>
>> >> Regards,
>> >> Alex.
>> >>
>> >> Newsletter and resources for Solr beginners and intermediates:
>> >> http://www.solr-start.com/
>> >>
>> >>
>> >> On 26 November 2015 at 08:59, Chaushu, Shani <shani.chau...@intel.com>
>> >> wrote:
>> >> > Hi all,
>> >> > I want to build UI for Solr that get result to the user and also
>> update
>> >> the solr back (set for specific field)
>> >> > I start using ajax-solr because there is good tutorial and it's easy
>> to
>> >> use, but I didn't saw an example for update, and also I'm not sure the
>> code
>> >> is stable (no release in GIT)
>> >> > I saw als
Re: Solr UI open source
If it works for Quepid, it is good enough for me :-) I might actually
try that for one of my upcoming projects where I do need a read-only
Solr.
But this is for read-only setup only. So, still not really useful for
the original request's second part: "There is another option?
Something that also update the solr and not only one way requests?"
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 26 November 2015 at 11:29, Doug Turnbull
<dturnb...@opensourceconnections.com> wrote:
> That sounded defensive :) Just sharing our experience. I also don't mind
> being corrected, especially if there's an issue with the config here.
>
> Cheers
> -Doug
>
> On Thu, Nov 26, 2015 at 11:28 AM, Doug Turnbull <
> dturnb...@opensourceconnections.com> wrote:
>
>> Nope, it's more of a template. But I still think its simpler than coding
>> up and deploying an API that acts as a relay to a search endpoint. Again, I
>> don't think this is right for every use case. But we use it for
>> http://solr.quepid.com
>>
>> In the nginx.conf, you need to basically update two spots
>>
>> # Replace this with your Solr host, ie solr.quepid.com
>> server_name YOUR.SOLR.HOST;
>>
>> And then copy the block for every search endpoint you want to support,
>> replacing with your collection name/
>>
>> # Create a location block for each handler you'd like to whitelist
>> location /solr/collection1/select {
>>
>>
>> On Thu, Nov 26, 2015 at 11:14 AM, Alexandre Rafalovitch <
>> arafa...@gmail.com> wrote:
>>
>>> I am happy to be corrected, but that repository says "This repository
>>> gives a basic outline to creating a functional reverse proxy with
>>> Nginx" as well as the famous last words ("e.t.c.") . Which is why I
>>> feel it is not exactly a turnkey solution I can recommend to a new
>>> Solr user. Is there an example of a full production config anywhere?
>>>
>>> Regards,
>>>Alex.
>>>
>>> Newsletter and resources for Solr beginners and intermediates:
>>> http://www.solr-start.com/
>>>
>>>
>>> On 26 November 2015 at 10:51, Doug Turnbull
>>> <dturnb...@opensourceconnections.com> wrote:
>>> > Actually I disagree Alex. We build JS apps that talk straight to Solr
>>> all
>>> > the time.
>>> >
>>> > However, we are sure to lock it down pretty heavily. Moreover, these
>>> cases
>>> > almost never have sensitive information. You need to think through the
>>> > worst case. As search is often a secondary artifact of a primary
>>> database,
>>> > you can often rebuild the data in the worst case. So to me it's not like
>>> > giving users access to your database. The risk is (usually) pretty low.
>>> >
>>> > We have a sample solr nginx proxy that disallows problematic parameters
>>> and
>>> > white lists the search endpoint
>>> > https://github.com/o19s/solr_nginx
>>> >
>>> > We also have a framework Spyglass if you are interested in Ember
>>> > https://github.com/o19s/spyglass
>>> >
>>> > -Doug
>>> >
>>> >
>>> > On Thu, Nov 26, 2015 at 9:30 AM, Alexandre Rafalovitch <
>>> arafa...@gmail.com>
>>> > wrote:
>>> >
>>> >> You should not be exposing Solr directly to the user, that's like
>>> >> giving them a database admin account. Unless you REALLY know what you
>>> >> are doing. So, the Javascript UIs are mostly for internal purposes and
>>> >> for people to play with Solr.
>>> >>
>>> >> Therefore, usually, there is a server-side component that talks to the
>>> >> client and to the Solr and does the conversion of parameters, etc.
>>> >>
>>> >> If your data model not terribly complex, you could look into something
>>> >> like Spring, which has Spring Data Solr integration component.
>>> >> http://spring.io/ You'll need to code the logic of course, but it
>>> >> makes it simpler.
>>> >>
>>> >> If you want something more features out of the box, you could look at
>>> >> Hue from Cloudera http://gethue.com/ . It is mostly for big data, but
>>> >> has quite a number of features for Solr as well. It has some live
>>> >> editing too in the most recent versions, so I am not sure if it goes
>>> >&
Re: Solr UI open source
gt; >>> >> If your data model not terribly complex, you could look into > something > >>> >> like Spring, which has Spring Data Solr integration component. > >>> >> http://spring.io/ You'll need to code the logic of course, but it > >>> >> makes it simpler. > >>> >> > >>> >> If you want something more features out of the box, you could look > at > >>> >> Hue from Cloudera http://gethue.com/ . It is mostly for big data, > but > >>> >> has quite a number of features for Solr as well. It has some live > >>> >> editing too in the most recent versions, so I am not sure if it goes > >>> >> back into Solr or into a database that Solr is synchronized to. > >>> >> > >>> >> Regards, > >>> >> Alex. > >>> >> > >>> >> Newsletter and resources for Solr beginners and intermediates: > >>> >> http://www.solr-start.com/ > >>> >> > >>> >> > >>> >> On 26 November 2015 at 08:59, Chaushu, Shani < > shani.chau...@intel.com> > >>> >> wrote: > >>> >> > Hi all, > >>> >> > I want to build UI for Solr that get result to the user and also > >>> update > >>> >> the solr back (set for specific field) > >>> >> > I start using ajax-solr because there is good tutorial and it's > easy > >>> to > >>> >> use, but I didn't saw an example for update, and also I'm not sure > the > >>> code > >>> >> is stable (no release in GIT) > >>> >> > I saw also banana but it's more complicated and more relevant for > >>> time > >>> >> series (my data doesn't have date field) > >>> >> > > >>> >> > What's better for basic solr UI? Ajax-solr or banana? > >>> >> > There is another option? Something that also update the solr and > not > >>> >> only one way requests? > >>> >> > > >>> >> > Thanks, > >>> >> > Shani > >>> >> > > >>> >> > > >>> >> > > >>> >> > > - > >>> >> > Intel Electronics Ltd. > >>> >> > > >>> >> > This e-mail and any attachments may contain confidential material > for > >>> >> > the sole use of the intended recipient(s). Any review or > distribution > >>> >> > by others is strictly prohibited. If you are not the intended > >>> >> > recipient, please contact the sender and delete all copies. > >>> >> > >>> > > >>> > > >>> > > >>> > -- > >>> > *Doug Turnbull **| *Search Relevance Consultant | OpenSource > Connections > >>> > <http://opensourceconnections.com>, LLC | 240.476.9983 > >>> > Author: Relevant Search <http://manning.com/turnbull> > >>> > This e-mail and all contents, including attachments, is considered > to be > >>> > Company Confidential unless explicitly stated otherwise, regardless > >>> > of whether attachments are marked as such. > >>> > >> > >> > >> > >> -- > >> *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections > >> <http://opensourceconnections.com>, LLC | 240.476.9983 > >> Author: Relevant Search <http://manning.com/turnbull> > >> This e-mail and all contents, including attachments, is considered to be > >> Company Confidential unless explicitly stated otherwise, regardless > >> of whether attachments are marked as such. > >> > > > > > > > > -- > > *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections > > <http://opensourceconnections.com>, LLC | 240.476.9983 > > Author: Relevant Search <http://manning.com/turnbull> > > This e-mail and all contents, including attachments, is considered to be > > Company Confidential unless explicitly stated otherwise, regardless > > of whether attachments are marked as such. > -- *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections <http://opensourceconnections.com>, LLC | 240.476.9983 Author: Relevant Search <http://manning.com/turnbull> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
Many PDFs indexed but only one returned in te Solr-UI
I followed the example here
(http://searchhub.org/2012/02/14/indexing-with-solrj/) for indexing all the
pdfs in a directory. The process seems to work well, but at the end, when I go
in the Solr-UI and click on Execute query(with q=*:*), I get only one entry.
Do I miss something in my code?
...
String[] files = documentDir.list();
if (files != null)
{
for (String document : files)
{
ContentHandler textHandler = new BodyContentHandler();
Metadata metadata = new Metadata();
ParseContext context = new ParseContext();
AutoDetectParser autoDetectParser = new AutoDetectParser();
InputStream inputStream = null;
try
{
inputStream = new FileInputStream(new File(documentDir, document));
autoDetectParser.parse(inputStream, textHandler, metadata, context);
SolrInputDocument doc = new SolrInputDocument();
doc.addField(id, document);
String content = textHandler.toString();
if (content != null)
{
doc.addField(fullText, content);
}
UpdateResponse resp = server.add(doc, 1);
server.commit(true, true, true);
if (resp.getStatus() != 0)
{
throw new IDSystemException(LOG, Document could not be indexed.
Status returned: + resp.getStatus());
}
}
catch (FileNotFoundException fnfe)
{
throw new IDSystemException(LOG, fnfe.getMessage(), fnfe);
}
catch (IOException ioe)
{
throw new IDSystemException(LOG, ioe.getMessage(), ioe);
}
catch (SAXException se)
{
throw new IDSystemException(LOG, se.getMessage(), se);
}
catch (TikaException te)
{
throw new IDSystemException(LOG, te.getMessage(), te);
}
catch (SolrServerException sse)
{
throw new IDSystemException(LOG, sse.getMessage(), sse);
}
finally
{
if (inputStream != null)
{
try
{
inputStream.close();
}
catch (IOException ioe)
{
throw new IDSystemException(LOG, ioe.getMessage(), ioe);
}
}
}
...
Thank you for any hint.
Francesco
Re: Many PDFs indexed but only one returned in te Solr-UI
Hmmm, that looks OK to me. I'd log out
the id you assign for each document,
it's _possible_ that somehow you're
getting the same ID for all the files
except this line should be preventing that:
doc.addField(id, document);
Tail the Solr log while you're doing this and
see the update messages to insure that there
are more than one. And I'm assuming that
you've got more than one file in your directory.
BTW, doing the commit after every doc is
generally poor practice in production.I know
you're just testing now, but thought I'd
mention it. Let autocommit handle most of it
and (perhaps) commit once at the end.
Hmmm, silly question perhaps, but are you
absolutely sure that you're querying the same
core you're indexing to? On the same machine?
Sometimes as a sanity check I'll add, say,
a timestamp to the id field (i.e.
doc.add(id, filename + timestamp) just to
have something that changes every run.
Best
Erick
On Tue, Mar 11, 2014 at 6:00 AM, Croci Francesco Luigi (ID SWS)
fcr...@id.ethz.ch wrote:
I followed the example here
(http://searchhub.org/2012/02/14/indexing-with-solrj/) for indexing all the
pdfs in a directory. The process seems to work well, but at the end, when I
go in the Solr-UI and click on Execute query(with q=*:*), I get only one
entry.
Do I miss something in my code?
...
String[] files = documentDir.list();
if (files != null)
{
for (String document : files)
{
ContentHandler textHandler = new BodyContentHandler();
Metadata metadata = new Metadata();
ParseContext context = new ParseContext();
AutoDetectParser autoDetectParser = new AutoDetectParser();
InputStream inputStream = null;
try
{
inputStream = new FileInputStream(new File(documentDir, document));
autoDetectParser.parse(inputStream, textHandler, metadata, context);
SolrInputDocument doc = new SolrInputDocument();
doc.addField(id, document);
String content = textHandler.toString();
if (content != null)
{
doc.addField(fullText, content);
}
UpdateResponse resp = server.add(doc, 1);
server.commit(true, true, true);
if (resp.getStatus() != 0)
{
throw new IDSystemException(LOG, Document could not be indexed.
Status returned: + resp.getStatus());
}
}
catch (FileNotFoundException fnfe)
{
throw new IDSystemException(LOG, fnfe.getMessage(), fnfe);
}
catch (IOException ioe)
{
throw new IDSystemException(LOG, ioe.getMessage(), ioe);
}
catch (SAXException se)
{
throw new IDSystemException(LOG, se.getMessage(), se);
}
catch (TikaException te)
{
throw new IDSystemException(LOG, te.getMessage(), te);
}
catch (SolrServerException sse)
{
throw new IDSystemException(LOG, sse.getMessage(), sse);
}
finally
{
if (inputStream != null)
{
try
{
inputStream.close();
}
catch (IOException ioe)
{
throw new IDSystemException(LOG, ioe.getMessage(), ioe);
}
}
}
...
Thank you for any hint.
Francesco
RE: Many PDFs indexed but only one returned in te Solr-UI
Hi Erik,
you were right...
I had the signatureField bound to the uid in the solrconfig.xml, so the uid
was always the same.
Now I defined a new field for the signatureField and it works!
Before:
...
updateRequestProcessorChain name=deduplication
processor
class=org.apache.solr.update.processor.SignatureUpdateProcessorFactory
bool name=overwriteDupesfalse/bool
str name=signatureFielduid/str -
bool name=enabledtrue/bool
str name=fieldscontent/str
str name=minTokenLen10/str
str name=quantRate.2/str
str
name=signatureClasssolr.update.processor.TextProfileSignature/str
/processor
processor class=solr.LogUpdateProcessorFactory /
processor class=solr.RunUpdateProcessorFactory /
/updateRequestProcessorChain...
...
fields
field name=uid type=string indexed=true stored=true
multiValued=false /
dynamicField name=ignored_* type=ignored multiValued=true
indexed=false stored=fasle /
field name=id type=string indexed=true stored=true
multiValued=false /
field name=fullText indexed=true type=text multiValued=true /
/fields
uniqueKeyuid/uniqueKey
After:
...
updateRequestProcessorChain name=deduplication
processor
class=org.apache.solr.update.processor.SignatureUpdateProcessorFactory
bool name=overwriteDupesfalse/bool
str name=signatureFieldsignatureField/str
-
bool name=enabledtrue/bool
str name=fieldscontent/str
str name=minTokenLen10/str
str name=quantRate.2/str
str
name=signatureClasssolr.update.processor.TextProfileSignature/str
/processor
processor class=solr.LogUpdateProcessorFactory /
processor class=solr.RunUpdateProcessorFactory /
/updateRequestProcessorChain...
...
fields
field name=uid type=string indexed=true stored=true
multiValued=false /
field name=signatureField type=string indexed=true stored=true
multiValued=false / --
dynamicField name=ignored_* type=ignored multiValued=true
indexed=false stored=fasle /
field name=id type=string indexed=true stored=true
multiValued=false /
field name=fullText indexed=true type=text multiValued=true /
/fields
uniqueKeyuid/uniqueKey
Greetings
Francesco
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Dienstag, 11. März 2014 12:46
To: solr-user@lucene.apache.org
Subject: Re: Many PDFs indexed but only one returned in te Solr-UI
Hmmm, that looks OK to me. I'd log out
the id you assign for each document,
it's _possible_ that somehow you're
getting the same ID for all the files
except this line should be preventing that:
doc.addField(id, document);
Tail the Solr log while you're doing this and see the update messages to insure
that there are more than one. And I'm assuming that you've got more than one
file in your directory.
BTW, doing the commit after every doc is generally poor practice in
production.I know you're just testing now, but thought I'd mention it. Let
autocommit handle most of it and (perhaps) commit once at the end.
Hmmm, silly question perhaps, but are you absolutely sure that you're querying
the same core you're indexing to? On the same machine?
Sometimes as a sanity check I'll add, say, a timestamp to the id field (i.e.
doc.add(id, filename + timestamp) just to have something that changes every
run.
Best
Erick
On Tue, Mar 11, 2014 at 6:00 AM, Croci Francesco Luigi (ID SWS)
fcr...@id.ethz.ch wrote:
I followed the example here
(http://searchhub.org/2012/02/14/indexing-with-solrj/) for indexing all the
pdfs in a directory. The process seems to work well, but at the end, when I
go in the Solr-UI and click on Execute query(with q=*:*), I get only one
entry.
Do I miss something in my code?
...
String[] files = documentDir.list();
if (files != null)
{
for (String document : files)
{
ContentHandler textHandler = new BodyContentHandler();
Metadata metadata = new Metadata();
ParseContext context = new ParseContext();
AutoDetectParser autoDetectParser = new AutoDetectParser();
InputStream inputStream = null;
try
{
inputStream = new FileInputStream(new File(documentDir,
document));
autoDetectParser.parse(inputStream, textHandler, metadata,
context);
SolrInputDocument doc = new SolrInputDocument();
doc.addField(id, document);
String content = textHandler.toString();
if (content != null)
{
doc.addField(fullText, content);
}
UpdateResponse resp = server.add(doc, 1
Re: solr UI logging when using logback?
On 5/20/2013 11:23 PM, Boogie Shafer wrote: in the _MM_DD-HHmmssSSS.start.log i get messages like this cat 2013_05_15-141100827.start.log Establishing start.log on Wed May 15 14:11:12 PDT 2013 14:11:15,756 |-INFO in null - Will use configuration file [resources/logback-access.xml] 14:11:15,768 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set 14:11:15,769 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 14:11:15,770 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 14:11:15,770 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 14:11:15,774 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use gz compression That's really interesting. This appears to be the initialization of logback itself, not jetty. If nobody steps up who's familiar with slf4j/logback with jetty, you might need to use a mailing list for one of those projects. Thanks, Shawn
Re: solr UI logging when using logback?
Ah I vaguely remember seeing that when we first used logback (on 4.0), as Shawn says I think its the problem that as logback is starting up, where can it log before it has configured its logging (catch-22), answer it has to log to its own internal format. If memory serves we just disabled that logging, but I don't recall the exact syntax, I don't have access to my work setup now, but will try and check tomorrow. We don't use the request log, so that is one difference. -Original Message- From: Shawn Heisey Sent: Tuesday, May 21, 2013 1:42 PM To: solr-user@lucene.apache.org Subject: Re: solr UI logging when using logback? On 5/20/2013 11:23 PM, Boogie Shafer wrote: in the _MM_DD-HHmmssSSS.start.log i get messages like this cat 2013_05_15-141100827.start.log Establishing start.log on Wed May 15 14:11:12 PDT 2013 14:11:15,756 |-INFO in null - Will use configuration file [resources/logback-access.xml] 14:11:15,768 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set 14:11:15,769 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 14:11:15,770 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 14:11:15,770 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 14:11:15,774 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use gz compression That's really interesting. This appears to be the initialization of logback itself, not jetty. If nobody steps up who's familiar with slf4j/logback with jetty, you might need to use a mailing list for one of those projects. Thanks, Shawn
solr UI logging when using logback?
i have logging working for the most part with logback 1.0.13 and slf4j 1.7.5 under solr 4.3.0 (or previously under solr 4.2.1) with two exceptions, i'm very happy with the setup as i can get all the jetty request logs, and various solr service events logged out with rotation, etc BUT i havent figured out what i need to do to get the logging events to display in the SOLR admin ui e.g. at http://solr-hostname:8983/solr/#/~logging AND i'm wondering if its possible to get the jetty start log managed under logback anybody have any pointers on these topics? --- the configuration details of my setup are summarized in the rpm building process here https://github.com/boogieshafer/jetty-solr-rpm
Re: solr UI logging when using logback?
On 5/20/2013 10:44 AM, Boogie Shafer wrote: BUT i havent figured out what i need to do to get the logging events to display in the SOLR admin ui e.g. at http://solr-hostname:8983/solr/#/~logging The logging page in the UI is populated by log watcher classes specific to the logging implementation. Prior to 4.3, the only watcher available in released Solr versions was the one for java.util.logging. The log4j watcher was incorporated in the 4.3.0 release. I have been using log4j since 4.1-SNAPSHOT, but I don't yet have any 4.3 servers in production, so I can't get logs in my UI. To get log events in the UI with logback, you would need to implement a watcher specifically for logback. I don't think this is a high priority item for the project at the moment, but patches are welcome. AND i'm wondering if its possible to get the jetty start log managed under logback On my setup using the jetty included with Solr and the slf4j/log4j jars in lib/ext, all jetty log entries are logged to the same file as my Solr logs, according to my log4j.properties file. If you have any logging config for jetty itself, then that will be used. The easiest way to proceed is to simply comment or remove that logging config. That will cause jetty to find slf4j in the classpath and use it, which you have already configured to use logback. The example jetty config does not have any logging configured. Thanks, Shawn
Re: solr UI logging when using logback?
thanks for the pointer on the missing logwatcher for logback...i'll take a look at that. on the jetty logging side of things i get nearly all the jetty logging but the initial startup logs which seem to happen prior to the other logging jars getting loaded. perhaps i need to add a few more statements to my logback.xml config, but it seems to be getting its naming _MM_DD-HHmmssSSS.start.log and pattern from somewhere outside logback. in the _MM_DD-HHmmssSSS.start.log i get messages like this cat 2013_05_15-141100827.start.log Establishing start.log on Wed May 15 14:11:12 PDT 2013 14:11:15,756 |-INFO in null - Will use configuration file [resources/logback-access.xml] 14:11:15,768 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set 14:11:15,769 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 14:11:15,770 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 14:11:15,770 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 14:11:15,774 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use gz compression On Mon, May 20, 2013 at 10:11 AM, Shawn Heisey s...@elyograg.org wrote: On 5/20/2013 10:44 AM, Boogie Shafer wrote: BUT i havent figured out what i need to do to get the logging events to display in the SOLR admin ui e.g. at http://solr-hostname:8983/**solr/#/~logginghttp://solr-hostname:8983/solr/#/~logging The logging page in the UI is populated by log watcher classes specific to the logging implementation. Prior to 4.3, the only watcher available in released Solr versions was the one for java.util.logging. The log4j watcher was incorporated in the 4.3.0 release. I have been using log4j since 4.1-SNAPSHOT, but I don't yet have any 4.3 servers in production, so I can't get logs in my UI. To get log events in the UI with logback, you would need to implement a watcher specifically for logback. I don't think this is a high priority item for the project at the moment, but patches are welcome. AND i'm wondering if its possible to get the jetty start log managed under logback On my setup using the jetty included with Solr and the slf4j/log4j jars in lib/ext, all jetty log entries are logged to the same file as my Solr logs, according to my log4j.properties file. If you have any logging config for jetty itself, then that will be used. The easiest way to proceed is to simply comment or remove that logging config. That will cause jetty to find slf4j in the classpath and use it, which you have already configured to use logback. The example jetty config does not have any logging configured. Thanks, Shawn
Re: query builder for solr UI?
sorry, The easiest way to describe it is specifically we desire a google-like experience. so if the end user types in a phrase or quotes or +, - (for and, not) etc etc. the UI will be flexible enough to build the correct solr query syntax. How will edismax help? And I tried simplifying queries by using the copyfield command to copy all of the metadata to the text field. So now the only field we have to query is the text field but I doubt that is going to be a panacea. Does that make sense? Thanks, -- View this message in context: http://lucene.472066.n3.nabble.com/query-builder-for-solr-UI-tp4043481p4043643.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: query builder for solr UI?
Hi, Have you tried edismax across your original (not text copyfield) fiels? If no, try it. If yes, which of your expectations did it not satisfy? Why would you want to build a query yourself, when Solr's queryParser is made to do just that for you from the input query string? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com 28. feb. 2013 kl. 14:39 skrev eShard zim...@yahoo.com: sorry, The easiest way to describe it is specifically we desire a google-like experience. so if the end user types in a phrase or quotes or +, - (for and, not) etc etc. the UI will be flexible enough to build the correct solr query syntax. How will edismax help? And I tried simplifying queries by using the copyfield command to copy all of the metadata to the text field. So now the only field we have to query is the text field but I doubt that is going to be a panacea. Does that make sense? Thanks, -- View this message in context: http://lucene.472066.n3.nabble.com/query-builder-for-solr-UI-tp4043481p4043643.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: query builder for solr UI?
Good question, if the user types in special characters like the dash - How will I know to treat it like a dash or the NOT operator? The first one will need to be URL encoded the second one won't be resulting in very different queries. So I apologize for not being more clear, so really what I'm after is making it easy for the user to communicate what exactly they are looking for and to URL encode their input correctly. that's what I meant by query building Thanks, -- View this message in context: http://lucene.472066.n3.nabble.com/query-builder-for-solr-UI-tp4043481p4043659.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: query builder for solr UI?
Again - what problems did you face when attempting this with the eDismax parser? Are you saying you are unhappy with the way eDisMax interprets -foo as NOT foo? A dash on its own - is treated like a dash. Your JavaScript code would anyway need to handle URL encoding properly so that a query input for +foo is sent to Solr as q=%2Bfoo, since the plus otherwise would be a space :) So simply urlencode the whole user input when constructing your URL. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com 28. feb. 2013 kl. 15:46 skrev eShard zim...@yahoo.com: Good question, if the user types in special characters like the dash - How will I know to treat it like a dash or the NOT operator? The first one will need to be URL encoded the second one won't be resulting in very different queries. So I apologize for not being more clear, so really what I'm after is making it easy for the user to communicate what exactly they are looking for and to URL encode their input correctly. that's what I meant by query building Thanks, -- View this message in context: http://lucene.472066.n3.nabble.com/query-builder-for-solr-UI-tp4043481p4043659.html Sent from the Solr - User mailing list archive at Nabble.com.
query builder for solr UI?
Good day, Currently we are building a front end for solr (in jquery, html, and css) and I'm struggling with making a query builder that can handle pretty much whatever the end user types into the search box. does something like this already exist in javascript/jquery? Thanks, -- View this message in context: http://lucene.472066.n3.nabble.com/query-builder-for-solr-UI-tp4043481.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: query builder for solr UI?
Hi, Can you be more specific on what query you want to build an what you expect end users to enter into that/those boxes? Why are you not just using eDisMax? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com 27. feb. 2013 kl. 22:05 skrev eShard zim...@yahoo.com: Good day, Currently we are building a front end for solr (in jquery, html, and css) and I'm struggling with making a query builder that can handle pretty much whatever the end user types into the search box. does something like this already exist in javascript/jquery? Thanks, -- View this message in context: http://lucene.472066.n3.nabble.com/query-builder-for-solr-UI-tp4043481.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: How to change Solr UI
you need to separate UI from Solr. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 9:29 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI On Dec 4, 2012, at 08:21 , Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. Point taken about being clear about this. But I disagree about removing /browse. It's useful, even if misunderstood/abused by some. If there are spots where we need to be clearer about what it is that is being rendered, how it's rendered, and the pros/cons to it, then let's see about getting it mentioned more clearly. But do keep in mind that something like this example: having Solr return suggestion lists as plain text suitable for suggest interfaces rather than having it return JSON or XML and having a middle tier process it when all you need is a plain list or some CSV. It's quite fine and sensible to use wt=velocity behind the firewall too, even /browse as-is. Same as with the XSL transformation writing capability. Erik=
Re: How to change Solr UI
(obviously) take these days, and it's getting some more attention, it looks like, soon. Blacklight and VuFind are much more richly capable. So there's options already out there, and surely many others that I don't even mention. A new top-level wiki page seems warranted from this discussion from http://wiki.apache.org/solr/FrontPage to list off all the various front-ends available. Erik On Dec 4, 2012, at 12:11 , Upayavira wrote: That's an interesting take. I agree that Solr needs *something* for folks to use. It is unfortunate that Solr actually has a functioning HTTP infrastructure, because it then makes less sense to build an alternative one up. E.g. How about: http://localhost:8983/solr - admin UI http://localhost:8983/browse - separate browse webapp It would be a separate app that runs as another wepapp, accessing Solr via HTTP just as any other app would. It could still use Velocity, but would demonstrate that you shouldn't integrate your app with Solr. A minimal dependency app for demonstration purposes only. Upayavira On Tue, Dec 4, 2012, at 02:37 PM, Jack Krupansky wrote: Or, maybe integrate /browse with the Solr Admin UI and give it a graphic treatment that screams that it is a development tool and not designed to be a model for an app UI. And, I still think it would be good to include SOME example of a prototype app UI with Solr, to drive home the point of here is [an example of] how you need to separate UI from Solr. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 9:29 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI On Dec 4, 2012, at 08:21 , Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. Point taken about being clear about this. But I disagree about removing /browse. It's useful, even if misunderstood/abused by some. If there are spots where we need to be clearer about what it is that is being rendered, how it's rendered, and the pros/cons to it, then let's see about getting it mentioned more clearly. But do keep in mind that something like this example: having Solr return suggestion lists as plain text suitable for suggest interfaces rather than having it return JSON or XML and having a middle tier process it when all you need is a plain list or some CSV. It's quite fine and sensible to use wt=velocity behind the firewall too, even /browse as-is. Same as with the XSL transformation writing capability. Erik=
Re: How to change Solr UI
I realised yesterday what useful about /browse, and why it is wrong as it is. The browse interface is a good way for a newcomer to explore some aspects of the query response without having to pour through lots of XML or JSON. It gives them a visual representation of their query result. While that's useful, /browse using Velocity also gives the impression that using Velocity for this purpose is a good idea, which it so clearly isn't. My thought, then, is that we should migrate the functionality of /browse over to the admin UI. My thoughts are that the query pane should, on the left, have 'simple' and 'advanced' tabs. The simple tab gives a more conventional search interface, whereas the advanced tab shows whats there currently. On the right, along the top you'd have buttons for XML, JSON, etc. One other button, HTML, would display the results of your search a bit more prettily, more like a conventional search results, or at least as much like that as possible when you really don't know much about what data you're getting back. To put my money where my mouth is, I've uploaded a patch to JIRA[1] with a first pass at what I mean. Thoughts/comments welcome. Upayavira [1] https://issues.apache.org/jira/browse/SOLR-4157 On Tue, Dec 4, 2012, at 10:41 PM, Upayavira wrote: But there's value in having something packaged within Solr itself, for demo purposes. That would I suspect make it Java (like it or not!) And that would probably not make it very state-of-the art, unless it used jquery, with a very lightweight java portion, which would be possible. Upayavira On Tue, Dec 4, 2012, at 05:42 PM, Erik Hatcher wrote: And basically that's what i had in mind with Prism here: https://github.com/lucidimagination/Prism Prism's very lightweight, uses Velocity (or not, any Ruby templating technology available), and is entirely separate from Solr. Before that there was Flare: https://github.com/erikhatcher/solr-ruby-flare/tree/master/flare. Prism is the approach I'd (obviously) take these days, and it's getting some more attention, it looks like, soon. Blacklight and VuFind are much more richly capable. So there's options already out there, and surely many others that I don't even mention. A new top-level wiki page seems warranted from this discussion from http://wiki.apache.org/solr/FrontPage to list off all the various front-ends available. Erik On Dec 4, 2012, at 12:11 , Upayavira wrote: That's an interesting take. I agree that Solr needs *something* for folks to use. It is unfortunate that Solr actually has a functioning HTTP infrastructure, because it then makes less sense to build an alternative one up. E.g. How about: http://localhost:8983/solr - admin UI http://localhost:8983/browse - separate browse webapp It would be a separate app that runs as another wepapp, accessing Solr via HTTP just as any other app would. It could still use Velocity, but would demonstrate that you shouldn't integrate your app with Solr. A minimal dependency app for demonstration purposes only. Upayavira On Tue, Dec 4, 2012, at 02:37 PM, Jack Krupansky wrote: Or, maybe integrate /browse with the Solr Admin UI and give it a graphic treatment that screams that it is a development tool and not designed to be a model for an app UI. And, I still think it would be good to include SOME example of a prototype app UI with Solr, to drive home the point of here is [an example of] how you need to separate UI from Solr. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 9:29 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI On Dec 4, 2012, at 08:21 , Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. Point taken about being clear about this. But I disagree about removing /browse. It's useful, even if misunderstood/abused by some. If there are spots where we need to be clearer about what it is that is being rendered, how it's rendered, and the pros/cons to it, then let's see about getting it mentioned more clearly. But do keep in mind that something like this example: having Solr return suggestion lists as plain text suitable for suggest interfaces rather than having it return JSON or XML and having a middle tier process it when all you need is a plain list or some CSV
Re: How to change Solr UI
It's a shame wt=velocity gets a bad rap because /update isn't out of the box strict with the HTTP/RESTful scene. A delete should be a DELETE of some sort. There are 3rd party standalone apps. There was even a standalone ruby app (flare) that was once upon a time in Solr's svn, but really the Solr committers can't be expected to maintain all those various examples and keep them up to date and working, so best to keep them 3rd party IMO. We've got Blacklight, VuFind, and all sorts of other front-ends out there with their own vibrant communities. I'm -1 for removing VW (it's contrib plugin as it is already, just like /update/extract). /browse certainly could use a cleaning up / revamping, but it's good stuff if I do say so myself and very handy to have available for several reasons*. Let's try not to conflate wt=velocity with /update being more easily dangerous than it probably should be. But let's also be clear always that Solr is meant to be behind the firewall as it's primary and default place in the world. Erik * One I'll share: There is a real-world use case of a (relatively big) company using wt=velocity to generate e-mail (for saved searches) texts very conveniently in a backend environment and very high speed, no other technologies/complexities needed in the mix but Solr and a little custom templating. On Dec 3, 2012, at 20:58 , Jack Krupansky wrote: It is annoying to have to repeat these explanations so much. Any serious objection to removing the VW UI from Solr proper and replacing it with a standalone app? I mean, Solr should have PHP, python, Java, and ruby example apps, right? -- Jack Krupansky -Original Message- From: Iwan Hanjoyo Sent: Monday, December 03, 2012 8:28 PM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI Note that Velocity _can_ be used for user-facing code, but be very sure you secure your Solr. If you allow direct access, a user can easily enter something like http:// solr/update?commit=truestream.body=deletequery*:*/query/delete. And all your documents will be gone. Hi Erickson, Thank you for the input. I'll notice and filter out this url. * http:// solr/update?commit=truestream.body=deletequery*:*/query/delete Kind regards, Hanjoyo
Re: How to change Solr UI
let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 5:23 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI It's a shame wt=velocity gets a bad rap because /update isn't out of the box strict with the HTTP/RESTful scene. A delete should be a DELETE of some sort. There are 3rd party standalone apps. There was even a standalone ruby app (flare) that was once upon a time in Solr's svn, but really the Solr committers can't be expected to maintain all those various examples and keep them up to date and working, so best to keep them 3rd party IMO. We've got Blacklight, VuFind, and all sorts of other front-ends out there with their own vibrant communities. I'm -1 for removing VW (it's contrib plugin as it is already, just like /update/extract). /browse certainly could use a cleaning up / revamping, but it's good stuff if I do say so myself and very handy to have available for several reasons*. Let's try not to conflate wt=velocity with /update being more easily dangerous than it probably should be. But let's also be clear always that Solr is meant to be behind the firewall as it's primary and default place in the world. Erik * One I'll share: There is a real-world use case of a (relatively big) company using wt=velocity to generate e-mail (for saved searches) texts very conveniently in a backend environment and very high speed, no other technologies/complexities needed in the mix but Solr and a little custom templating. On Dec 3, 2012, at 20:58 , Jack Krupansky wrote: It is annoying to have to repeat these explanations so much. Any serious objection to removing the VW UI from Solr proper and replacing it with a standalone app? I mean, Solr should have PHP, python, Java, and ruby example apps, right? -- Jack Krupansky -Original Message- From: Iwan Hanjoyo Sent: Monday, December 03, 2012 8:28 PM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI Note that Velocity _can_ be used for user-facing code, but be very sure you secure your Solr. If you allow direct access, a user can easily enter something like http:// solr/update?commit=truestream.body=deletequery*:*/query/delete. And all your documents will be gone. Hi Erickson, Thank you for the input. I'll notice and filter out this url. * http:// solr/update?commit=truestream.body=deletequery*:*/query/delete Kind regards, Hanjoyo
Re: How to change Solr UI
On Dec 4, 2012, at 08:21 , Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. Point taken about being clear about this. But I disagree about removing /browse. It's useful, even if misunderstood/abused by some. If there are spots where we need to be clearer about what it is that is being rendered, how it's rendered, and the pros/cons to it, then let's see about getting it mentioned more clearly. But do keep in mind that something like this example: having Solr return suggestion lists as plain text suitable for suggest interfaces rather than having it return JSON or XML and having a middle tier process it when all you need is a plain list or some CSV. It's quite fine and sensible to use wt=velocity behind the firewall too, even /browse as-is. Same as with the XSL transformation writing capability. Erik
Re: How to change Solr UI
I have been mulling on this. The browse UI is getting a little out of date, and has interesting 'features' such as only showing a map for a document if the document has a 'name' field, which makes no real sense at all. Apart from renovating the UI of browse, or possibly replacing it with something more modern based upon the new admin UI technology, it would make sense to add a 'disclaimer' somewhere prominent on the browse interface - title it 'Solr Demo' or 'Solr Prototype', and add a link to a wiki page that explains *why* you shouldn't use this in production. Apart from the security issues already mentioned there's the MVC side - you have a model and a view, but no controller, thus it becomes hard to build anything useful very quickly. I'd happily hack disclaimers into place if considered useful. Upayavira On Tue, Dec 4, 2012, at 01:21 PM, Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 5:23 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI It's a shame wt=velocity gets a bad rap because /update isn't out of the box strict with the HTTP/RESTful scene. A delete should be a DELETE of some sort. There are 3rd party standalone apps. There was even a standalone ruby app (flare) that was once upon a time in Solr's svn, but really the Solr committers can't be expected to maintain all those various examples and keep them up to date and working, so best to keep them 3rd party IMO. We've got Blacklight, VuFind, and all sorts of other front-ends out there with their own vibrant communities. I'm -1 for removing VW (it's contrib plugin as it is already, just like /update/extract). /browse certainly could use a cleaning up / revamping, but it's good stuff if I do say so myself and very handy to have available for several reasons*. Let's try not to conflate wt=velocity with /update being more easily dangerous than it probably should be. But let's also be clear always that Solr is meant to be behind the firewall as it's primary and default place in the world. Erik * One I'll share: There is a real-world use case of a (relatively big) company using wt=velocity to generate e-mail (for saved searches) texts very conveniently in a backend environment and very high speed, no other technologies/complexities needed in the mix but Solr and a little custom templating. On Dec 3, 2012, at 20:58 , Jack Krupansky wrote: It is annoying to have to repeat these explanations so much. Any serious objection to removing the VW UI from Solr proper and replacing it with a standalone app? I mean, Solr should have PHP, python, Java, and ruby example apps, right? -- Jack Krupansky -Original Message- From: Iwan Hanjoyo Sent: Monday, December 03, 2012 8:28 PM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI Note that Velocity _can_ be used for user-facing code, but be very sure you secure your Solr. If you allow direct access, a user can easily enter something like http:// solr/update?commit=truestream.body=deletequery*:*/query/delete. And all your documents will be gone. Hi Erickson, Thank you for the input. I'll notice and filter out this url. * http:// solr/update?commit=truestream.body=deletequery*:*/query/delete Kind regards, Hanjoyo
Re: How to change Solr UI
Or, maybe integrate /browse with the Solr Admin UI and give it a graphic treatment that screams that it is a development tool and not designed to be a model for an app UI. And, I still think it would be good to include SOME example of a prototype app UI with Solr, to drive home the point of here is [an example of] how you need to separate UI from Solr. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 9:29 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI On Dec 4, 2012, at 08:21 , Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. Point taken about being clear about this. But I disagree about removing /browse. It's useful, even if misunderstood/abused by some. If there are spots where we need to be clearer about what it is that is being rendered, how it's rendered, and the pros/cons to it, then let's see about getting it mentioned more clearly. But do keep in mind that something like this example: having Solr return suggestion lists as plain text suitable for suggest interfaces rather than having it return JSON or XML and having a middle tier process it when all you need is a plain list or some CSV. It's quite fine and sensible to use wt=velocity behind the firewall too, even /browse as-is. Same as with the XSL transformation writing capability. Erik=
Re: How to change Solr UI
That's an interesting take. I agree that Solr needs *something* for folks to use. It is unfortunate that Solr actually has a functioning HTTP infrastructure, because it then makes less sense to build an alternative one up. E.g. How about: http://localhost:8983/solr - admin UI http://localhost:8983/browse - separate browse webapp It would be a separate app that runs as another wepapp, accessing Solr via HTTP just as any other app would. It could still use Velocity, but would demonstrate that you shouldn't integrate your app with Solr. A minimal dependency app for demonstration purposes only. Upayavira On Tue, Dec 4, 2012, at 02:37 PM, Jack Krupansky wrote: Or, maybe integrate /browse with the Solr Admin UI and give it a graphic treatment that screams that it is a development tool and not designed to be a model for an app UI. And, I still think it would be good to include SOME example of a prototype app UI with Solr, to drive home the point of here is [an example of] how you need to separate UI from Solr. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 9:29 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI On Dec 4, 2012, at 08:21 , Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. Point taken about being clear about this. But I disagree about removing /browse. It's useful, even if misunderstood/abused by some. If there are spots where we need to be clearer about what it is that is being rendered, how it's rendered, and the pros/cons to it, then let's see about getting it mentioned more clearly. But do keep in mind that something like this example: having Solr return suggestion lists as plain text suitable for suggest interfaces rather than having it return JSON or XML and having a middle tier process it when all you need is a plain list or some CSV. It's quite fine and sensible to use wt=velocity behind the firewall too, even /browse as-is. Same as with the XSL transformation writing capability. Erik=
Re: How to change Solr UI
And basically that's what i had in mind with Prism here: https://github.com/lucidimagination/Prism Prism's very lightweight, uses Velocity (or not, any Ruby templating technology available), and is entirely separate from Solr. Before that there was Flare: https://github.com/erikhatcher/solr-ruby-flare/tree/master/flare.Prism is the approach I'd (obviously) take these days, and it's getting some more attention, it looks like, soon. Blacklight and VuFind are much more richly capable. So there's options already out there, and surely many others that I don't even mention. A new top-level wiki page seems warranted from this discussion from http://wiki.apache.org/solr/FrontPage to list off all the various front-ends available. Erik On Dec 4, 2012, at 12:11 , Upayavira wrote: That's an interesting take. I agree that Solr needs *something* for folks to use. It is unfortunate that Solr actually has a functioning HTTP infrastructure, because it then makes less sense to build an alternative one up. E.g. How about: http://localhost:8983/solr - admin UI http://localhost:8983/browse - separate browse webapp It would be a separate app that runs as another wepapp, accessing Solr via HTTP just as any other app would. It could still use Velocity, but would demonstrate that you shouldn't integrate your app with Solr. A minimal dependency app for demonstration purposes only. Upayavira On Tue, Dec 4, 2012, at 02:37 PM, Jack Krupansky wrote: Or, maybe integrate /browse with the Solr Admin UI and give it a graphic treatment that screams that it is a development tool and not designed to be a model for an app UI. And, I still think it would be good to include SOME example of a prototype app UI with Solr, to drive home the point of here is [an example of] how you need to separate UI from Solr. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 9:29 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI On Dec 4, 2012, at 08:21 , Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. Point taken about being clear about this. But I disagree about removing /browse. It's useful, even if misunderstood/abused by some. If there are spots where we need to be clearer about what it is that is being rendered, how it's rendered, and the pros/cons to it, then let's see about getting it mentioned more clearly. But do keep in mind that something like this example: having Solr return suggestion lists as plain text suitable for suggest interfaces rather than having it return JSON or XML and having a middle tier process it when all you need is a plain list or some CSV. It's quite fine and sensible to use wt=velocity behind the firewall too, even /browse as-is. Same as with the XSL transformation writing capability. Erik=
Re: How to change Solr UI
But there's value in having something packaged within Solr itself, for demo purposes. That would I suspect make it Java (like it or not!) And that would probably not make it very state-of-the art, unless it used jquery, with a very lightweight java portion, which would be possible. Upayavira On Tue, Dec 4, 2012, at 05:42 PM, Erik Hatcher wrote: And basically that's what i had in mind with Prism here: https://github.com/lucidimagination/Prism Prism's very lightweight, uses Velocity (or not, any Ruby templating technology available), and is entirely separate from Solr. Before that there was Flare: https://github.com/erikhatcher/solr-ruby-flare/tree/master/flare. Prism is the approach I'd (obviously) take these days, and it's getting some more attention, it looks like, soon. Blacklight and VuFind are much more richly capable. So there's options already out there, and surely many others that I don't even mention. A new top-level wiki page seems warranted from this discussion from http://wiki.apache.org/solr/FrontPage to list off all the various front-ends available. Erik On Dec 4, 2012, at 12:11 , Upayavira wrote: That's an interesting take. I agree that Solr needs *something* for folks to use. It is unfortunate that Solr actually has a functioning HTTP infrastructure, because it then makes less sense to build an alternative one up. E.g. How about: http://localhost:8983/solr - admin UI http://localhost:8983/browse - separate browse webapp It would be a separate app that runs as another wepapp, accessing Solr via HTTP just as any other app would. It could still use Velocity, but would demonstrate that you shouldn't integrate your app with Solr. A minimal dependency app for demonstration purposes only. Upayavira On Tue, Dec 4, 2012, at 02:37 PM, Jack Krupansky wrote: Or, maybe integrate /browse with the Solr Admin UI and give it a graphic treatment that screams that it is a development tool and not designed to be a model for an app UI. And, I still think it would be good to include SOME example of a prototype app UI with Solr, to drive home the point of here is [an example of] how you need to separate UI from Solr. -- Jack Krupansky -Original Message- From: Erik Hatcher Sent: Tuesday, December 04, 2012 9:29 AM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI On Dec 4, 2012, at 08:21 , Jack Krupansky wrote: let's also be clear always that Solr is meant to be behind the firewall Absolutely, but we are NOT doing that when we provide the Velocity-based /browse UI. Erik, your email example sounds reasonable, so if you want to substitute something like that for the /browse handler, fine. As you point out, it is not Velocity per se, but the /browse UI that results in a lack of clarity about Solr being meant to be behind the firewall. Point taken about being clear about this. But I disagree about removing /browse. It's useful, even if misunderstood/abused by some. If there are spots where we need to be clearer about what it is that is being rendered, how it's rendered, and the pros/cons to it, then let's see about getting it mentioned more clearly. But do keep in mind that something like this example: having Solr return suggestion lists as plain text suitable for suggest interfaces rather than having it return JSON or XML and having a middle tier process it when all you need is a plain list or some CSV. It's quite fine and sensible to use wt=velocity behind the firewall too, even /browse as-is. Same as with the XSL transformation writing capability. Erik=
How to change Solr UI
Hi, I want to change the Solr UI. As far as i understand, Solritas is just for prototyping, where I can change the UI according to a predefined template (Velocity) and cannot add on any additional functionality to that page. How can I change the Solr UI otherwise. Any guidance would be appreciated. Thanks and regards, Romita
Re: How to change Solr UI
Hi Romita, In my opinion, if you are new to Solr, you can start learning from Solritas. Solritas uses Apache Velocity, a templating language, CSS and JQuery to manage it looks and behavior. Besides that you can write a custom SearchComponent inside the /browse SearchHandler to add more functionality to your search application. Kind regards, Hanjoyo On Mon, Dec 3, 2012 at 4:35 PM, Romita Saha romita.s...@sg.panasonic.comwrote: Hi, I want to change the Solr UI. As far as i understand, Solritas is just for prototyping, where I can change the UI according to a predefined template (Velocity) and cannot add on any additional functionality to that page. How can I change the Solr UI otherwise. Any guidance would be appreciated. Thanks and regards, Romita
Re: How to change Solr UI
Adding to what Iwan said, I want to be sure you're not confusing prototyping with a full-fledged application. The Velocity code included is mostly intended as a rapid-prototyping vehicle. There are significant security issues if you try to use it as your user-facing application, be sure you trust your users if you go down this route. But to change it, see the Apache velocity project, and the code in solr home/conf/velocity. Note that Velocity _can_ be used for user-facing code, but be very sure you secure your Solr. If you allow direct access, a user can easily enter something like http://solr/update?commit=truestream.body=deletequery*:*/query/delete. And all your documents will be gone. Most installations use a middle layer between Solr and the user that controls access. Best Erick On Mon, Dec 3, 2012 at 5:01 AM, Iwan Hanjoyo ihanj...@gmail.com wrote: Hi Romita, In my opinion, if you are new to Solr, you can start learning from Solritas. Solritas uses Apache Velocity, a templating language, CSS and JQuery to manage it looks and behavior. Besides that you can write a custom SearchComponent inside the /browse SearchHandler to add more functionality to your search application. Kind regards, Hanjoyo On Mon, Dec 3, 2012 at 4:35 PM, Romita Saha romita.s...@sg.panasonic.com wrote: Hi, I want to change the Solr UI. As far as i understand, Solritas is just for prototyping, where I can change the UI according to a predefined template (Velocity) and cannot add on any additional functionality to that page. How can I change the Solr UI otherwise. Any guidance would be appreciated. Thanks and regards, Romita
Re: How to change Solr UI
Note that Velocity _can_ be used for user-facing code, but be very sure you secure your Solr. If you allow direct access, a user can easily enter something like http:// solr/update?commit=truestream.body=deletequery*:*/query/delete. And all your documents will be gone. Hi Erickson, Thank you for the input. I'll notice and filter out this url. * http:// solr/update?commit=truestream.body=deletequery*:*/query/delete Kind regards, Hanjoyo
Re: How to change Solr UI
It is annoying to have to repeat these explanations so much. Any serious objection to removing the VW UI from Solr proper and replacing it with a standalone app? I mean, Solr should have PHP, python, Java, and ruby example apps, right? -- Jack Krupansky -Original Message- From: Iwan Hanjoyo Sent: Monday, December 03, 2012 8:28 PM To: solr-user@lucene.apache.org Subject: Re: How to change Solr UI Note that Velocity _can_ be used for user-facing code, but be very sure you secure your Solr. If you allow direct access, a user can easily enter something like http:// solr/update?commit=truestream.body=deletequery*:*/query/delete. And all your documents will be gone. Hi Erickson, Thank you for the input. I'll notice and filter out this url. * http:// solr/update?commit=truestream.body=deletequery*:*/query/delete Kind regards, Hanjoyo
Re: How to change Solr UI
That's only one example, there are others, stream.body=deleteidblah/id/delete. or deletequeryid:*/query/delete Jack's comment is well taken, consider a real middleware application. Best Erick On Mon, Dec 3, 2012 at 5:28 PM, Iwan Hanjoyo ihanj...@gmail.com wrote: Note that Velocity _can_ be used for user-facing code, but be very sure you secure your Solr. If you allow direct access, a user can easily enter something like http:// solr/update?commit=truestream.body=deletequery*:*/query/delete. And all your documents will be gone. Hi Erickson, Thank you for the input. I'll notice and filter out this url. * http:// solr/update?commit=truestream.body=deletequery*:*/query/delete Kind regards, Hanjoyo
Solr UI for File Search
Hello, I'm almost done with my file (rich document) searching system for server and client side. Now I have to do is configure search result interface so that it displays result properly and attach a link to the searched files. (It just shows xml result now) I cannot simply use other application because I added my own file parsers on Tika. So what would be my best option in order to add nice UI to my system without messing with it? Thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-UI-for-File-Search-tp4015476.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr UI
Hi Erik, Re this project, do you have any demos available to check it out? https://github.com/lucidimagination/Prism And will it work on standard solr installs or do you need a Lucid imagination subscription. Thanks -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-UI-tp3182594p3925211.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr UI
On Tue, Jul 19, 2011 at 7:51 PM, Erik Hatcher erik.hatc...@gmail.com wrote: There's several starting points for Solr UI out there, but really the best choice is whatever fits your environment and the skills/resources you have handy. Here's a few off the top of my head - [...] Besides these excellent examples, if you are looking at Python/Django, Haystack works well as a starting point, though: * One does have to build a template/view architecture around it, that is fairly easy to do. * Haystack allows multiple search back-ends, and while that is convenient for starting out, it does not implement some Solr features. E.g., one big missing item is support for multi-core Solr. Regards, Gora
Solr UI
Hi, I installed Solr 3.2 and able to search results successfully from the crawled data, however , I would like to develop UI for the http or json response. Can anyone guide me with the tutorial or sample ? I referred few thing like Ajax Solr but am not sure how to do the things. Serenity -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-UI-tp3182594p3182594.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr UI
There's several starting points for Solr UI out there, but really the best choice is whatever fits your environment and the skills/resources you have handy. Here's a few off the top of my head - * Blacklight - it's a Ruby on Rails full-featured search UI powered by Solr. It can be customized fairly easily to work with any arbitrary Solr schema, but by default it is kinda library-specific in it's out of the box experience. It powers UVa, Stanford, and other libraries and sites out there in production now - http://projectblacklight.org/ * Flare - it's the first prototype to Blacklight, and fairly dusty and prototypical, but I still think a good example of how lean a search UI can be that has a number of fancy features - http://wiki.apache.org/solr/Flare/HowTo * Solritas/VelocityResponseWriter - this is built right into Solr and allows easily templating of Solr responses. It's the /browse interface out of the box. While probably not how someone would deploy a production search UI, it can make proof of concepts and getting up and running quite quick and easy - http://wiki.apache.org/solr/VelocityResponseWriter And there's a new little tinkering I've started a while back that might be good food for thought for the same sorts of ideas as the above but in a slightly different direction - https://github.com/lucidimagination/Prism Erik On Jul 19, 2011, at 10:00 , serenity wrote: Hi, I installed Solr 3.2 and able to search results successfully from the crawled data, however , I would like to develop UI for the http or json response. Can anyone guide me with the tutorial or sample ? I referred few thing like Ajax Solr but am not sure how to do the things. Serenity -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-UI-tp3182594p3182594.html Sent from the Solr - User mailing list archive at Nabble.com.
Open source Solr UI with multiple select faceting?
Hi, Any open source Solr UI's that support selecting multiple facet values (OR faceting)? For example allowing a user to select red or blue for the facet field Color. I'd prefer libraries in javascript or Python. I know about ajax-solr but it doesn't seem to support multiple selects. Thanks.
Re: Open source Solr UI with multiple select faceting?
SolrNet has a great example application that you can use...There is a great Javascript project called SolrAjax but I don't know what the state of it is. Adam On Thu, Dec 9, 2010 at 4:53 PM, Andy angelf...@yahoo.com wrote: Hi, Any open source Solr UI's that support selecting multiple facet values (OR faceting)? For example allowing a user to select red or blue for the facet field Color. I'd prefer libraries in javascript or Python. I know about ajax-solr but it doesn't seem to support multiple selects. Thanks.
