[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2009-08-06 Thread Avlesh Singh (JIRA)

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

Avlesh Singh commented on SOLR-247:
---

I haven't tested this patch yet.  But my belief is that the primary objective 
should be to support dynamic fields than pure wildcard field names. Dynamic 
fields offer wide range of capabilities with w.r.t key-value(s) kind of data. 
Most of the times people use such fields because the keys are not known upfront.

If nothing more, this patch should at least cater to that audience.

> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch, SOLR-247.patch, 
> SOLR-247.patch, SOLR-247.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2009-01-09 Thread Lars Kotthoff (JIRA)

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

Lars Kotthoff commented on SOLR-247:


Off the top of my head, having an automated feed parser which adds fields and 
facet_field to facet on. I agree that all this should be part of a global 
glob-like thing, but that would probably only apply to the part which parses 
the parameters anyway. How a glob is matched depends on the type of glob (i.e. 
whether the field is indexed/stored/... and we want to facet/highlight/...).

If people start using it and it turns out to be important, it can always be 
refactored into something more general. If nobody uses globbing, there'd be no 
need to invest the effort of making it general :)

> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch, SOLR-247.patch, 
> SOLR-247.patch, SOLR-247.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2009-01-09 Thread Shalin Shekhar Mangar (JIRA)

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

Shalin Shekhar Mangar commented on SOLR-247:


Lars, I see you have been updating the patches to trunk diligently. However, 
I'm not sure if there is a consensus on adding this without having a glob like 
feature in place.

Do you have a use-case in mind which can be solved only with the current patch?

> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch, SOLR-247.patch, 
> SOLR-247.patch, SOLR-247.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2008-01-10 Thread Hoss Man (JIRA)

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

Hoss Man commented on SOLR-247:
---

i've put soem thoughts on the broader issues of having solr admin control over 
how field names are dealt with (globs, regexes, aliasing, etc...)  in various 
contexts on the wiki...

http://wiki.apache.org/solr/FieldAliasesAndGlobsInParams

...it might be best to use that as a whiteboard for a design discussion since 
the ultimate issues are a little bigger then this issue originally set out to 
tackle.

> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2008-01-10 Thread Matthew Runo (JIRA)

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

Matthew Runo commented on SOLR-247:
---

http://www.nabble.com/Dynamic-fields---Facets-to14739422.html

also provides a use case for this to be fixed. While I'd never do a "*", I'd 
love to be able to do a "attribute_*". It just makes using the dynamic fields 
so much easier. 

> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-08-23 Thread Pieter Berkel (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522345
 ] 

Pieter Berkel commented on SOLR-247:


Some recent discussion on this topic:

http://www.nabble.com/Structured-Lucene-documents-tf4234661.html

I get the impression that general wildcard syntax support for field listing 
parameters (i.e. the reverse of dynamic fields) as described in the above 
thread would be far more useful than a simple '*' match-anything syntax (not 
only in faceting but other cases like hl.fl and perhaps even mlt.fl).

I haven't really considered the performance issues of this approach however, as 
it would involve checking each field supplied in the parameter for '*' before 
expanding it into full field names for every query.

Given the above, the fact that it could be used across multiple response 
handlers and subhandlers like SimpleFacets & Highlighting, and that it would 
require access to IndexReader to getFieldNames(), where might be the most 
sensible place to put this code?


> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-24 Thread Hoss Man (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498761
 ] 

Hoss Man commented on SOLR-247:
---

see some follow up comments in the mailing lists...

http://www.nabble.com/forum/Search.jtp?forum=14479&local=y&query=SOLR-247

in a nut shell, i think this issue *can* be resolved won't fix ... but i'm not 
opposed to leaving open if someone wants to work on it.  there are ways for 
people to configure solr so that all the fields they want to facet on are 
faceted on by defualt (when configuring the requestHanlder) which is safer then 
wild carding.

> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



RE: [jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-24 Thread Chris Hostetter

: Also, the reason other engines require you to mark the fields in the
: index definition is because they actually index the data differently if
: it is a facet vs a normal indexed field.  It's cool that solr doesn't
: have to do this but there may be a case where it would be a good idea
: someday.

right ... if down the road we find a way to imrpvoe faceting (or any other
feature) by storing more data on disk at indexing time, then configuration
to tell you that data was there and how to use it would live in the
schema.xml -- but options that don't matter once the data is already
written (or can be differet for differnet people depending on how they
use the data) can/should live in solrconfig.xml (like the options in
mainIndex right now)

Alternately: if kwe add some custom "facet caching" that doens't require
any new data on disk, but builds new in memory structures, that should
live in the solrconfig.xml as well since it's the kind of thing that would
likely be configured idfferently for masters/slaves.


-Hoss



RE: [jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-23 Thread Will Johnson
Good point, I was proposing it as an alternative to myfield_facet since
that seems to overload the field name a bit too much.  I agree that
solrconfig + specialized request handlers are a much better location for
that kind of stuff.  

Also, the reason other engines require you to mark the fields in the
index definition is because they actually index the data differently if
it is a facet vs a normal indexed field.  It's cool that solr doesn't
have to do this but there may be a case where it would be a good idea
someday. 

- will

-Original Message-
From: Chris Hostetter [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 23, 2007 6:34 PM
To: Solr Dev
Subject: RE: [jira] Commented: (SOLR-247) Allow facet.field=* to facet
on all fields (without knowing what they are)


: What about adding an optional parameter to the field definition in the
: IndexSchema for defaultFacet="true/false".  This would make solr's

information should go in schema.xml if the are inherient to the data
and the physical index.  Things should go in the solrconfig.xml if they
relate to how the index is used -- a master might have a differnet
solrconfig then a slave because it doesn't get used for queries, while
two
diffenret slaves might have differnet solrconfigs because they get used
by
different sets of clients and need differnet cache configs or request
handler configs -- but all three would use the same schema.xml because
the
physical index is the same in all cases.

a mechanism already exists to say "by default, i want clients to get
facets on certian fields" in teh solrconfig.xml, it's just a default
param
for hte requestHandler ...

  

 
   category
   author
   type
   ...

...then the params are defaulted for everyone, and the only thingthe
user
needs in the URL is "facet=true" ... or that can be defaulted as well.


-Hoss



RE: [jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-23 Thread Chris Hostetter

: What about adding an optional parameter to the field definition in the
: IndexSchema for defaultFacet="true/false".  This would make solr's

information should go in schema.xml if the are inherient to the data
and the physical index.  Things should go in the solrconfig.xml if they
relate to how the index is used -- a master might have a differnet
solrconfig then a slave because it doesn't get used for queries, while two
diffenret slaves might have differnet solrconfigs because they get used by
different sets of clients and need differnet cache configs or request
handler configs -- but all three would use the same schema.xml because the
physical index is the same in all cases.

a mechanism already exists to say "by default, i want clients to get
facets on certian fields" in teh solrconfig.xml, it's just a default param
for hte requestHandler ...

  

 
   category
   author
   type
   ...

...then the params are defaulted for everyone, and the only thingthe user
needs in the URL is "facet=true" ... or that can be defaulted as well.


-Hoss



RE: [jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-23 Thread Will Johnson
What about adding an optional parameter to the field definition in the
IndexSchema for defaultFacet="true/false".  This would make solr's
functionality/configuration similar with many of the major search engine
vendors and keep people from having to follow naming conventions for
fields.  Then facet.field=* just turns on those fields with
defaultFacet="true" but still lets you facet on others if you deem
necessary.  If there were a list of default facet fields it might also
let the index warming process pre-cache the results of those filter
queries which would be a nice side benefit.

The *_facet thing scares me because I'm afraid I'll eventually be
'forced' to have field names like:

myfield_facet_vector_stem_morelikethis_highlight.

- will

-Original Message-
From: Ryan McKinley (JIRA) [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 23, 2007 3:38 PM
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-247) Allow facet.field=* to facet on
all fields (without knowing what they are)


[
https://issues.apache.org/jira/browse/SOLR-247?page=com.atlassian.jira.p
lugin.system.issuetabpanels:comment-tabpanel#action_12498338 ] 

Ryan McKinley commented on SOLR-247:


> 
> There are *lots* of reasons why a field might be indexed though, so
faceting on every indexed field doesn't seem like it would ever make
sense.
> 

agreed, but *_facet would be useful

> 
> if we do this, i would think it only makes sense to generalize the use
of "*" in both fl and facet.field into a true glob style syntax

One issue is that fl=XXX is typically a field list separated with "," or
"|", facet.field expects each field as a separate parameter.




> Allow facet.field=* to facet on all fields (without knowing what they
are)
>

--
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a
bad idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top
term collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-23 Thread Chris Hostetter

: One issue is that fl=XXX is typically a field list separated with "," or
: "|", facet.field expects each field as a separate parameter.

personally, i've never really lke that splitting behavior of fl, i'd
really rather not add it to facet.field.


-Hoss



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-23 Thread Ryan McKinley (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498338
 ] 

Ryan McKinley commented on SOLR-247:


> 
> There are *lots* of reasons why a field might be indexed though, so faceting 
> on every indexed field doesn't seem like it would ever make sense.
> 

agreed, but *_facet would be useful

> 
> if we do this, i would think it only makes sense to generalize the use of "*" 
> in both fl and facet.field into a true glob style syntax

One issue is that fl=XXX is typically a field list separated with "," or "|", 
facet.field expects each field as a separate parameter.




> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-23 Thread Hoss Man (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498336
 ] 

Hoss Man commented on SOLR-247:
---

I have a really hard time imagining anything but the most trivial use cases for 
facet.field=* ... it doesn't really sime like a problem in need of a solution.

with somehting like fl=*, we're only talking about stored fields ... storing a 
field makes no sense unless you plan on returning it in the field list some of 
the time, so fl=* makes sense as a "return all of hte fields that are possible 
to return" option.

There are *lots* of reasons why a field might be indexed though, so faceting on 
every indexed field doesn't seem like it would ever make sense.

in my opinion a "best practice" is not to use fl=* unless you are debugging 
anyway, otherwise you find yourself getting slammed with large amounts of data 
you don't want as the index evolves over time ... something like facet.field=* 
would be worse because it's not just the amount of data getting returned that 
would increase, but the amount of computation (and time and poor cache 
performance) that would spike as well.

if we do this, i would think it only makes sense to generalize the use of "*" 
in both fl and facet.field into a true glob style syntax, so we can at least 
encourage people who want this type of syntax to use a naming convention to 
help limit how much they hurt themselves.

(i have no problem giving people enough rope to hang themselves, but we 
shouldn't tie a noose in the rope before we give it to them)

 

> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are)

2007-05-23 Thread Erik Hatcher (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498311
 ] 

Erik Hatcher commented on SOLR-247:
---

I can see value in supporting the dynamicField wildcard syntax, so *_facet 
would work.   In fact, maybe that'd be a good syntax to support for all fl-like 
parameters too. 

* scares me, and it'd certainly be discouraged for anything but small indexes!  
 But of course I don't have to use it.   :) 

> Allow facet.field=* to facet on all fields (without knowing what they are)
> --
>
> Key: SOLR-247
> URL: https://issues.apache.org/jira/browse/SOLR-247
> Project: Solr
>  Issue Type: Improvement
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-247-FacetAllFields.patch
>
>
> I don't know if this is a good idea to include -- it is potentially a bad 
> idea to use it, but that can be ok.
> This came out of trying to use faceting for the LukeRequestHandler top term 
> collecting.
> http://www.nabble.com/Luke-request-handler-issue-tf3762155.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.