Hello,
I want to have an additional field that appears for every document in
search results. I understand that I should do this by adding the field to
the schema.xml, so I add:
field name=myField default=0 type=integer stored=true
indexed=false/
Then I restart Solr (so that I loads the new
Hi Gabriele,
Did you index any docs with your new field ?
The results will just bring back docs and what fields they have. They won't
bring back null fields just because they are in your schema. Lucene
is schema-less.
Solr adds the schema to make it nice to administer and very powerful to use.
I'd start by removing lots of stuff, particularly
WordDelimiterFilterFactory. That's splitting your input up by non-alpha
characters.
If you really want just the string stored, try just using KeywordTokenizer
and LowerCaseFilter (although AsciFolding... wouln't hurt).
But the best way to
Can you post the results of adding debugQuery=on to your two versions? And
have you re-indexed or not?
Best
Erick
On Jul 1, 2011 12:31 PM, dhastings dhasti...@wshein.com wrote:
i guess what im asking is how to set up solr/lucene to find
yale l.j.
yale l. j.
yale l j
as all the same thing.
Is there how I can compute and add the field to all indexed documents
without re-indexing? MyField counts the number of terms per document (unique
word count).
On Sun, Jul 3, 2011 at 12:24 PM, lee carroll
lee.a.carr...@googlemail.comwrote:
Hi Gabriele,
Did you index any docs with your new
Hello,
I just tried up(down?)grading our current Solr 4.0 trunk setup to Solr 3.3.0
as result grouping was the only reason for us to stay with the trunk.
Everything worked like a charm except for one of our queries, where we group
results by the owning user and sort by distance.
A simplified
Hello,
I'm trying to add a field that counts the number of terms in a document to
my schema. So far I've been computing this value at query-time. Is there how
I could compute this once only and store the field?
final SolrIndexSearcher searcher = request.getSearcher();
final
You'll need to index the field. I would think you would want to
index/store the field along with the associated document, in which case
you'll have to reindex the documents as well - there's no single-field
update capability in Lucene (yet?).
-Mike
On 7/3/2011 1:09 PM, Gabriele Kahlout
On 7/2/2011 12:34 PM, Yonik Seeley wrote:
OK, I tried a quick test of 1.4.1 vs 3x on optimized indexes
(unoptimized had different numbers of segments so I didn't try that).
3x (as of today) was 28% faster at a large filter query (300 terms in
one big disjunction, with each term matching ~1000
I know the queryResultCache and stuff live only so long as a commit happens
but I'm wondering if the custom caches are like this as well? I'd actually
rather have a custom cache which is not cleared at all. I want to give the
elements of this Cache a 6 hour TTL (or some time frame) but I never
On Sun, Jul 3, 2011 at 10:52 PM, arian487 akarb...@tagged.com wrote:
I know the queryResultCache and stuff live only so long as a commit happens
but I'm wondering if the custom caches are like this as well? I'd actually
rather have a custom cache which is not cleared at all.
That's not
Hi All
I have complex phrase queries including wildcard.
(ex. q=conn* pho*~2 OR inter* pho*~2 OR ...)
That takes long query result time.
I tried reindex after changing termIndexInterval to 8 for reduce the query
result time through more loading term index info.
I thought if I do so query result
12 matches
Mail list logo