With such a short replication period, the statistics for autowarming won’t be
very good. They will be recent, but not the most popular and likely, because of
the tiny sampling period.
You might try some static warming queries instead.
Find a fairly stable set of most popular queries and put
Hi all,
I have a scenario here and I'd love some advice on what my options are. We
have one Solr master and two read replicas. The replicas query the master
every 10 seconds because we need relatively quick availability of new
documents. We balance read queries across all three servers
What are your autowarm settings? You should be able to alleviate this by
configuring these in solrconfig.xml
1 your cache autowarm settings, particularly filterCache and
documentResultCache.
2 your newSearcher settings.
The point of all the autowarming is that these queries are executed after
do this by having group.limit set
to 1. The ultimate goal is to get the first artifact in a group as well as some
metadata about the entire group.
Where in the implementation of group queries is numFound calculated? Is it
possible to, at this time, add in code to support additional roll up
, Hayden Muhl haydenm...@gmail.com
wrote:
I'm working on using Solr for autocompleting usernames. I'm running
into
a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like solr-user will
be
tokenized into solr and user, and will match
AM, Hayden Muhl haydenm...@gmail.com
wrote:
I'm working on using Solr for autocompleting usernames. I'm running
into
a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like solr-user will
be
tokenized into solr and user
into
a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like solr-user will
be
tokenized into solr and user, and will match both sol and use
prefixes. The problem is when we get solr-u as a prefix, I'm having
to
split that up
/ and @solrstart
Solr popularizers community:
https://www.linkedin.com/groups?gid=6713853
On Tue, Jul 15, 2014 at 8:04 AM, Hayden Muhl haydenm...@gmail.com
wrote:
I'm working on using Solr for autocompleting usernames. I'm running
into
a
problem with the wildcard queries (e.g. username:al
://www.linkedin.com/groups?gid=6713853
On Tue, Jul 15, 2014 at 8:04 AM, Hayden Muhl haydenm...@gmail.com
wrote:
I'm working on using Solr for autocompleting usernames. I'm running
into
a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like
?gid=6713853
On Tue, Jul 15, 2014 at 8:04 AM, Hayden Muhl haydenm...@gmail.com wrote:
I'm working on using Solr for autocompleting usernames. I'm running into
a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like solr-user
, Hayden Muhl haydenm...@gmail.com
wrote:
I'm working on using Solr for autocompleting usernames. I'm running
into
a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like solr-user will be
tokenized into solr and user, and will match
I'm working on using Solr for autocompleting usernames. I'm running into a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like solr-user will be
tokenized into solr and user, and will match both sol and use
prefixes. The problem is when we
running into a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like solr-user will be
tokenized into solr and user, and will match both sol and use
prefixes. The problem is when we get solr-u as a prefix, I'm having to
split that up
How is running multiple queries at the same time different from running
them in parallel? So, why not just run them in parallel. I mean, Solr can
accept simultaneous query requests just fine, so what's the issue here?
IOW, put the logic in your application layer and use SOlr as a streamlined
Krupansky j...@basetechnology.com wrote:
How is running multiple queries at the same time different from running
them in parallel? So, why not just run them in parallel. I mean, Solr can
accept simultaneous query requests just fine, so what's the issue here?
IOW, put the logic in your application
?
I am not good at JAVA, is there any why to do that with built in solr
component ?
Thanks,
Chunki.
On Jul 10, 2014, at 11:53 PM, Jack Krupansky j...@basetechnology.com wrote:
How is running multiple queries at the same time different from running
them in parallel? So, why not just run
Hi,
Is there any way to run multiple queries at the same time?
situation is
1. when query in
2. check synonyms
3. get search results for all synonym queries and original query
even if, I can get search results by looping searcher but, as you know, it is
time consuming.
Thanks,
Chunki.
=ljangra_query_:select?q=text:sharepointwt=jsonindent=truefq:acls:(*)
Is it still more performant than using two separate queries?
Regards.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Clubbing-queries-with-different-criterias-together-tp4143829p4145217.html
Sent from the Solr
returning zero.
Can anyone help me in this regard.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Aggregate-functions-in-Solr-entity-Queries-tp4143675.html
Sent from the Solr - User mailing list archive at Nabble.com.
=true_query_=%22AuthenticatedUserName=lalit%22
But for second set of documents, i need to use filter queries.
http://solrserver/solr/collection1/select?q=*%3A*fq=alf_acls%3AGROUP_EVERYONEwt=jsonindent=true
One way of getting all documents is to make two different queries and
combine their results
Hi Lalit,
_query_ is a magic field name. Please see :
http://searchhub.org/2009/03/31/nested-queries-in-solr/
What do you use _query_=AuthenticatedUserName=lalit ? It is simply ignored.
Ahmet
On Tuesday, June 24, 2014 11:34 PM, lalitjangra lalit.j.jan...@gmail.com
wrote:
Hi,
I have
. Was expecting one of: EOF OR ...
AND ... NOT ... W ... N ... ^ ... ,
*
Couldn't figure out the syntax from SurroundQParserPlugin code.
How to combine other term and/or boolean queries with surround queries. Also
looking for syntax to add more than one surround query on different fields
Hello,
special field name _query_ is your friend.
+_query_:{!surround maxBasicQueries=10}company:5N(comput*, appli*)
+_query_:{!lucene}year:[2005 TO *]
http://searchhub.org/2009/03/31/nested-queries-in-solr/
Ahmet
On Friday, June 20, 2014 9:39 AM, Shyamsunder R Mutcha
sjh
Thanks for the info. I will look at that.
On Wed, Jun 11, 2014 at 3:47 PM, Joel Bernstein joels...@gmail.com wrote:
In Solr 4.9 there is a feature called RankQueries, that allows you to
plugin your own ranking collector. So, if you wanted to write a
ranking/sorting collector that used a thread
called fingerprint that stores a few (let's say 100) bytes that are
some kind of digital fingerprint-like thing.
Let's say I want to perform queries on that field to achieve sorting
or filtering based on a kind of custom distance function
customDistance, i.e. I input a reference fingerprint
On Wed, Jun 11, 2014 at 7:46 AM, Robert Krüger krue...@lesspain.de wrote:
Or will I have to set up distributed search to achieve that?
Yes — you have to shard it to achieve that. The shards could be on the
same node.
There were some discussions this year in JIRA about being able to do
In Solr 4.9 there is a feature called RankQueries, that allows you to
plugin your own ranking collector. So, if you wanted to write a
ranking/sorting collector that used a thread per segment, you could cleanly
plug it in.
Joel Bernstein
Search Engineer at Heliosearch
On Wed, Jun 11, 2014 at
that are
some kind of digital fingerprint-like thing.
Let's say I want to perform queries on that field to achieve sorting
or filtering based on a kind of custom distance function
customDistance, i.e. I input a reference fingerprint and Solr
returns either all documents sorted by
customDistance
Hi,
let's say I have an index that contains a field of type BinaryField
called fingerprint that stores a few (let's say 100) bytes that are
some kind of digital fingerprint-like thing.
Let's say I want to perform queries on that field to achieve sorting
or filtering based on a kind of custom
,
let's say I have an index that contains a field of type BinaryField
called fingerprint that stores a few (let's say 100) bytes that are
some kind of digital fingerprint-like thing.
Let's say I want to perform queries on that field to achieve sorting
or filtering based on a kind of custom
Hi,
Solr is good at caching: even if first cold query takes longer time, the
subsequent one is much quicker, given that it shares the fq's of the first
query.
This is more like an idea question:
what about the out-of-vocabulary (OOV) queries? According to my quick
measurements, they take same
It seems as if 0-hit queries should be pretty fast since they can
terminate very early? Are you seeing a big difference between
first-time and subsequent (cached) no-match queries?
-Mike
On 6/5/2014 8:47 AM, Dmitry Kan wrote:
Hi,
Solr is good at caching: even if first cold query takes
On Thu, Jun 5, 2014 at 4:17 PM, Michael Sokolov
msoko...@safaribooksonline.com wrote:
It seems as if 0-hit queries should be pretty fast since they can
terminate very early? Are you seeing a big difference between first-time
and subsequent (cached) no-match queries?
-Mike
On 6/5/2014 8:47
Hi! I have a question which I posted on
http://stackoverflow.com/questions/23959727/sum-of-nested-queries-in-solr about
taking the sum of OR'd nested queries. I'll repeat it here, but if you want
some SO points and have an answer, feel free to answer there.
[quote]
We have a search
://stackoverflow.com/questions/23959727/sum-of-nested-queries-in-solr about
taking the sum of OR'd nested queries. I'll repeat it here, but if you want
some SO points and have an answer, feel free to answer there.
[quote]
We have a search that takes text from two different fields
Thanks for looking into this.
These are our static queries. We only see one of them getting executed. If it
fails to execute others, shouldn't it show error in log?
listener event=newSearcher class=solr.QuerySenderListener
arr name=queries
lst
Subject: Re: multiple queries in single request
No, I was rejecting BOTH methods 1 and 2. I was suggesting a different method.
I'll leave it to somebody else to describe the method so that it is easier to
understand.
-- Jack Krupansky
-Original Message-
From: Pavel Belenkovich
Sent
I agree with Eric that this is premature unless you can show that it makes
a difference.
Firstly why are you splitting the data into multiple time tiers (one
recent, and one all) and then waiting to merge results from all of them?
Time tiering is useful when you can do the search separately on
, 2014 01:26
To: solr-user@lucene.apache.org
Subject: Re: multiple queries in single request
Nothing special for this use case.
This seems to be a use case that I would call bulk data retrieval - based on
ID.
I would suggest batching your requests - limit each request query to, say,
50 or 100 IDs
Message-
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: Thursday, May 22, 2014 01:26
To: solr-user@lucene.apache.org
Subject: Re: multiple queries in single request
Nothing special for this use case.
This seems to be a use case that I would call bulk data retrieval - based
on ID
Great, thanx Mikhail, Ill try that out.
regards,
Pavel.
-Original Message-
From: Mikhail Khludnev [mailto:mkhlud...@griddynamics.com]
Sent: Thursday, May 22, 2014 11:49
To: solr-user
Subject: Re: multiple queries in single request
Pavel,
I suppose the benchmark matters, anyway. (when
@lucene.apache.org
Subject: RE: multiple queries in single request
Hi Jack!
Thanx for the response!
So you say that using method 2 below (single request with ORs and sorting
results in client) is better than method 1 (separate requests)?
regards,
Pavel.
-Original Message-
From: Jack
in the application is complex as well.
Is there some Solr code I can use in the application level to unify multiple
results? (this can be actually an interesting direction)
The queries were of course just an example. In real life I have 4 cores with
very complex queries for each so unifying all 4
Thanks for looking into this.
Auto warming queries are the ones which gets executed upon creation of first
searcher and new searcher. We use same set of queries for first and new
searcher.
These are our queries.
listener event=newSearcher class=solr.QuerySenderListener
arr name
Thanks, Erick!
On Tue, May 20, 2014 at 3:55 AM, Erick Erickson erickerick...@gmail.comwrote:
This might be useful:
http://searchhub.org/2012/02/23/date-math-now-and-filter-queries/
Best,
Erick
On Mon, May 19, 2014 at 12:09 AM, Dmitry Kan solrexp...@gmail.com wrote:
Thanks, Jack, Alex
I have 2 cores.
One with active data and one with historical data (for documents which were
removed from the active one).
I want to run Distributed Search on both and get the unified result (as
supported by Solr Distributed Search, I'm not using Solr Cloud).
My problem is that the query for each
I suppose you could, but I _really_ question whether it's a wise
investment in time. Personally I'd treat them as two different
collections and have the app layer fire off two queries and do the
aggregation (this is a variant of federated search I think). This
removes your issue with having
-
From: Avner Levy
Sent: Wednesday, May 21, 2014 9:56 AM
To: solr-user@lucene.apache.org
Subject: Distributed Search in Solr with different queries per shard
I have 2 cores.
One with active data and one with historical data (for documents which were
removed from the active one).
I want to run
Hi,
I have list of 1000 values for some field which is sort of id (essentially
unique between documents)
(let's say firstname_lastmane).
I need to get the document for each id (to know which document is for which id,
not just list of responses).
Is there some support for multiple queries
: Wednesday, May 21, 2014 1:07 PM
To: solr-user@lucene.apache.org
Subject: multiple queries in single request
Hi,
I have list of 1000 values for some field which is sort of id (essentially
unique between documents)
(let's say firstname_lastmane).
I need to get the document for each id (to know which
-
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: Wednesday, May 21, 2014 6:52 PM
To: solr-user@lucene.apache.org
Subject: Re: Distributed Search in Solr with different queries per shard
Unfortunately the same query will be sent to all cores if you use the shards
parameter to query
I believe unifying multiple query results including facets, paging, sorts and
other extra features on my own in the application is complex as well.
Is there some Solr code I can use in the application level to unify multiple
results? (this can be actually an interesting direction)
The queries
Thanks, Jack, Alex and Shawn.
This makes proper sense. One win of rounding down on indexing side is
saving index space, according to hoss (reply over IRC):
with the TrieDateFields, rounding dates at indexing time won't have any
effect on the cachability of the rounded queries, and even for non
This might be useful:
http://searchhub.org/2012/02/23/date-math-now-and-filter-queries/
Best,
Erick
On Mon, May 19, 2014 at 12:09 AM, Dmitry Kan solrexp...@gmail.com wrote:
Thanks, Jack, Alex and Shawn.
This makes proper sense. One win of rounding down on indexing side is
saving index space
Hi all
Postingshighlighter in Solr 4.7 is supposed to be able to highlight prefix
queries. However you are supposed to subclass it and override getAnalyzer
to that used at index time.
Any examples to show how this is done when using Solr?
Regards
Puneet
Are you talking about static warming queries, which you define as
newSearcher and firstSearcher events? If so, you should see all three
queries in the log. If you're still having the issue, can you post your
warming query configuration?
Joel Bernstein
Search Engineer at Heliosearch
On Wed, May
Hi,
There was a mention either on solr wiki or on this list, that in order to
optimize the date range queries, it is beneficial to round down the range
values.
For example, if a range query is:
DateTime:[NOW-3DAYS TO NOW]
then if the precision up to msec is not required, we can safely round
My e-book has an example of an update processor that rounds to any specified
resolution (e.g, day, year, hour, etc.)
The performance reason was for filter queries, to keep their uniqueness
down, not random user queries, which should be fine unrounded, except that
they can't be used for exact
Hi,
How many auto warming queries are supported per collection in Solr4.4 and
higher? We see one out of three queries in log when new searcher is created.
Thanks!
I thought the date math rounding was for _caching_ the repeated
queries, not so much the speed of the query itself.
Also, if you are using TrieDateField, precisionStep value is how
optimization is done. There is bucketing at different level of
precision, so the range search works at the least
On 5/15/2014 1:34 AM, Alexandre Rafalovitch wrote:
I thought the date math rounding was for _caching_ the repeated
queries, not so much the speed of the query itself.
Absolutely correct. When NOW is used without rounding, caching is
completely ineffective. This is because if the same query
Hi,
How many auto warming queries are supported per collection in Solr4.4 and
higher? We see one out of three queries in log when new searcher is created.
Shouldn't it print all searcher queries?
Thanks!
We added an id (str name=xxxsearcher3/str) in each searcher but it never
gets printed in log file. Does Solr internally massages the searcher queries?
_
From: Joshi, Shital [Tech]
Sent: Monday, May 12, 2014 11:27 AM
To: 'solr-user@lucene.apache.org
First define an auto-warming query :)...
firstSearcher queries are fired when the server is started
newSearcher queries are fired when a new searcher is opened, i.e. when
a commit (hard when openSeracher=true or soft) happens.
Let's see your configuration too where you think you're setting up
queries in parallel?
On Thu, Apr 24, 2014 at 12:53 PM, Ahmet Arslan iori...@yahoo.com wrote:
Hi Vijay,
May be you can use _query_ hook?
_query_:{!span}BookingRecordId:234 OrderLineType:11 OR _query_:{!span}
OrderLineType:13 + BookingRecordId:ID_N
Ahmet
On Thursday, April 24
No, though one could write a custom SearchComponent, I imagine. Not
terribly useful for most situations where queries typically run for only a
few milliseconds, but
Otis
--
Performance Monitoring * Log Analytics * Search Analytics
Solr Elasticsearch Support * http://sematext.com/
On Thu
SpanTermQuery(new Term(BookingRecordId, ID_N))
);
On Friday, April 25, 2014 3:22 AM, Vijay Kokatnur kokatnur.vi...@gmail.com
wrote:
Thanks Ahmet. It worked!
Does solr execute these nested queries in parallel?
On Thu, Apr 24, 2014 at 12:53 PM, Ahmet Arslan iori...@yahoo.com wrote:
Hi Vijay
Some of our site's categories are actually search driven. They're created
manually by crafting a Solr query our of list of Lucene queries that are
joined in a DisjunctionMaxQuery. There are often 100+ disjuncts in this
query.
This works nicely, but is much slower than it could be because many
Hi,
I have defined a SpanQuery for proximity search like -
val q1 = new SpanTermQuery(new Term(BookingRecordId, 234))
val q2 = new SpanTermQuery(new Term(OrderLineType, 11))
val q2m = new FieldMaskingSpanQuery(q2, BookingRecordId)
val sp = Array[SpanQuery](q1, q2m)
val q = new SpanNearQuery(sp,
Hi Vijay,
May be you can use _query_ hook?
_query_:{!span}BookingRecordId:234 OrderLineType:11 OR _query_:{!span}
OrderLineType:13 + BookingRecordId:ID_N
Ahmet
On Thursday, April 24, 2014 9:34 PM, Vijay Kokatnur kokatnur.vi...@gmail.com
wrote:
Hi,
I have defined a SpanQuery for proximity
Thanks Ahmet. It worked!
Does solr execute these nested queries in parallel?
On Thu, Apr 24, 2014 at 12:53 PM, Ahmet Arslan iori...@yahoo.com wrote:
Hi Vijay,
May be you can use _query_ hook?
_query_:{!span}BookingRecordId:234 OrderLineType:11 OR _query_:{!span}
OrderLineType:13
/
/analyzer
/fieldType
--
View this message in context:
http://lucene.472066.n3.nabble.com/Filtering-Solr-Queries-tp4131924.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hello,
Is there some way of getting a list of all queries that are currently
executing? Something similar to 'show full processlist' in MySQL.
Thanks,
Nikhil
://www.solr-start.com/ - Accelerating your Solr proficiency
On Thu, Apr 17, 2014 at 6:34 PM, Nikhil Chhaochharia
nikhil...@yahoo.com wrote:
Hello,
Is there some way of getting a list of all queries that are currently
executing? Something similar to 'show full processlist' in MySQL.
Thanks
://lucene.472066.n3.nabble.com/Filtering-Solr-Queries-tp4131924.html
Sent from the Solr - User mailing list archive at Nabble.com.
Looking at this, sharding seems to be best and simple option to handle such
queries.
On Wed, Apr 2, 2014 at 1:26 AM, Mikhail Khludnev mkhlud...@griddynamics.com
wrote:
Hello Salman,
Let's me drop few thoughts on
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200903.mbox
AM, Salman Akram salman.ak...@northbaysolutions.net
wrote:
Looking at this, sharding seems to be best and simple option to handle such
queries.
On Wed, Apr 2, 2014 at 1:26 AM, Mikhail Khludnev mkhlud...@griddynamics.com
wrote:
Hello Salman,
Let's me drop few thoughts on
http://mail
bool name=waittrue/bool
/listener
--
/updateHandler
query
!-- Maximum number of clauses in a boolean query... can affect
range or prefix queries that expand to big boolean
queries. An exception is thrown if exceeded. --
maxBooleanClauses1024/maxBooleanClauses
I am using apache solr-4.6.1 and solr works fine when the number of
requests are less
*But when the number of concurrent requests are more Solr is not able to
handle it and it gives the following errors on server.*
834246 [qtp1797259051-168] WARN org.eclipse.jetty.servlet.ServletHandler
-
On 4/8/2014 3:17 AM, Sohan Kalsariya wrote:
I am using apache solr-4.6.1 and solr works fine when the number of
requests are less
*But when the number of concurrent requests are more Solr is not able to
handle it and it gives the following errors on server.*
834246 [qtp1797259051-168] WARN
I am using the Jetty that comes with the solr. And I am not using any third
party plugins or patches.
BTW what kinda error is this ?
Is this related to memory issue or what make me understand please.
On Tue, Apr 8, 2014 at 9:25 PM, Shawn Heisey s...@elyograg.org wrote:
On 4/8/2014 3:17 AM,
Shawn Heisey [s...@elyograg.org] wrote:
Are you using the Jetty that comes with Solr, or are you using Jetty
from another source? If you are using Jetty from another source, the
maxThreads parameter may not be high enough. I believe the default in a
typical Jetty config is 200, but the jetty
Actually I found why... I had and as lowercase word in my queries at the
checkbox does not seem to work in the admin UI.
adding lowercaseOperators=false made the queries work.
2014-04-04 18:10 GMT+02:00 Nils Kaiser m...@nils-kaiser.de:
Hey,
I am currently using solr to recognize songs
query
term phrase matches exactly.
-- Jack Krupansky
From: Nils Kaiser
Sent: Friday, April 4, 2014 10:10 AM
To: solr-user@lucene.apache.org
Subject: Strange behavior of edismax and mm=0 with long queries (bug?)
Hey,
I am currently using solr to recognize songs and people from a list of user
the collated comments as query. So it is a
case where the query is much longer. I need to use mm=0 or mm=1.
My plan was to use edismax as the pf2 and pf3 parameters should work well
for my usecase.
However when using longer queries, I get a strange behavior which can be
seen in debugQuery.
Here
Does lucene 4.6 use Lucene41PostingsFormat for Postings.nextdoc() while
executing the span queries?
When I am debugging the lucene 4.6 test cases for span queries, it is
showing that for above nextdoc() call it is utilizing DirectPostingsFormat.
My requirement is to run multiple span queries
So you too never got any response...
On Mon, Mar 31, 2014 at 6:57 PM, Luis Lebolo luis.leb...@gmail.com wrote:
Hi Salman,
I was interested in something similar, take a look at the following thread:
I got responses, but no easy solution to allow me to directly cancel a
request. The responses did point to:
- timeAllowed query parameter that returns partial results -
https://cwiki.apache.org/confluence/display/solr/Common+Query+Parameters#CommonQueryParameters-ThetimeAllowedParameter
rewrite occurs, it's thrown away, after
search is done. I think the most straightforward way is to address this
issue by caching these expensive queries. Solr does it well
http://wiki.apache.org/solr/CommonQueryParameters#fq However, only for
http://en.wikipedia.org/wiki/Conjunctive_normal_form like
/extract?literal.id=yabbauprefix=attr_fmap.content=attr_contentcommit=true
there are hundreds of tab and newline characters (i.e. \n and \t) in the
attr_content field. When a string occurs only once in the document, and is
adjacent to one of these characters, queries for that term are not
successful
.
-- Jack Krupansky
-Original Message-
From: chtjfi
Sent: Monday, March 31, 2014 3:23 AM
To: solr-user@lucene.apache.org
Subject: Unsuccessful queries for terms next to tabs and newlines in
uploaded Word documents
Short Version: What do I need to do to successfully query for terms
Anyone?
On Wed, Mar 26, 2014 at 7:55 PM, Salman Akram
salman.ak...@northbaysolutions.net wrote:
With reference to this
threadhttp://mail-archives.apache.org/mod_mbox/lucene-solr-user/200903.mbox/%3c856ac15f0903272054q2dbdbd19kea3c5ba9e105b...@mail.gmail.com%3EI
wanted to know if there was
Hi Salman,
I was interested in something similar, take a look at the following thread:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201401.mbox/%3CCADSoL-i04aYrsOo2%3DGcaFqsQ3mViF%2Bhn24ArDtT%3D7kpALtVHzA%40mail.gmail.com%3E#archives
I never followed through, however.
-Luis
On
With reference to this
threadhttp://mail-archives.apache.org/mod_mbox/lucene-solr-user/200903.mbox/%3c856ac15f0903272054q2dbdbd19kea3c5ba9e105b...@mail.gmail.com%3EI
wanted to know if there was any response to that or if Chris Harris
himself can comment on what he ended up doing, that would be
The Grouping feature only works if groups are in the same shard.
Perhaps that is the problem here?
I could find https://issues.apache.org/jira/browse/SOLR-4164 which
says that once the sharding was fixed, the problem went away. We
should come up with a better exception message though.
On Fri,
Hi Shalin,
Thank you for your answer.
I'm already using custom hashing to make sure all the docs that are going
to be grouped together are on the same shard. During index I make sure the
uniqueKey is something like:
productId!skuId
so all the skus belonging to the same product will end up
On 3/20/2014 12:55 PM, solr2020 wrote:
Thanks Shawn. When we run any solrj application , the below message is
displayed
org.apache.solr.client.solrj.impl.HttpClientUtil createClient
INFO: Creating new http client,
config:maxConnections=128maxConnectionsPerHost=32followRedirects=false
Those
Hi,
I have a two shard collection running and I'm getting this error on each
query:
2014-03-21 17:08:42,018 [qtp-75] ERROR
org.apache.solr.servlet.SolrDispatchFilter -
*null:java.lang.IllegalArgumentException:
numHits must be 0; please use TotalHitCountCollector if you just need the
total hit
://lucene.472066.n3.nabble.com/Parallel-queries-to-Solr-tp4119959p4125806.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi,
I have searched the mailing list archives but couldn't find the right
answer so far.
I want to elevate some results using instructions from
QueryElevationComponent page, but
I'm not sure how to set queries in *elevate.xml* file. My query looks like
this :
(content:foobar OR text:foobar
801 - 900 of 2470 matches
Mail list logo
