I have my index based spell checker configured, and the select request
handlers are configured with collation i.e. true
For my testing I have indexed 2 million records there after generated the
index based dictionary (I am evaluating the DirectSpellChecker, I am seeing
my memory consumption is mor
Can you set omitNorms to true in the fieldType and see if that helps? Check
http://wiki.apache.org/solr/SchemaXml#Common_field_options
On Fri, Jan 18, 2013 at 4:37 AM, wwhite1133 wrote:
> Sorry, I did not understand what you mean. Can you pl. elaborate..
> Thanks
> WW
>
>
>
> --
> View this mess
I'll always query on the set of 6 values, but in some cases, the matching
doesn't need to be exact.
I mean, an usual query (you know, 6 integer values) could be exact matching
for the first 4 values, but then a range for the other 2 values.
What do u think would be the best way to face it?
--
Could you not just have six different fields?
If you wanted greater search efficiency, maybe you could try indexing
them as described above, as strings. You could use the 'shingles' idea,
for example, if you had: 11 22 33 44 55 66 as your numbers, index the
terms:
11
11-22
11-22-33
11-22-33-44
1
Are you asking to sort on the number of matching terms?
Not an answer, but hopefully giving you pointers...
Firstly, highlighting is done in the highlighting component, which comes
after the QueryComponent in the list of search components invoked.
Sorting happens within the QueryComponent, which
Ok. Thank you everyone for your helpful answers.
I understand that fieldValueCache is not used for resolving queries.
Is there any cache that can help this basic scenario (a lot of different
queries, on a small set of fields)?
Does Lucene's FieldCache help (implicitly)?
How can I use RAM to reduce
I was using Solr 4.0 but ran into a few problems using SolrCloud. I'm
trying out 4.1 RC1 right now but the update URL I used to use is returning
HTTP 404.
For example, I would post my document updates to,
http://localhost:8983/solr/collection1
But that is 404ing now (collection1 exists according
I'm actually wondering if this other issue I've been having is a problem:
https://issues.apache.org/jira/browse/SOLR-4321
The fact that some nodes don't "get" pieces of a collection could explain
the 404.
That said, even when a node has "parts" of a collection it reports 404
sometimes. What's od
Hi Mike.
I am going through this too.
How did you solve this?
Thanks.
Arcadius.
On 15 December 2011 12:49, Michael Kelleher wrote:
> Yeah, I tried:
>
>
> //xhtml:div[@class='**bibliographicData']/**descendant:node()
>
> also tried
>
> //xhtml:div[@class='**bibliographicData']
>
> Neither wo
Indexing should def not slow down substantially if you commit every minute or
something. Be sure to use openSearcher=false on the auto hard commit.
- Mark
On Jan 19, 2013, at 11:11 PM, Nikhil Chhaochharia wrote:
>
>
> Hi,
>
> We run a SolrCloud cluster using Solr 4.0 updateLog is not confi
oakstream wrote
> Thanks guys!
> David,
>
> In general and in your opinion would Lucene Spatial be the way to go to
> index hundreds of terabytes of spatial data that continually grows.
> Mostly point data, mostly structured, however, could be polygons. The
> searches would be within or contains
11 matches
Mail list logo