Hi,
When I tried to execute the mlt handler query on a shard it is giving
result if the documents exist on that shards.
in below scenario, I have a cloud shards on localhost with ports 8181 and
8191. where documents are distributed. if the mlt query document id belongs
to 8181 shard and the
Hi,
When I tried to execute the mlt handler query on a shard it is giving
result if the documents exist on that shards.
in below scenario, I have a cloud shards on localhost with ports 8181 and
8191. where documents are distributed. if the mlt query document id belongs
to 8181 shard and the
Hi Experts, Its an urgent issue, Please advice :- I am Running solrj
program which connect to Solr server and run queries and gives result-set.
Queries :-2 level Nested queries First level fetch 154 rows. Each row
contain 2 fields Second Level fetch only counts for 154 rows Now problem:-
It
bq: Cloudera 4.5 setup
Probably should ask this on the Cloudera user's list.
But a 10,000 ms timeout is pretty low, I'd increase that. I suspect
the 80 rows bit is coincidental and there's something else happening.
Best,
Erick
On Tue, Nov 18, 2014 at 3:36 AM, Uddgam Singh
Is there any kind of general rule-of-thumb character limit in regards to
faceting on very long strings?
I have a string field that I want to facet on (contains geographic data
structured as a GeoJSON Feature), where the length is typically around 220
characters. Is this too long to facet on,
Thanks will try with a POST
--
View this message in context:
http://lucene.472066.n3.nabble.com/Restrict-search-to-subset-a-list-of-aprrox-40-000-ids-from-an-external-service-of-corpus-tp4169210p4169675.html
Sent from the Solr - User mailing list archive at Nabble.com.
English, Eben [eengl...@bpl.org] wrote:
Is there any kind of general rule-of-thumb character limit in regards to
faceting on very long strings?
Not really. There are limits, but they are quite high. Due to a bad analyzer we
had an index with ~1M unique facet values that ranged from 100-3000
On 27/10/2014 14:25, Charlie Hull wrote:
Hi all,
We noticed that there isn't a Lucene/Solr user group in London (although
there is an Elasticsearch user group) - so we decided to start one!
http://www.meetup.com/Apache-Lucene-Solr-London-User-Group
Please join if you're interested and do pass
We're achieving some success by treating aliases as collections and
collections as shards.
More specifically, there's a read alias that spans all the collections,
and a write alias that points at the 'latest' collection. Every week, I
create a new collection, add it to the read alias, and
On 18 November 2014 11:41, Charlie Hull char...@flax.co.uk wrote:
presenting some results of a Solr/Elasticsearch comparative performance
study.
I was asked about that a couple of times at the Solr Revolution
conference. Looking forward to seeing the results.
Regards,
Alex.
Personal:
Hi All,
I am getting an error when using solrj to index records.
Exception in thread main
org.apache.solr.client.solrj.impl.CloudSolrServer$RouteException: Exception
writing document id 529241050 to the index; possible analysis error.
at
I haven't seen this specific error before, but my guess would be that
your 'schemaless' mode has created a field of a particular type which
does not match it's later usage.
So, it may have seen '3' and assumed integers and now you are giving it 'four'.
I would pull that specific record up and
Please help me on this issue. Please provide me suggestions what is missing
to get the response from multiple solr shards in cloud.
On Tue, Nov 18, 2014 at 1:40 PM, Jilani Shaik jilani24...@gmail.com wrote:
Hi,
When I tried to execute the mlt handler query on a shard it is giving
result if
followup - hunspell has:
follow/SDRZGJ
follower/M
following/M
follow/G generates following
I guess the reason for the /M entries is to represent the nouns, which
have plural endings, so that
following-followings
-- I'm not really sure where the bug is, but it seems as if generating
I find that a query for stemmed terms sometimes fails with the edismax
query parser and hunspell stemmer. Looklng at the output of analysis for
the query (text:following) I can see that it generates two different
terms at the same position: follow and following. Then edismax seems
to generate
Hi,
I am getting OOM when faceting on numFound=28. The receiving solr node throws
the OutOfMemoryError even though there is 7gb available heap before the
faceting request was submitted. If a different solr node is selected that one
fails too. Any suggestions ?
1) Test setup is:-
100
Mohsin Beg Beg [mohsin@oracle.com] wrote:
I am getting OOM when faceting on numFound=28. The receiving
solr node throws the OutOfMemoryError even though there is 7gb
available heap before the faceting request was submitted.
fc and fcs faceting memory overhead is (nearly) independent on the
Solr JOINs are a way to enforce simple document security, as explained
by Yonik Seeley at
http://lucene.472066.n3.nabble.com/document-level-security-filter-solution-for-Solr-tp4126992p4126994.html
I'm trying to tweak this pattern so that I don't have to keep the
security information in each of my
I need to implement indexing of hierarchical data , like post and its
comments .
Each comment has few fields like username / text / date .
There are few more types like comment that I need too . ( the only
difference is field names and its count)
There are LatLonType filed type , which
OK - please disregard; I found a rogue new component in our analyzer
that was messing everything up.
The hunspell behavior was perhaps a little confusing, but I don't
believe it leads to broken queries.
-Mike
On 11/18/2014 02:38 PM, Michael Sokolov wrote:
followup - hunspell has:
Hi,
I tried to use bf for boosting, and got the following error:
org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError:
Unexpected text after function: )
Here's the bf boosting:
str
Hi Jilani,
Looking at the use case you have, you might want to try out the MLT Query
parser. The handler has issues when the client sends MLT request to a shard
that doesn't contain the document because of the way it's been designed.
Look at the following issues:
* SOLR-5480
On 18 November 2014 15:52, Michael Sokolov
msoko...@safaribooksonline.com wrote:
I found a rogue new component in our analyzer
We have a first Solr virus? I thought we were safe until the upload
the plugin JIRA was in production :-)
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and
On 11/18/2014 1:10 AM, Jilani Shaik wrote:
When I tried to execute the mlt handler query on a shard it is giving
result if the documents exist on that shards.
in below scenario, I have a cloud shards on localhost with ports 8181 and
8191. where documents are distributed. if the mlt query
Would LOVE to see the results (assuming you can ensure the same fruit(s?)
are being compared)
Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr Elasticsearch Support * http://sematext.com/
On Tue, Nov 18, 2014 at 11:55 AM, Alexandre Rafalovitch
Looking at SimpleFacets.java, doesn't fc/fcs iterate only over the DocSet for
the fields. So assuming each field has a unique term across the 28 rows, a max
of 28 * 15 unique small strings (100bytes), should be in the order of 1MB. For
100 collections, lets say a total of 1GB. Now lets say I
On 11/18/2014 3:06 PM, Mohsin Beg Beg wrote:
Looking at SimpleFacets.java, doesn't fc/fcs iterate only over the DocSet for
the fields. So assuming each field has a unique term across the 28 rows, a
max of 28 * 15 unique small strings (100bytes), should be in the order of
1MB. For 100
Mohsin Beg Beg [mohsin@oracle.com] wrote:
Looking at SimpleFacets.java, doesn't fc/fcs iterate only over the DocSet for
the fields.
To get the seed for the concrete faceting resolving, yes. That still leaves the
mapping and the counting structures.
So assuming each field has a unique
solrcloud has 8billion+ docs and increasing non-linearly each hour.
numFound=28 was for the faceting query only.
If fieldCache (lucene caches) is the issue, is q=time:[begin time TO end
time] be better instead ?
-Mohsin
- Original Message -
From: apa...@elyograg.org
To:
Thanks Evan and Jason.
I'll probably go with the approach that Evan suggested. This allows the UI to
change and display full hierarchy if required in future.
-Original Message-
From: Evan Pease [mailto:evancpe...@gmail.com]
Sent: Tuesday, November 18, 2014 12:41 AM
To:
30 matches
Mail list logo
