> we can start having more explict structured info
> about all of the concepts that are really "core" to how a param works (ie:
> name, datatype, is it multivalued, can it be overridden per field, what
> is/are the value(s) used for).
defaults as well, please
Structured information per param
: that for a newbie, there is a certain confusion when it comes to "one
: thing with comma a separated list, the other can have multiple
: values". This could also be solved perfectly in the wiki (i.e. making
: it very clear multiple GET params with the same name can be used, or
: if a comma-separ
: I dunno... for something like "fl", it still seems a bit verbose to
: list every field separately.
: Some of these things feel like trade offs in ease of readability &
: manually typing of URLs vs ease of programmatic manipulation.
I don't even think the primary issue is programmatic manipulat
On Sat, May 31, 2008 at 7:03 AM, Chris Hostetter
<[EMAIL PROTECTED]> wrote:
>
> : For date faceting, count missing the order doesn't matter either, and
> : there it's given as a comma-separated list.
>
> Either you are mistaken, or i don't understand your statement. date
> faceting works just like
On Sat, May 31, 2008 at 1:03 AM, Chris Hostetter
<[EMAIL PROTECTED]> wrote:
> The only reason *any* existing solr params use comma or white space
> seperated lists is because way, way, WAY back in the day [...]
I dunno... for something like "fl", it still seems a bit verbose to
list every field s
: For date faceting, count missing the order doesn't matter either, and
: there it's given as a comma-separated list.
Either you are mistaken, or i don't understand your statement. date
faceting works just like field faceting -- no comma seperated lists.
: I think it makes sense doing everythi
On 29-May-08, at 11:22 AM, Bram de Jong wrote:
On Thu, May 29, 2008 at 6:40 PM, Otis Gospodnetic
<[EMAIL PROTECTED]> wrote:
I haven't been paying close attention to the uniformity of URL
parameters, but if there is room for making them more uniform
(e.g. always use singular, always use comma
On May 30, 2008, at 2:40 AM, Otis Gospodnetic wrote:
Right, the only actively developed Solr client is really Solrj.
All other ones are not well maintained - I don't recall seeing any
patches for any of them in the recent months
Ummm solr-ruby! It doesn't need any patches ;) It's u
:09 PM
> Subject: Re: new user: some questions about parameters and query syntax
>
> On Thu, May 29, 2008 at 6:40 PM, Otis Gospodnetic
> wrote:
> > I haven't been paying close attention to the uniformity of URL parameters,
> > but
> if there is room for making th
On Thu, May 29, 2008 at 6:40 PM, Otis Gospodnetic
<[EMAIL PROTECTED]> wrote:
> I haven't been paying close attention to the uniformity of URL parameters,
> but if there is room for making them more uniform
> (e.g. always use singular, always use comma as a delimiting character, etc.)
> without hu
riginal Message
> From: Bram de Jong <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Thursday, May 29, 2008 5:38:50 AM
> Subject: Re: new user: some questions about parameters and query syntax
>
> Hello Eric (and others)
>
> >>
> >>
Hello Eric (and others)
>>
>> repeating the parameter:
>> sort=field1,field2 desc,field3
>> but
>> facet.field=field1&facet.field=field2
>> This is pretty confusing to first-hand users! :-)
>
> Yeah, it is confusing. But we have to be careful with order. I don't
> believe you can rely on the or
On May 28, 2008, at 10:41 AM, Bram de Jong wrote:
a new user here. I will be using solr to power the search over at
freesound ( http://freesound.iua.upf.edu ).
Welcome! Cool use of Solr too.
1. I have a minor remark about the inconsistencies in the
query-parameter definitions... Sometimes m
hello all,
a new user here. I will be using solr to power the search over at
freesound ( http://freesound.iua.upf.edu ).
been experimenting with solr and it's damned cool :)
here we go:
1. I have a minor remark about the inconsistencies in the
query-parameter definitions... Sometimes multiple
14 matches
Mail list logo
