Healthgrades looking for Search Product Manager

[William Bell]

Hi all.

I am reaching out to see if anyone of the Search experts in this group
would consider helping us out on Healthgrades search. We have a ton of
ideas from chat bots, to personalization, collaborative filtering, and are
going to build some ridiculously crazy ideas that consumers use to find a
doctor.

We are building a world class search experience and need help doing it.

Looking for FTE - can be anywhere but prefer Denver, CO or Consultant.

If interested reach out to me (bb...@healthgrades.com).

Thanks.

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: slow updates/searches

[Erick Erickson]

If both queries _and_ updates are slow, it's hard to see how upping
the number of
threads would help overall. Hmmm, you also reported that the CPUs
didn't seem to be
stressed so its worth a try, perhaps there's some kind of blocking going on

Best,
Erick

On Mon, Sep 19, 2016 at 5:33 PM, Rallavagu  wrote:
> Hi Erick,
>
> Would increasing (or adjusting) update threads help as per this JIRA ((Allow
> the number of threads ConcurrentUpdateSolrClient StreamingSolrClients
> configurable by a system property) here?
>
> https://issues.apache.org/jira/browse/SOLR-8500
>
> Thanks
>
>
> On 9/19/16 8:30 AM, Erick Erickson wrote:
>>
>> Hmmm, not sure, and also not sure what to suggest next. QTimes
>> measure only the search time, not, say, time waiting for the request to
>> get
>> serviced.
>>
>> I'm afraid the next suggestion is to throw a profiler at it 'cause nothing
>> jumps
>> out at me..'
>>
>> Best,
>> Erick
>>
>> On Fri, Sep 16, 2016 at 10:23 AM, Rallavagu  wrote:
>>>
>>> Comments in line...
>>>
>>> On 9/16/16 10:15 AM, Erick Erickson wrote:


 Well, the next thing I'd look at is CPU activity. If you're flooding the
 system
 with updates there'll be CPU contention.
>>>
>>>
>>>
>>> Monitoring does not suggest any high CPU but as you can see from vmstat
>>> output "user" cpu is a bit high during updates that are taking time (34
>>> user, 65 idle).
>>>

 And there are a number of things you can do that make updates in
 particular
 much less efficient, from committing very frequently (sometimes combined
 with excessive autowarm parameters) and the like.
>>>
>>>
>>>
>>> softCommit is set to 10 minutes, autowarm count is set to 0 and commit is
>>> set to 15 sec for NRT.
>>>

 There are a series of ideas that might trigger an "aha" moment:
 https://wiki.apache.org/solr/SolrPerformanceFactors
>>>
>>>
>>>
>>> Reviewed this document and made few changes accordingly a while ago.



 But the crude measure is just to look at CPU usage when updates happen,
 or
 just before. Are you running hot with queries alone then add an update
 burden?
>>>
>>>
>>>
>>> Essentially, it is high QTimes for queries got me looking into logs,
>>> system
>>> etc and I could correlate updates slowness and searching slowness. Some
>>> other time QTimes go high is right after softCommit which is expected.
>>>
>>> Wondering what causes update threads wait and if it has any impact on
>>> search
>>> at all. I had couple of more CPUs added but I still see similar behavior.
>>>
>>> Thanks.
>>>
>>>

 Best,
 Erick

 On Fri, Sep 16, 2016 at 9:19 AM, Rallavagu  wrote:
>
>
> Erick,
>
> Was monitoring GC activity and couldn't align GC pauses to this
> behavior.
> Also, the vmstat shows no swapping or cpu I/O wait. However, whenever I
> see
> high update response times (corresponding high QTimes for searches)
> vmstat
> shows as series of number of "waiting to runnable" processes in "r"
> column
> of "procs" section.
>
>
>
> https://dl.dropboxusercontent.com/u/39813705/Screen%20Shot%202016-09-16%20at%209.05.51%20AM.png
>
> procs ---memory-- ---swap--
> -io -system-- cpu -timestamp-
>  r  b swpd freeinact   active   si   so bi
> bo
> in   cs  us  sy  id  wa  st CDT
>  2  071068 18688496  2526604 2420444000 0
> 0
> 1433  462  27   1  73   0   0 2016-09-16 11:02:32
>  1  071068 18688180  2526600 2420456800 0
> 0
> 1388  404  26   1  74   0   0 2016-09-16 11:02:33
>  1  071068 18687928  2526600 2420456800 0
> 0
> 1354  401  25   0  75   0   0 2016-09-16 11:02:34
>  1  071068 18687800  2526600 2420457200 0
> 0
> 1311  397  25   0  74   0   0 2016-09-16 11:02:35
>  1  071068 18687164  2527116 2420484400 0
> 0
> 1770  702  31   1  69   0   0 2016-09-16 11:02:36
>  1  071068 18686944  2527108 2420490800 0
> 52
> 1266  421  26   0  74   0   0 2016-09-16 11:02:37
> 12  171068 18682676  2528560 2420711600 0
> 280
> 2388  934  34   1  65   0   0 2016-09-16 11:02:38
>  2  171068 18651340  2530820 2423336800 0
> 1052
> 10258 5696  82   5  13   0   0 2016-09-16 11:02:39
>  5  071068 18648600  2530112 2423506000 0
> 1988
> 7261 3644  84   2  13   1   0 2016-09-16 11:02:40
>  9  171068 18647804  2530580 2423607600 0
> 1688
> 7031 3575  84   2  13   1   0 2016-09-16 11:02:41
>  1  071068 18647628 

Re: Exception is thrown when using TimestampUpdateProcessorFactory

[Chris Hostetter]

: But I am getting below exception when i run update or through DIH. Please
: let me know how to fix this.
: 
: java.lang.NullPointerException
: at
: 
org.apache.solr.update.processor.TimestampUpdateProcessorFactory$1.getDefaultValue(TimestampUpdateProcessorFactory.java:66)


That's a really weird error.

I don't *think* Reth's suggestion will have any barring on the outcome, 
but i would love to hear if it changes anything.

the method name "getDefaultValue" in that stack trace is just 
because of how the class implements the general contract of a 
DefaultValueUpdateProcessor -- what that specific line is doing in 5.2.1 
is accessing the definition of "NOW" for the Solr Request -- metadata that 
is initialized when the request is first initiated (to ensure that a 
consistent value is used if, for example, multiple date based facets 
are computed i na single request, or multiple docs are added in a single 
request).

If you *only* got thsi error when using DIH, I would guess maybe DIH has a 
bug when it creates it's internal requests (because it's operating 
asynchronously) that prevents this value from getting initialized properly 
-- but you said "getting below exception when i run update or through DIH" 
... impliying that you get teh same exception when you do updates in other 
ways.

can you confirm/deny that you get a similar exception if/when you send 
updates *not* from DIH, and if so can you please show us the full stack 
trace of the error in that situation and provide some details regarding 
how you sent the update that caused that exception?


-Hoss
http://www.lucidworks.com/

Re: slow updates/searches

[Rallavagu]

Hi Erick,

Would increasing (or adjusting) update threads help as per this JIRA 
((Allow the number of threads ConcurrentUpdateSolrClient 
StreamingSolrClients configurable by a system property) here?


https://issues.apache.org/jira/browse/SOLR-8500

Thanks


On 9/19/16 8:30 AM, Erick Erickson wrote:

Hmmm, not sure, and also not sure what to suggest next. QTimes
measure only the search time, not, say, time waiting for the request to get
serviced.

I'm afraid the next suggestion is to throw a profiler at it 'cause nothing jumps
out at me..'

Best,
Erick

On Fri, Sep 16, 2016 at 10:23 AM, Rallavagu  wrote:

Comments in line...

On 9/16/16 10:15 AM, Erick Erickson wrote:


Well, the next thing I'd look at is CPU activity. If you're flooding the
system
with updates there'll be CPU contention.



Monitoring does not suggest any high CPU but as you can see from vmstat
output "user" cpu is a bit high during updates that are taking time (34
user, 65 idle).



And there are a number of things you can do that make updates in
particular
much less efficient, from committing very frequently (sometimes combined
with excessive autowarm parameters) and the like.



softCommit is set to 10 minutes, autowarm count is set to 0 and commit is
set to 15 sec for NRT.



There are a series of ideas that might trigger an "aha" moment:
https://wiki.apache.org/solr/SolrPerformanceFactors



Reviewed this document and made few changes accordingly a while ago.



But the crude measure is just to look at CPU usage when updates happen, or
just before. Are you running hot with queries alone then add an update
burden?



Essentially, it is high QTimes for queries got me looking into logs, system
etc and I could correlate updates slowness and searching slowness. Some
other time QTimes go high is right after softCommit which is expected.

Wondering what causes update threads wait and if it has any impact on search
at all. I had couple of more CPUs added but I still see similar behavior.

Thanks.




Best,
Erick

On Fri, Sep 16, 2016 at 9:19 AM, Rallavagu  wrote:


Erick,

Was monitoring GC activity and couldn't align GC pauses to this behavior.
Also, the vmstat shows no swapping or cpu I/O wait. However, whenever I
see
high update response times (corresponding high QTimes for searches)
vmstat
shows as series of number of "waiting to runnable" processes in "r"
column
of "procs" section.


https://dl.dropboxusercontent.com/u/39813705/Screen%20Shot%202016-09-16%20at%209.05.51%20AM.png

procs ---memory-- ---swap--
-io -system-- cpu -timestamp-
 r  b swpd freeinact   active   si   so bi
bo
in   cs  us  sy  id  wa  st CDT
 2  071068 18688496  2526604 2420444000 0
0
1433  462  27   1  73   0   0 2016-09-16 11:02:32
 1  071068 18688180  2526600 2420456800 0
0
1388  404  26   1  74   0   0 2016-09-16 11:02:33
 1  071068 18687928  2526600 2420456800 0
0
1354  401  25   0  75   0   0 2016-09-16 11:02:34
 1  071068 18687800  2526600 2420457200 0
0
1311  397  25   0  74   0   0 2016-09-16 11:02:35
 1  071068 18687164  2527116 2420484400 0
0
1770  702  31   1  69   0   0 2016-09-16 11:02:36
 1  071068 18686944  2527108 2420490800 0
52
1266  421  26   0  74   0   0 2016-09-16 11:02:37
12  171068 18682676  2528560 2420711600 0
280
2388  934  34   1  65   0   0 2016-09-16 11:02:38
 2  171068 18651340  2530820 2423336800 0
1052
10258 5696  82   5  13   0   0 2016-09-16 11:02:39
 5  071068 18648600  2530112 2423506000 0
1988
7261 3644  84   2  13   1   0 2016-09-16 11:02:40
 9  171068 18647804  2530580 2423607600 0
1688
7031 3575  84   2  13   1   0 2016-09-16 11:02:41
 1  071068 18647628  2530364 2423625600 0
680
7065 4463  61   3  35   1   0 2016-09-16 11:02:42
 1  071068 18646344  2531204 2423653600 0
44
6422 4922  35   3  63   0   0 2016-09-16 11:02:43
 2  071068 18644460  2532196 2423744000 0
0
6561 5056  25   3  72   0   0 2016-09-16 11:02:44
 0  071068 18661900  2531724 2421876400 0
0
7312 10050  11   3  86   0   0 2016-09-16 11:02:45
 2  071068 18649400  2532228 2422980000 0
0
7211 6222  34   3  63   0   0 2016-09-16 11:02:46
 0  071068 18648280  2533440 2423030000 0
108
3936 3381  20   1  79   0   0 2016-09-16 11:02:47
 0  071068 18648156  2533212 2423068400 0
12
1279 1681   2   0  97   0   0 2016-09-16 11:02:48


Captured stack trace including timing for one of the update threads.

Re: Distributing nodes with the collections API RESTORE command

[Stephen Lewis]

Thanks Hrishikesh! Looking forward to hearing from you.

On Fri, Sep 16, 2016 at 9:30 PM, Hrishikesh Gadre 
wrote:

> Hi Stephen,
>
> Thanks for the update. I filed SOLR-9527
>  for tracking purpose. I
> will take a look and get back to you.
>
> Thanks
> Hrishikesh
>
> On Fri, Sep 16, 2016 at 2:56 PM, Stephen Lewis  wrote:
>
> > Hello,
> >
> > I've tried this on both solr 6.1 and 6.2, with the same result. You are
> > right that the collections API offering collection level backup/restore
> > from remote server is a new feature.
> >
> > After some more experimentation, I am fairly sure that this is a bug
> which
> > is specific to the leaders in backup restore. After I ran a command to
> > restore a backup of the collection "foo" (which has maxShardsPerNode set
> to
> > 1 as well) with a replication factor of 2, I see consistently that the
> > followers (replica > 1) are correctly distributed, but all of the leaders
> > are brought up hosted on one shard.
> >
> > *Repro*
> >
> > *create *
> > http://solr.test:8983/solr/admin/collections?action=
> > CREATE=foo=3=1
> > configName=test-one
> > (after creation, all shards are on different nodes as expected)
> >
> > *backup*
> > http://solr.test:8983/solr/admin/collections?action=
> > BACKUP=foo-2=foo=foo-2
> >
> > *delete*
> > http://solr.test:8983/solr/admin/collections?action=DELETE=foo
> >
> > *restore*
> > Result: All leaders are hosted on node, followers are spread about.
> >
> >  {
> >   "responseHeader" : { "status" : 0,"QTime" : 7},
> >   "cluster" : {
> > "collections" : {
> >   "foo" : {
> > "replicationFactor" : "2",
> > "shards" : {
> >   "shard2" : {
> > "range" : "d555-2aa9",
> > "state" : "active",
> > "replicas" : {
> >   "core_node1" : {
> > "core" : "foo_shard2_replica0",
> > "base_url" : "http://IP1:8983/solr;,
> > "node_name" : "IP1:8983_solr",
> > "state" : "active",
> > "leader" : "true"
> >   },
> >   "core_node4" : {
> > "core" : "foo_shard2_replica1",
> > "base_url" : "http://IP2:8983/solr;,
> > "node_name" : "IP2:8983_solr",
> > "state" : "recovering"
> >   }
> > }
> >   },
> >   "shard3" : {
> > "range" : "2aaa-7fff",
> > "state" : "active",
> > "replicas" : {
> >   "core_node2" : {
> > "core" : "foo_shard3_replica0",
> > "base_url" : "http://IP1:8983/solr;,
> > "node_name" : "IP1:8983_solr",
> > "state" : "active",
> > "leader" : "true"
> >   },
> >   "core_node5" : {
> > "core" : "foo_shard3_replica1",
> > "base_url" : "http://IP3:8983/solr;,
> > "node_name" : "IP3:8983_solr",
> > "state" : "recovering"
> >   }
> > }
> >   },
> >   "shard1" : {
> > "range" : "8000-d554",
> > "state" : "active",
> > "replicas" : {
> >   "core_node3" : {
> > "core" : "foo_shard1_replica0",
> > "base_url" : "http://IP1:8983/solr;,
> > "node_name" : "IP1:8983_solr",
> > "state" : "active",
> > "leader" : "true"
> >   },
> >   "core_node6" : {
> > "core" : "foo_shard1_replica1",
> > "base_url" : "http://IP4:8983/solr;,
> > "node_name" : "IP4:8983_solr",
> > "state" : "recovering"
> >   }
> > }
> >   }
> > },
> > "router" : {
> >   "name" : "compositeId"
> > },
> > "maxShardsPerNode" : "1",
> > "autoAddReplicas" : "false",
> > "znodeVersion" : 204,
> > "configName" : "test-one"
> >   }
> > },
> > "properties" : {
> >   "location" : "/mnt/solr_backups"
> > },
> > "live_nodes" : [
> >   "IP5:8983_solr",
> >   "IP3:8983_solr",
> >   "IP6:8983_solr",
> >   "IP4:8983_solr",
> >   "IP7:8983_solr",
> >   "IP1:8983_solr",
> >   "IP8:8983_solr",
> >   "IP9:8983_solr",
> >   "IP2:8983_solr"]
> >   }
> > }
> >
> >
> > On Fri, Sep 16, 2016 at 2:07 PM, Reth RM  wrote:
> >
> > > Which version of solr? Afaik, until 6.1, solr backup and restore
> command
> > > apis required to do separate backup for each shard, and then restore in
> > > similar lines( both go for each). 6.1 version seems to have new feature
> > of
> > > backing up entire collection records and then restoring it back to new
> > > collection setup(did not try yet).
> > >

Re: [Rerank Query] Distributed search + pagination

[Joel Bernstein]

Alessandro, I'll be doing some testing with the re-ranker as part of
SOLR-9403 for Solr 6.3. I'll see if I can better understand the issue
you're bringing up during the testing. I'll report back to this thread
after I've done some testing.

Joel Bernstein
http://joelsolr.blogspot.com/

On Fri, Sep 16, 2016 at 11:17 AM, Alessandro Benedetti <
abenede...@apache.org> wrote:

> In addition to that, I think the only way to solve this is to rely on the
> aggregator node to actually re-rank after having aggregated.
>
> Cheer
>
> On Fri, Sep 9, 2016 at 11:48 PM, Alessandro Benedetti <
> abenede...@apache.org
> > wrote:
>
> > Let me explain further,
> > let's assume a simple case when we have 2 shards.
> > ReRankDocs =10 , rows=10 .
> >
> > Correct me if I am wrong Joel,
> > What we would like :
> > 1 page : top 10 re-scored
> > 2 page: remaining 10 re-scored
> > From page 3 the original scored docs.
> > This is what is happening in a single sol instance if we put reRankDocs
> to
> > 20.
> >
> > Let's see with sharing :
> > To get the first page we get top 10 ( re-scored) from shard1 and top 10
> > reranked for shard 2.
> > Then the merged top 10 ( re-scored) will be calculated, and that is the
> > page 1.
> >
> > But when we require the page 2, which means we additionally ask now :
> > 20 docs to shard1, 10 re-scored and 10 not.
> > 20 docs to shard2, 10 re-scored and 10 not.
> > At this point we have 40 docs to merge and rank..
> > The docs with the original score can go at any position ( not necessarily
> > the last 20)
> > In the page 2 we can find potentially docs with the original score.
> > This is even more likely if the scores are on differente scales (e.g. the
> > re-scored 0100 ) .
> >
> > Am I right ?
> > Did I make any wrong assumption so far ?
> >
> > Cheers
> >
> >
> > On Fri, Sep 9, 2016 at 7:47 PM, Joel Bernstein 
> wrote:
> >
> >> I'm not understanding where the inconsistency comes into play.
> >>
> >> The re-ranking occurs on the shards. The aggregator node will be sent
> some
> >> docs that have been re-scored and others that are not. But the sorting
> >> should be the same as someone pages through the result set.
> >>
> >>
> >>
> >> Joel Bernstein
> >> http://joelsolr.blogspot.com/
> >>
> >> On Fri, Sep 9, 2016 at 9:28 AM, Alessandro Benedetti <
> >> abenede...@apache.org>
> >> wrote:
> >>
> >> > Hi guys,
> >> > was just experimenting some reranker with really low number of rerank
> >> docs
> >> > ( 10= pageSize) .
> >> > Let's focus on the distributed enviroment and  the manual sharding
> >> > approach.
> >> >
> >> > Currently what happens is that the reranking task is delivered by the
> >> > shards, they rescore the docs and then send them back to the
> aggregator
> >> > node.
> >> >
> >> > If you want to rerank only few docs ( leaving the others with the
> >> original
> >> > score following), this can be done in a single Solr instance ( the
> >> howmany
> >> > logic manages that in the reranker) .
> >> >
> >> > What happens when you move to a distributed environment ?
> >> > The aggregator will aggregate both rescored and original scored
> >> documents,
> >> > making the final ranking inconsistent.
> >> > In the other hand if we make the rarankingDocs threshold dynamic ( to
> >> adapt
> >> > to start+rows) we can incur in the very annoying issue of having a
> >> document
> >> > sliding through the pages ( visible in the first page , then appearing
> >> > again in the third ect ect).
> >> >
> >> > Any thought ?
> >> >
> >> > Cheers
> >> >
> >> > --
> >> > --
> >> >
> >> > Benedetti Alessandro
> >> > Visiting card : http://about.me/alessandro_benedetti
> >> >
> >> > "Tyger, tyger burning bright
> >> > In the forests of the night,
> >> > What immortal hand or eye
> >> > Could frame thy fearful symmetry?"
> >> >
> >> > William Blake - Songs of Experience -1794 England
> >> >
> >>
> >
> >
> >
> > --
> > --
> >
> > Benedetti Alessandro
> > Visiting card : http://about.me/alessandro_benedetti
> >
> > "Tyger, tyger burning bright
> > In the forests of the night,
> > What immortal hand or eye
> > Could frame thy fearful symmetry?"
> >
> > William Blake - Songs of Experience -1794 England
> >
>
>
>
> --
> --
>
> Benedetti Alessandro
> Visiting card : http://about.me/alessandro_benedetti
>
> "Tyger, tyger burning bright
> In the forests of the night,
> What immortal hand or eye
> Could frame thy fearful symmetry?"
>
> William Blake - Songs of Experience -1794 England
>

RE: script to get core num docs

[Kris Musshorn]

Thanks David.. got it working

-Original Message-
From: David Santamauro [mailto:david.santama...@gmail.com] 
Sent: Monday, September 19, 2016 11:55 AM
To: solr-user@lucene.apache.org
Cc: david.santama...@gmail.com
Subject: Re: script to get core num docs


https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API

wget -O- -q \
 
'/admin/cores?action=STATUS=coreName=json=true' 
\

   | grep numDocs

//


/admin/cores?action=STATUS=alexandria_shard2_replica1=json=1'|grep
 
numDocs|cut -f2 -d':'|

On 09/19/2016 11:22 AM, KRIS MUSSHORN wrote:
> How can i get the count of docs from a core with bash?
> Seems like I have to call Admin/Luke but cant find any specifics.
> Thanks
> Kris
>

Re: Solr DateRange Query with AND and different op types

[Sandeep Khanzode]

Hi, Can someone please reply to my query? Let me know if it is not 
understandable. Thanks.
SRK 

On Monday, September 19, 2016 6:00 PM, Sandeep Khanzode 
 wrote:
 

 Hi,
Can I not query like this?
{!field f=schedule1 op=Contains}[1988-10-22T18:30:00Z TO *] AND 
-schedule3:[1988-10-22T18:30:00Z TO *] AND -schedule2:[1988-10-22T18:30:00Z TO 
*] I keep getting parsing and date math related errors.
If I change it to ...schedule1:[1988-10-22T18:30:00Z TO *] AND 
-schedule3:[1988-10-22T18:30:00Z TO *] AND -schedule2:[1988-10-22T18:30:00Z TO 
*]
... this works. But then I obviously have the functionality wrong (intersects 
is the default).
Can I not mix and match multiple op types (like contains, within, intersects) 
in a AND/OR joined query?
SRK

   

Re: request SOLR - spatial field with Intersect and Contains functions

[David Smiley]

Hi Leo,

You should use two spatial fields for this -- one is for an indexed
Box/Envelope, and another for an indexed LineString.  The indexed box
should use either BBoxField or RptWithGeometrySpatialField, and the
LineString field should use RptWithGeometrySpatialField.   If you have an
older installation 5.x version, RptWithGeometrySpatialField may not be
available in which case settle
for solr.SpatialRecursivePrefixTreeFieldType.  When you do a search, it'd
be a search for one field OR the other with the requirements you have for
each.

~ David

On Mon, Sep 19, 2016 at 8:48 AM Leo BRUVRY-LAGADEC <
leo.bruvry.laga...@partenaire-exterieur.ifremer.fr> wrote:

> Hi,
>
> I am trying spatial search in SOLR 5.0 and I don't know how to implement
> a solution for the problem I will try to explain.
>
> On a SOLR server I have indexed a collection of objects that contains
> spacial field :
>
>  multiValued="true" />
>  class="solr.SpatialRecursivePrefixTreeFieldType"
> geo="true"
> distErrPct="0.025"
> maxDistErr="0.09"
> distanceUnits="degrees" />
>
> The spatial data indexed in the field named "geo" can be ENVELOPE or
> LINESTRING :
>
> LINESTRING(-4.6837 48.5792, -4.6835 48.5788, -4.684
> 48.5788, -4.6832 48.579, -4.6837 48.5792, -4.6188 48.6265, -4.6122
> 48.63, -4.615 48.6258, -4.6125 48.6215, -4.6112 48.6218)
>
> or
>
> ENVELOPE(-5.0, -4.0, 49.0, 48.0)
>
> Actually in my application, when I do a SOLR request to get objects that
> are in a spatial area, I do something like this :
>
> q=:=(geo:"Intersects(ENVELOPE(-116.894531, 107.402344, 57.433227,
> -42.146973))")
>
> But I want to change how it work. Now, when the geo field contain an
> ENVELOPE I want to do an CONTAINS request and when it contain a
> LINESTRING I want to do an INTERSECTS request.
>
> example :
>
> If geo = ENVELOPE then q=*:*=(geo:"Contains(ENVELOPE(-116.894531,
> 107.402344, 57.433227, -42.146973))")
>
> If geo = LINESTRING then q=*:*=(geo:"Intersects(ENVELOPE(-116.894531,
> 107.402344, 57.433227, -42.146973))")
>
> How can my application know if the field contain ENVELOPE or LINESTRING ?
>
> Any idea can this be done ?
>
> Best reguards,
> Leo.
>
-- 
Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
http://www.solrenterprisesearchserver.com

Re: Tutorial not working for me

[Steve Rowe]

For now, I was thinking of making it reflect current reality as much as 
possible, without changing coverage.

--
Steve
www.lucidworks.com

> On Sep 19, 2016, at 1:13 PM, Alexandre Rafalovitch  wrote:
> 
> Whatever works. If JIRA, SOLR-6871 is probably a reasonable place.
> Depends on the scope of "updating" you want to do.
> 
> Regards,
>   Alex.
> 
> Newsletter and resources for Solr beginners and intermediates:
> http://www.solr-start.com/
> 
> 
> On 20 September 2016 at 00:02, Steve Rowe  wrote:
>> Hi Alex,
>> 
>> Sure - I assume you mean independently from SOLR-9526 and SOLR-6871?
>> 
>> --
>> Steve
>> www.lucidworks.com
>> 
>>> On Sep 19, 2016, at 12:40 PM, Alexandre Rafalovitch  
>>> wrote:
>>> 
>>> On 19 September 2016 at 23:37, Steve Rowe  wrote:
 I’m going to start working on updating the quick start tutorial - nobody 
 has updated it since 5.0 AFAICT.
>>> 
>>> Is that something that's worth discussing in a group/JIRA/etc?
>>> 
>>> Regards,
>>>  Alex.
>>> 
>>> 
>>> Newsletter and resources for Solr beginners and intermediates:
>>> http://www.solr-start.com/
>> 

Re: Tutorial not working for me

[Alexandre Rafalovitch]

And bringing shipped and website version in sync I assume. Ok, I'll be
happy to watch whatever issue that happens in and proof-read when it
is done.

Regards,
   Alex.

Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/


On 20 September 2016 at 00:16, Steve Rowe  wrote:
> For now, I was thinking of making it reflect current reality as much as 
> possible, without changing coverage.
>
> --
> Steve
> www.lucidworks.com
>
>> On Sep 19, 2016, at 1:13 PM, Alexandre Rafalovitch  
>> wrote:
>>
>> Whatever works. If JIRA, SOLR-6871 is probably a reasonable place.
>> Depends on the scope of "updating" you want to do.
>>
>> Regards,
>>   Alex.
>> 
>> Newsletter and resources for Solr beginners and intermediates:
>> http://www.solr-start.com/
>>
>>
>> On 20 September 2016 at 00:02, Steve Rowe  wrote:
>>> Hi Alex,
>>>
>>> Sure - I assume you mean independently from SOLR-9526 and SOLR-6871?
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
 On Sep 19, 2016, at 12:40 PM, Alexandre Rafalovitch  
 wrote:

 On 19 September 2016 at 23:37, Steve Rowe  wrote:
> I’m going to start working on updating the quick start tutorial - nobody 
> has updated it since 5.0 AFAICT.

 Is that something that's worth discussing in a group/JIRA/etc?

 Regards,
  Alex.

 
 Newsletter and resources for Solr beginners and intermediates:
 http://www.solr-start.com/
>>>
>

Re: Tutorial not working for me

[Alexandre Rafalovitch]

Whatever works. If JIRA, SOLR-6871 is probably a reasonable place.
Depends on the scope of "updating" you want to do.

Regards,
   Alex.

Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/


On 20 September 2016 at 00:02, Steve Rowe  wrote:
> Hi Alex,
>
> Sure - I assume you mean independently from SOLR-9526 and SOLR-6871?
>
> --
> Steve
> www.lucidworks.com
>
>> On Sep 19, 2016, at 12:40 PM, Alexandre Rafalovitch  
>> wrote:
>>
>> On 19 September 2016 at 23:37, Steve Rowe  wrote:
>>> I’m going to start working on updating the quick start tutorial - nobody 
>>> has updated it since 5.0 AFAICT.
>>
>> Is that something that's worth discussing in a group/JIRA/etc?
>>
>> Regards,
>>   Alex.
>>
>> 
>> Newsletter and resources for Solr beginners and intermediates:
>> http://www.solr-start.com/
>

Re: Tutorial not working for me

[Steve Rowe]

Hi Alex,

Sure - I assume you mean independently from SOLR-9526 and SOLR-6871?

--
Steve
www.lucidworks.com

> On Sep 19, 2016, at 12:40 PM, Alexandre Rafalovitch  
> wrote:
> 
> On 19 September 2016 at 23:37, Steve Rowe  wrote:
>> I’m going to start working on updating the quick start tutorial - nobody has 
>> updated it since 5.0 AFAICT.
> 
> Is that something that's worth discussing in a group/JIRA/etc?
> 
> Regards,
>   Alex.
> 
> 
> Newsletter and resources for Solr beginners and intermediates:
> http://www.solr-start.com/

Re: Boost according to values

[Walter Underwood]

1. Use edismax and the boost parameter. Multiplicative boosting works much, 
much better than the additive boost used in dismax.

2. Use a log-scaled popularity value. If you know popularity is always greater 
than 1, use “1 + log(popularity)”. It is a bit safer to use “1 + log(max(1, 
popularity))”.

3. Multiple that value by a weight to make it a tie-breaker. If two items have 
the same title (or text), you want the more popular one first. But you rarely 
want a different result boosted above a match. No matter how popular the movie 
“Twilight” is, it should not rank above “Twilight Zone” for the query “twilight 
zone”.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)


> On Sep 18, 2016, at 11:49 PM, Rajendra Gaikwad  wrote:
> 
> Hi Midas,
> I am sure,even though you have results with constant relavance, sorting
> will give you expected results.
> Anyway there is parameter bf in dismax parser. Add parameter
> bf=field(popularity) to query, It is similar to boost items by value in
> popularity field. hence ultimately higher popularity items occurs on top.
> Add parameter to your query bf=field(popularity)=edismax
> 
> 
> Thanks,
> Rajendra Gaikwad
> 
> On Mon, Sep 19, 2016, 11:55 AM Midas A  wrote:
> 
>> my use case do not suggest me to sort  . i have set of data with same
>> relevance.
>> 
>> what should be query in that case  .
>> 
>> On Mon, Sep 19, 2016 at 11:51 AM, Rajendra Gaikwad 
>> wrote:
>> 
>>> Hi Midas,
>>> 
>>> Sort search results on popularity field by desc order.
>>> E.g popularity is field in the index which stores popularity information.
>>> 
>>> http://localhost:8983/solr/mycollection/select?q=*:*=popularity
>> desc
>>> 
>>> Thanks,
>>> Rajendra Gaikwad
>>> Please execuse typo
>>> 
>>> 
>>> 
>>> On Mon, Sep 19, 2016, 11:36 AM Midas A  wrote:
>>> 
 i have n items in my search result  with popularity (1,2,3,4n) . I
>>> want
 higher popularity item should come first then next popularity item
 
 
 say for example
 a) item with popularity n,
 b) item with popularity n -1,
 c) item with popularity n -2,
 d) item with popularity n - 3,
 e) item with popularity n - 4,
 f) item with popularity n - 5,
 
 
 y) item with popularity 2,
 z) item with popularity 1,
 
 
 what should be my query  if relevance for items are constant
 
>>> --
>>> 
>>> sent from mobile, execuse typo
>>> 
>> 
> -- 
> 
> sent from mobile, execuse typo

Re: Tutorial not working for me

[Alexandre Rafalovitch]

On 19 September 2016 at 23:37, Steve Rowe  wrote:
> I’m going to start working on updating the quick start tutorial - nobody has 
> updated it since 5.0 AFAICT.

Is that something that's worth discussing in a group/JIRA/etc?

Regards,
   Alex.


Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/

Re: Tutorial not working for me

[Steve Rowe]

In the data driven configset, autoguessing text fields as the “strings" field 
type is intended to enable faceting.  The catch-all _text_ field enables search 
on all fields, but this may not be a good alternative to fielded search. 

I’m going to start working on updating the quick start tutorial - nobody has 
updated it since 5.0 AFAICT.

--
Steve
www.lucidworks.com

> On Sep 16, 2016, at 8:34 PM, Chris Hostetter  wrote:
> 
> 
> : I apologize if this is a really stupid question. I followed all
> 
> It's not a stupid question, the tutorial is completley broken -- and for 
> that matter, in my opinion, the data_driven_schema_configs used by that 
> tutorial (and recommended for new users) are largely useless for the same 
> underlying reason...
> 
> https://issues.apache.org/jira/browse/SOLR-9526
> 
> Thank you very much for asking about this - hopefully the folks who 
> understand this more (and don't share my opinion that the entire concept 
> of data_driven schemas are a terrible idea) can chime in and explain WTF 
> is going on here)
> 
> 
> -Hoss
> http://www.lucidworks.com/

Solr replication failure then restart.

[Yunee Lee]

Hi, 

I have a solr replication set up from master to slave in legacy ( It's not from 
the solr cloud).
Somehow the first initial replication doesn't finish and when it reaches 99% 
and got the error as following and then restart from the beginning.
I don't know why it is keep retriggering to start the replication over and over.

ERROR
ReplicationHandler
Index fetch failed :org.apache.solr.common.SolrException: Unable to download 
_55sm.si completely. Downloaded 0!=363

Here is the config in the slave. I wonder if solrconfig has any 
misconfiguration. 



startup
commit

0


 
   http://url.com
 00:05:00
   
  

Anyone had a similar experience, please share how to resolve the issue.
Thanks.

Re: [Query Elevation Component] Elevate on collapsed field

[Alessandro Benedetti]

More I investigate the code more I grow sceptical it is feasible at all
with the current architecture 
I will investifgate a bit more.

Cheers

On Mon, Sep 19, 2016 at 10:17 AM, Alessandro Benedetti <
abenede...@apache.org> wrote:

> Hi gents,
> I was thinking to use the query elevation component sequentially to the
> field collapsing.
> This means I want to collapse over a field and then elevate docs for that
> field.
> Correct me if I am wrong, but we don't have this flexibility right now.
>
> I think it is an easy change to give the possibility of having the elevate
> idField parametric.
> By default will be the unique key.
>
> What do you think?
>
> https://issues.apache.org/jira/browse/SOLR-9531
>
> Cheers
>
> --
> --
>
> Benedetti Alessandro
> Visiting card : http://about.me/alessandro_benedetti
>
> "Tyger, tyger burning bright
> In the forests of the night,
> What immortal hand or eye
> Could frame thy fearful symmetry?"
>
> William Blake - Songs of Experience -1794 England
>



-- 
--

Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti

"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"

William Blake - Songs of Experience -1794 England

Re: script to get core num docs

[David Santamauro]

https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API

wget -O- -q \

'/admin/cores?action=STATUS=coreName=json=true' 
\


  | grep numDocs

//


/admin/cores?action=STATUS=alexandria_shard2_replica1=json=1'|grep 
numDocs|cut -f2 -d':'|


On 09/19/2016 11:22 AM, KRIS MUSSHORN wrote:

How can i get the count of docs from a core with bash?
Seems like I have to call Admin/Luke but cant find any specifics.
Thanks
Kris

Re: script to get core num docs

[Walter Underwood]

Do a search. The URL will looks something like this:

   /solr/core-name/select?q=*:*=0=json

That will return something like this:

   
{"responseHeader":{"status":0,"QTime":1},"response":{"numFound":287176,"start":0,"docs":[]}}

Filter that response through this:

   jq .response.numFound

And you’ll get the number of documents in the core.

Alternatively, the info is in the admin status API.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)


> On Sep 19, 2016, at 8:30 AM, John Bickerstaff  
> wrote:
> 
> I would imagine there's an http call that would get it and you could call
> cURL in your bash script...  I don't know the URL parameters off hand
> however...
> 
> On Mon, Sep 19, 2016 at 9:22 AM, KRIS MUSSHORN 
> wrote:
> 
>> How can i get the count of docs from a core with bash?
>> Seems like I have to call Admin/Luke but cant find any specifics.
>> Thanks
>> Kris
>> 

Re: script to get core num docs

[Alexandre Rafalovitch]

If you see it in the Admin UI (and you do), you can get it from the
web browser's Developer interface but just reloading the page and
watching for traffic.

Is that enough for you to discover what you need or do you need more
specific help?

Regards,
   Alex.

Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/


On 19 September 2016 at 22:22, KRIS MUSSHORN  wrote:
> How can i get the count of docs from a core with bash?
> Seems like I have to call Admin/Luke but cant find any specifics.
> Thanks
> Kris

Re: slow updates/searches

[Erick Erickson]

Hmmm, not sure, and also not sure what to suggest next. QTimes
measure only the search time, not, say, time waiting for the request to get
serviced.

I'm afraid the next suggestion is to throw a profiler at it 'cause nothing jumps
out at me..'

Best,
Erick

On Fri, Sep 16, 2016 at 10:23 AM, Rallavagu  wrote:
> Comments in line...
>
> On 9/16/16 10:15 AM, Erick Erickson wrote:
>>
>> Well, the next thing I'd look at is CPU activity. If you're flooding the
>> system
>> with updates there'll be CPU contention.
>
>
> Monitoring does not suggest any high CPU but as you can see from vmstat
> output "user" cpu is a bit high during updates that are taking time (34
> user, 65 idle).
>
>>
>> And there are a number of things you can do that make updates in
>> particular
>> much less efficient, from committing very frequently (sometimes combined
>> with excessive autowarm parameters) and the like.
>
>
> softCommit is set to 10 minutes, autowarm count is set to 0 and commit is
> set to 15 sec for NRT.
>
>>
>> There are a series of ideas that might trigger an "aha" moment:
>> https://wiki.apache.org/solr/SolrPerformanceFactors
>
>
> Reviewed this document and made few changes accordingly a while ago.
>>
>>
>> But the crude measure is just to look at CPU usage when updates happen, or
>> just before. Are you running hot with queries alone then add an update
>> burden?
>
>
> Essentially, it is high QTimes for queries got me looking into logs, system
> etc and I could correlate updates slowness and searching slowness. Some
> other time QTimes go high is right after softCommit which is expected.
>
> Wondering what causes update threads wait and if it has any impact on search
> at all. I had couple of more CPUs added but I still see similar behavior.
>
> Thanks.
>
>
>>
>> Best,
>> Erick
>>
>> On Fri, Sep 16, 2016 at 9:19 AM, Rallavagu  wrote:
>>>
>>> Erick,
>>>
>>> Was monitoring GC activity and couldn't align GC pauses to this behavior.
>>> Also, the vmstat shows no swapping or cpu I/O wait. However, whenever I
>>> see
>>> high update response times (corresponding high QTimes for searches)
>>> vmstat
>>> shows as series of number of "waiting to runnable" processes in "r"
>>> column
>>> of "procs" section.
>>>
>>>
>>> https://dl.dropboxusercontent.com/u/39813705/Screen%20Shot%202016-09-16%20at%209.05.51%20AM.png
>>>
>>> procs ---memory-- ---swap--
>>> -io -system-- cpu -timestamp-
>>>  r  b swpd freeinact   active   si   so bi
>>> bo
>>> in   cs  us  sy  id  wa  st CDT
>>>  2  071068 18688496  2526604 2420444000 0
>>> 0
>>> 1433  462  27   1  73   0   0 2016-09-16 11:02:32
>>>  1  071068 18688180  2526600 2420456800 0
>>> 0
>>> 1388  404  26   1  74   0   0 2016-09-16 11:02:33
>>>  1  071068 18687928  2526600 2420456800 0
>>> 0
>>> 1354  401  25   0  75   0   0 2016-09-16 11:02:34
>>>  1  071068 18687800  2526600 2420457200 0
>>> 0
>>> 1311  397  25   0  74   0   0 2016-09-16 11:02:35
>>>  1  071068 18687164  2527116 2420484400 0
>>> 0
>>> 1770  702  31   1  69   0   0 2016-09-16 11:02:36
>>>  1  071068 18686944  2527108 2420490800 0
>>> 52
>>> 1266  421  26   0  74   0   0 2016-09-16 11:02:37
>>> 12  171068 18682676  2528560 2420711600 0
>>> 280
>>> 2388  934  34   1  65   0   0 2016-09-16 11:02:38
>>>  2  171068 18651340  2530820 2423336800 0
>>> 1052
>>> 10258 5696  82   5  13   0   0 2016-09-16 11:02:39
>>>  5  071068 18648600  2530112 2423506000 0
>>> 1988
>>> 7261 3644  84   2  13   1   0 2016-09-16 11:02:40
>>>  9  171068 18647804  2530580 2423607600 0
>>> 1688
>>> 7031 3575  84   2  13   1   0 2016-09-16 11:02:41
>>>  1  071068 18647628  2530364 2423625600 0
>>> 680
>>> 7065 4463  61   3  35   1   0 2016-09-16 11:02:42
>>>  1  071068 18646344  2531204 2423653600 0
>>> 44
>>> 6422 4922  35   3  63   0   0 2016-09-16 11:02:43
>>>  2  071068 18644460  2532196 2423744000 0
>>> 0
>>> 6561 5056  25   3  72   0   0 2016-09-16 11:02:44
>>>  0  071068 18661900  2531724 2421876400 0
>>> 0
>>> 7312 10050  11   3  86   0   0 2016-09-16 11:02:45
>>>  2  071068 18649400  2532228 2422980000 0
>>> 0
>>> 7211 6222  34   3  63   0   0 2016-09-16 11:02:46
>>>  0  071068 18648280  2533440 2423030000 0
>>> 108
>>> 3936 3381  20   1  79   0   0 2016-09-16 11:02:47
>>>  0  071068 18648156  2533212 2423068400 0
>>> 12
>>> 1279 1681   2   0  97   0   0 2016-09-16 11:02:48
>>>
>>>
>>> Captured stack trace including timing 

Re: script to get core num docs

[John Bickerstaff]

I would imagine there's an http call that would get it and you could call
cURL in your bash script...  I don't know the URL parameters off hand
however...

On Mon, Sep 19, 2016 at 9:22 AM, KRIS MUSSHORN 
wrote:

> How can i get the count of docs from a core with bash?
> Seems like I have to call Admin/Luke but cant find any specifics.
> Thanks
> Kris
>

Re: In cloud mode, using implicit router. Leader changed, not available to index data, and no error occurred.

[Erick Erickson]

Are all the documents in the collection? By using implicit router, you are
assuming control of what shard each document ends up on. So my
guess is that you are not routing the docs to each shard.

If you want Solr to automatically assign the shard to a doc, you should
be using the default compositeId routing scheme.

If you index docs and not all of them are somewhere in the collection,
that's a problem, assuming you are routing them properly when using
the implicit router.

Best,
Erick

On Sun, Sep 18, 2016 at 8:04 PM, Jerome Yang  wrote:
> Hi all,
>
> The situation is:
> Three hosts, host1, host2, host3. Solr version 6.1 in cloud mode. 8 solr
> nodes on each host.
>
> Create a collection using implicit router. Execute index and delete index.
> The collection works fine.
> Then kill 3 nodes, some of shards change leader.
> Then index data to new leaders of shards, and commit. But some of shards
> still has 0 documents. And no error occurred.
> By checking the log on that leader replica, it did receive the update
> request and processed. No error found in the log.
>
> After restart all nodes, everything works fine.
>
> This is a serious bug I think.
> Can you confirm it's a bug or not?
>
> Regards,
> Jerome

script to get core num docs

[KRIS MUSSHORN]

How can i get the count of docs from a core with bash? 
Seems like I have to call Admin/Luke but cant find any specifics. 
Thanks 
Kris 

Re: one of the shard delay in response in Solr cluster

[Shawn Heisey]

On 9/19/2016 12:58 AM, Mugeesh Husain wrote:
> I have 3 shard, each of shard with 3 servers in solrcloud, if we fired
> the query in solr, we woudl get the result from these shard data, if
> one of the shard have delay in response, then how to identify which
> shard is not giving properly response time(or delay reponse or some
> issue etc). I am looking for debugging the shard performance or how to
> check each performance individually 

If you include a shards.info parameter with the request, set to true,
the response should contain timing and count information about each
shard consulted for the query.

Thanks,
Shawn

request SOLR - spatial field with Intersect and Contains functions

[Leo BRUVRY-LAGADEC]

Hi,

I am trying spatial search in SOLR 5.0 and I don't know how to implement 
a solution for the problem I will try to explain.


On a SOLR server I have indexed a collection of objects that contains 
spacial field :


multiValued="true" />
class="solr.SpatialRecursivePrefixTreeFieldType"

   geo="true"
   distErrPct="0.025"
   maxDistErr="0.09"
   distanceUnits="degrees" />

The spatial data indexed in the field named "geo" can be ENVELOPE or 
LINESTRING :


LINESTRING(-4.6837 48.5792, -4.6835 48.5788, -4.684 
48.5788, -4.6832 48.579, -4.6837 48.5792, -4.6188 48.6265, -4.6122 
48.63, -4.615 48.6258, -4.6125 48.6215, -4.6112 48.6218)


or

ENVELOPE(-5.0, -4.0, 49.0, 48.0)

Actually in my application, when I do a SOLR request to get objects that 
are in a spatial area, I do something like this :


q=:=(geo:"Intersects(ENVELOPE(-116.894531, 107.402344, 57.433227, 
-42.146973))")


But I want to change how it work. Now, when the geo field contain an 
ENVELOPE I want to do an CONTAINS request and when it contain a 
LINESTRING I want to do an INTERSECTS request.


example :

If geo = ENVELOPE then q=*:*=(geo:"Contains(ENVELOPE(-116.894531, 
107.402344, 57.433227, -42.146973))")


If geo = LINESTRING then q=*:*=(geo:"Intersects(ENVELOPE(-116.894531, 
107.402344, 57.433227, -42.146973))")


How can my application know if the field contain ENVELOPE or LINESTRING ?

Any idea can this be done ?

Best reguards,
Leo.

Solr DateRange Query with AND and different op types

[Sandeep Khanzode]

Hi,
Can I not query like this?
{!field f=schedule1 op=Contains}[1988-10-22T18:30:00Z TO *] AND 
-schedule3:[1988-10-22T18:30:00Z TO *] AND -schedule2:[1988-10-22T18:30:00Z TO 
*] I keep getting parsing and date math related errors.
If I change it to ...schedule1:[1988-10-22T18:30:00Z TO *] AND 
-schedule3:[1988-10-22T18:30:00Z TO *] AND -schedule2:[1988-10-22T18:30:00Z TO 
*]
... this works. But then I obviously have the functionality wrong (intersects 
is the default).
Can I not mix and match multiple op types (like contains, within, intersects) 
in a AND/OR joined query?
SRK

[Query Elevation Component] Elevate on collapsed field

[Alessandro Benedetti]

Hi gents,
I was thinking to use the query elevation component sequentially to the
field collapsing.
This means I want to collapse over a field and then elevate docs for that
field.
Correct me if I am wrong, but we don't have this flexibility right now.

I think it is an easy change to give the possibility of having the elevate
idField parametric.
By default will be the unique key.

What do you think?

https://issues.apache.org/jira/browse/SOLR-9531

Cheers

-- 
--

Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti

"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"

William Blake - Songs of Experience -1794 England

Fwd: solr AND riche Data

[kostali hassan]

I index rich data in solr 5.4.1 and I use solarium to search terms in index
at the field text ;how to display for each term hes
category,synonym,similair result,suggester,autocomplet...
for  exemple the term to search is q=java
similair term is: javascript,javaEE..
framworks:Hibernate,Jboss,strut,spring...
category:Informatique
NO synonym
I deevloppe this interface in php using the framework cakephp
for each document in the index I have to fields: id the path of each
files(msword and pdf) AND the field  text.
What is the best approch to build an interface displaying all information
for each term .

one of the shard delay in response in Solr cluster

[Mugeesh Husain]

Hi,

I have 3 shard, each of shard with 3 servers in solrcloud, if we fired the
query in solr, we woudl get the result from these shard data, if one of the
shard have delay in response, then how to identify which shard is not giving
properly response time(or delay reponse or some issue etc).


I am looking for debugging the shard performance or how to check each
performance  individually


Thanks



--
View this message in context: 
http://lucene.472066.n3.nabble.com/one-of-the-shard-delay-in-response-in-Solr-cluster-tp4296673.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Boost according to values

[Rajendra Gaikwad]

Hi Midas,
I am sure,even though you have results with constant relavance, sorting
will give you expected results.
Anyway there is parameter bf in dismax parser. Add parameter
bf=field(popularity) to query, It is similar to boost items by value in
popularity field. hence ultimately higher popularity items occurs on top.
Add parameter to your query bf=field(popularity)=edismax


Thanks,
Rajendra Gaikwad

On Mon, Sep 19, 2016, 11:55 AM Midas A  wrote:

> my use case do not suggest me to sort  . i have set of data with same
> relevance.
>
> what should be query in that case  .
>
> On Mon, Sep 19, 2016 at 11:51 AM, Rajendra Gaikwad 
> wrote:
>
> > Hi Midas,
> >
> > Sort search results on popularity field by desc order.
> > E.g popularity is field in the index which stores popularity information.
> >
> > http://localhost:8983/solr/mycollection/select?q=*:*=popularity
> desc
> >
> > Thanks,
> > Rajendra Gaikwad
> > Please execuse typo
> >
> >
> >
> > On Mon, Sep 19, 2016, 11:36 AM Midas A  wrote:
> >
> > > i have n items in my search result  with popularity (1,2,3,4n) . I
> > want
> > > higher popularity item should come first then next popularity item
> > >
> > >
> > > say for example
> > > a) item with popularity n,
> > > b) item with popularity n -1,
> > > c) item with popularity n -2,
> > > d) item with popularity n - 3,
> > > e) item with popularity n - 4,
> > > f) item with popularity n - 5,
> > > 
> > > 
> > > y) item with popularity 2,
> > > z) item with popularity 1,
> > >
> > >
> > > what should be my query  if relevance for items are constant
> > >
> > --
> >
> > sent from mobile, execuse typo
> >
>
-- 

sent from mobile, execuse typo

Re: Boost according to values

[Midas A]

my use case do not suggest me to sort  . i have set of data with same
relevance.

what should be query in that case  .

On Mon, Sep 19, 2016 at 11:51 AM, Rajendra Gaikwad 
wrote:

> Hi Midas,
>
> Sort search results on popularity field by desc order.
> E.g popularity is field in the index which stores popularity information.
>
> http://localhost:8983/solr/mycollection/select?q=*:*=popularity desc
>
> Thanks,
> Rajendra Gaikwad
> Please execuse typo
>
>
>
> On Mon, Sep 19, 2016, 11:36 AM Midas A  wrote:
>
> > i have n items in my search result  with popularity (1,2,3,4n) . I
> want
> > higher popularity item should come first then next popularity item
> >
> >
> > say for example
> > a) item with popularity n,
> > b) item with popularity n -1,
> > c) item with popularity n -2,
> > d) item with popularity n - 3,
> > e) item with popularity n - 4,
> > f) item with popularity n - 5,
> > 
> > 
> > y) item with popularity 2,
> > z) item with popularity 1,
> >
> >
> > what should be my query  if relevance for items are constant
> >
> --
>
> sent from mobile, execuse typo
>

Re: Boost according to values

[Rajendra Gaikwad]

Hi Midas,

Sort search results on popularity field by desc order.
E.g popularity is field in the index which stores popularity information.

http://localhost:8983/solr/mycollection/select?q=*:*=popularity desc

Thanks,
Rajendra Gaikwad
Please execuse typo



On Mon, Sep 19, 2016, 11:36 AM Midas A  wrote:

> i have n items in my search result  with popularity (1,2,3,4n) . I want
> higher popularity item should come first then next popularity item
>
>
> say for example
> a) item with popularity n,
> b) item with popularity n -1,
> c) item with popularity n -2,
> d) item with popularity n - 3,
> e) item with popularity n - 4,
> f) item with popularity n - 5,
> 
> 
> y) item with popularity 2,
> z) item with popularity 1,
>
>
> what should be my query  if relevance for items are constant
>
-- 

sent from mobile, execuse typo

Re: Boost according to values

[Rajendra Gaikwad]

Hi Midas,

Sort search results on popularity field by desc order.
E.g popularity is field in the index which stores  popularity information.

http://localhost:8983/solr/mycollection/select?q=*:*=popularity desc

Thanks,
Rajendra Gaikwad
Please execuse typo

On Mon, Sep 19, 2016, 11:36 AM Midas A  wrote:

> i have n items in my search result  with popularity (1,2,3,4n) . I want
> higher popularity item should come first then next popularity item
>
>
> say for example
> a) item with popularity n,
> b) item with popularity n -1,
> c) item with popularity n -2,
> d) item with popularity n - 3,
> e) item with popularity n - 4,
> f) item with popularity n - 5,
> 
> 
> y) item with popularity 2,
> z) item with popularity 1,
>
>
> what should be my query  if relevance for items are constant
>
-- 

sent from mobile, execuse typo

Boost according to values

[Midas A]

i have n items in my search result  with popularity (1,2,3,4n) . I want
higher popularity item should come first then next popularity item


say for example
a) item with popularity n,
b) item with popularity n -1,
c) item with popularity n -2,
d) item with popularity n - 3,
e) item with popularity n - 4,
f) item with popularity n - 5,


y) item with popularity 2,
z) item with popularity 1,


what should be my query  if relevance for items are constant