is there a JIRA ticket for this?
+1 to Robert's observation that this independent from any format discussion
On Wed, Nov 14, 2012 at 5:46 AM, Robert Muir rcm...@gmail.com wrote:
On Tue, Nov 13, 2012 at 11:41 PM, Toke Eskildsen t...@statsbiblioteket.dk
wrote:
On Tue, 2012-11-13 at 19:50
On Tue, Dec 18, 2012 at 8:06 PM, Ryan McKinley ryan...@gmail.com wrote:
is there a JIRA ticket for this?
+1 to Robert's observation that this independent from any format discussion
I dont know of one: but feel free!
I thought of the stats situation at some point:
terms.size ==
On Wed, 2012-11-14 at 14:46 +0100, Robert Muir wrote:
On Tue, Nov 13, 2012 at 11:41 PM, Toke Eskildsen t...@statsbiblioteket.dk
wrote:
Dynamically changing response formats sounds horrible.
I don't understand how this is related with my proposal to
automatically use a different data
On Wed, Nov 14, 2012 at 8:41 AM, Toke Eskildsen t...@statsbiblioteket.dk
wrote:
Dynamically changing response formats sounds horrible.
It depends if you consider it a change of format. A single value
would always be presented as a single value, while multiple values
would always be represented
On Tue, Nov 13, 2012 at 11:41 PM, Toke Eskildsen t...@statsbiblioteket.dk
wrote:
On Tue, 2012-11-13 at 19:50 +0100, Yonik Seeley wrote:
The original version of Solr (SOLAR when it was still inside CNET) did
this - a multiValued field with a single value was output as a singe
value, not an
The optimization I am talking about is safe and simple and no user
would have any idea.
+1
the end format should be a different issue -- under the hood, multivalued
fields should perform well if they are actually single valued.
If the only motivation for adding 'multiValued=flexible' is the response
format, what about just changing the response format version number and
writing the wrapping list based on that?
Allowing multiple values, but behaving like single value fields when only
one value exists would be a *huge*
On Tue, Nov 13, 2012 at 6:37 PM, Ryan McKinley ryan...@gmail.com wrote:
If the only motivation for adding 'multiValued=flexible' is the response
format, what about just changing the response format version number and
writing the wrapping list based on that?
The original version of Solr (SOLAR
On Tue, 2012-11-13 at 19:50 +0100, Yonik Seeley wrote:
The original version of Solr (SOLAR when it was still inside CNET) did
this - a multiValued field with a single value was output as a singe
value, not an array containing a single value. Some people wanted
more predictability (always an
BlackBerry sur le réseau mobile de Vidéotron
--
*From: * Robert Muir rcm...@gmail.com
*Date: *Sat, 10 Nov 2012 21:33:47 -0500
*To: *dev@lucene.apache.org
*ReplyTo: * dev@lucene.apache.org
*Subject: *Optimize facets when actually single valued?
I am guessing
, 10 Nov 2012 21:33:47 -0500
*To: *dev@lucene.apache.org
*ReplyTo: * dev@lucene.apache.org
*Subject: *Optimize facets when actually single valued?
I am guessing at times people are lazy about schema definition. But, I
think with lucene 4 stats we can detect if a field is actually single
On Sat, Nov 10, 2012 at 9:41 PM, Jimmy Sélamy jym...@gmail.com wrote:
Im having perfomance issues with facet on multivalued field with an index
over 20Million documents.
And when doing faceting search on multivalued field the QTIME is
unacceptable for my application because it can take up to
On Sun, Nov 11, 2012 at 3:33 AM, Robert Muir rcm...@gmail.com wrote:
I am guessing at times people are lazy about schema definition. But, I think
with lucene 4 stats we can detect if a field is actually single valued...
Something like terms.size == terms.doccount == terms.sumdocfreq. I have to
I am guessing at times people are lazy about schema definition. But, I
think with lucene 4 stats we can detect if a field is actually single
valued... Something like terms.size == terms.doccount == terms.sumdocfreq.
I have to think about it a bit, maybe its even simpler than this? Anyway,
this
@lucene.apache.org
Subject: Optimize facets when actually single valued?
I am guessing at times people are lazy about schema definition. But, I
think with lucene 4 stats we can detect if a field is actually single
valued... Something like terms.size == terms.doccount == terms.sumdocfreq.
I have to think about
15 matches
Mail list logo
