First it was "I18N", then "LAMP", and recently "RoR" ... and now ... Solr
has hit the big time by becoming integrated into an obfuscated and
non-intuitive acronym that pertains to a stack/suite of software...
! ! !"LNS"! ! !
http://www.ideaeng.com/pub/entsrch/2008/num
Hello,
i have encountered a problem concerning the wildcard. When i search for
field:testword i get 50 results. That's ok but when I search for
field:testwor* i get just 3 hits! I get only words returned without a
whitespace after the char like "testwordtest" but i wont find any single
"test
On Fri, 11 Jan 2008 00:43:19 -0200
Leonardo Santagada <[EMAIL PROTECTED]> wrote:
> No, actually my problem is that the solr index is mirroring data on a
> database (a Zope app to be more acurate) so it would be better if I
> could send the whole transaction together so I don't have to keep it
On 12/01/2008, at 11:24, Norberto Meijome wrote:
On Fri, 11 Jan 2008 00:43:19 -0200
Leonardo Santagada <[EMAIL PROTECTED]> wrote:
No, actually my problem is that the solr index is mirroring data on a
database (a Zope app to be more acurate) so it would be better if I
could send the whole tran
Hi,
In my schema I have a multivalued field, and the values of that field are
"stored" and "indexed" in the index. I wanted to know if its possible to
restrict the number of multiple values being returned from that field, on a
search? And how? Because, lets say, if I have thousands of values in th
I don't have the answer to this one other than the "process it yourself in your
app". But should anyone decide to work on this, I have another similar
suggestion/request: return N *unique* values from a multivalued field sorted by
their count.
The use case for this is a tagging system like sim
Do you have to have your data in Solr as soon as its added to the DB? Probably
not. What if somebody manually changes the DB? It will be out of sync with
your DB. We see similar situations pretty frequently and our solution is a
standalone DB Indexing application that knows how to do increme
