You seem to know what you want the words to map to, so index the map. Have one
field for the word, one field for the mapped value, and at query time, search
the words and return the mapped field. If it is comma separated, so be it and
split it up in your code post search.
Otherwise, same as
Usually, people want to do the opposite - store the numeric code as a
numeric field for perceived efficiency and let the user query and view
results with the text form. But, there isn't any evidence of any great
performance benefit of doing so - just store the string code in a string
field.
When merging through the core admin (
http://wiki.apache.org/solr/MergingSolrIndexes) what is the policy for
conflicts during the merge? So for instance if I am merging core 1 and
core 2 into core 0 (first example), what happens if core 1 and core 2 both
have a document with the same key, say
On Jun 8, 2013, at 12:52 PM, Jamie Johnson jej2...@gmail.com wrote:
When merging through the core admin (
http://wiki.apache.org/solr/MergingSolrIndexes) what is the policy for
conflicts during the merge? So for instance if I am merging core 1 and
core 2 into core 0 (first example), what
Turning swappiness down to 0 can have some decent performance impact.
- http://en.wikipedia.org/wiki/Swappiness
In the past, I've seen better performance with ext3 over ext4 around
commits/fsync. Test were actually enough slower (lots of these operations),
that I made a special ext3 partition
I wanted to analyze high frequency terms using Solr's Luke request handler
and keep updating the stopwords file for new queries from time to time.
Obviously I have to index all terms whether they belong to stopwords list or
not.
So I configured query analyzer stopwords list but disabled index
Remove the stopFilter from the index section of your fieldType, only keep it
in the query section. This way your stopwords will always be indexed and
edismax will be able to selectively remove stopwords from the query depending
on whether all words are stopwords or not.
--
Jan Høydahl, search
Maybe returned hits match other query terms.
Otis
Solr ElasticSearch Support
http://sematext.com/
On Jun 8, 2013 6:34 PM, jchen2000 jchen...@yahoo.com wrote:
I wanted to analyze high frequency terms using Solr's Luke request handler
and keep updating the stopwords file for new queries from
Dear All
I have a multi-valued field blocked_company_ids in index.
You can think like
1. document1 , blocked_company_ids: 1, 5, 7
2. document2 , blocked_company_ids: 2, 6, 7
3. document3 , blocked_company_ids: 4, 5, 6
and so on .
If I want to retrieve all the documents where
Try:
...q=*:*fq=-blocked_company_ids:5
Otis
--
Solr ElasticSearch Support
http://sematext.com/
On Sat, Jun 8, 2013 at 9:37 PM, Kamal Palei palei.ka...@gmail.com wrote:
Dear All
I have a multi-valued field blocked_company_ids in index.
You can think like
1. document1 ,
Also please note that for some documents, blocked_company_ids may not be
present as well. In such cases that document should be present in search
result as well.
BR,
Kamal
On Sun, Jun 9, 2013 at 7:07 AM, Kamal Palei palei.ka...@gmail.com wrote:
Dear All
I have a multi-valued field
Though the syntax looks fine, but I get all the records. As per example
given above I get all the documents, meaning filtering did not work. I am
curious to know if my indexing went fine or not. I will check and revert
back.
On Sun, Jun 9, 2013 at 7:21 AM, Otis Gospodnetic
Hi,
Is there anything in SolrCloud that would support query-node/shard
affinity/stickiness?
What I mean by that is a mechanism that is smart enough to keep
sending the same query X to the same node(s)+shard(s)... with the goal
being better utilization of Solr and OS caches?
Example:
* Imagine a
Hello,
This sounds like a custom SearchComponent.
Which clustering library you want to use or DIY is up to you, but go
with the SearchComponent approach. You will still need to process N
hits, but you won't need to first send them all over the wire.
Otis
--
Solr ElasticSearch Support
I have noticed that when I write a doc with an id that already exists, it
creates a new revision with the only the fields from the second write. I
guess there is a REST API in the latest solr version which updates only
selected fields.
In my opinion, merge should be creating a doc which is a
Hi,
Is there a notion of a data-node vs. non-data node in SolrCloud?
Something a la http://www.elasticsearch.org/guide/reference/modules/node/
Thanks,
Otis
Solr ElasticSearch Support
http://sematext.com/
16 matches
Mail list logo
