You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Yonik Seeley <yo...@apache.org> on 2008/06/01 16:30:57 UTC
Re: new user: some questions about parameters and query syntax
On Sat, May 31, 2008 at 1:03 AM, Chris Hostetter
<ho...@fucit.org> 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 separately.
Some of these things feel like trade offs in ease of readability &
manually typing of URLs vs ease of programmatic manipulation.
-Yonik
Re: new user: some questions about parameters and query syntax
Posted by Chris Hostetter <ho...@fucit.org>.
: 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 manipulation ... it's
ease of readability and manual typing vs a need for external mapping of
internal field names to external field labels. even the simplest use
cases of Solr almost allways need some external mapping from field labels
they display to end users and field names that are used in the schema ...
it would be really nice if that wasn't actually neccessary.
just making fl a multivalued field wouldn't get you far enough obviously,
you'd also need some aliasing mechanism to deal with field names
for sorting vs field names for quering, and in many cases you have to
worry about whether your field names contain characters the
standard QueryParser considers special (like whitespace) but it would
certainly be nice to say...
q=*:*&fl=Product+Id&fl=Product+Name&fl=Sales+Price
-Hoss