Average term position
I hope someone could give me some direction on what to read in order to implement the following: Given a query and a term, how could I calculate the average position of the term within every document in the resultset and return that average? I am looking for the fastest (performance wise) solution and willing to extend the solr functionality if needed Following that, I would need to calculate the average position of a term across all documents in the query resultset. With that, I do not need to return the documents themselves to the client - just the average term position. Thanks Saar
Solr - what's the next big thing?
If I am not mistaken the most impressive improvement of Solr 4.0 compared to previous versions was the Solr Cloud architecture. What would be the next big thing in Solr 5.0 ? Saar
Re: Solr - what's the next big thing?
LOL, Jack. I can imagine Otis saying that. Otis, with these marriage, are we going to see map reduce based queries? On Oct 25, 2013 10:03 PM, "Jack Krupansky" wrote: > But a lot of that big yellow elephant stuff is in 4.x anyway. > > (Otis: I was afraid that you were going to say that the next big thing in > Solr is... Elasticsearch!) > > -- Jack Krupansky > > -Original Message- From: Otis Gospodnetic > Sent: Friday, October 25, 2013 2:43 PM > To: solr-user@lucene.apache.org > Subject: Re: Solr - what's the next big thing? > > Saar, > > The marriage with the big yellow elephant is a big deal. It changes the > scale. > > Otis > Solr & ElasticSearch Support > http://sematext.com/ > On Oct 25, 2013 5:32 AM, "Saar Carmi" wrote: > > If I am not mistaken the most impressive improvement of Solr 4.0 compared >> to previous versions was the Solr Cloud architecture. >> >> What would be the next big thing in Solr 5.0 ? >> >> Saar >> >> >
Re: Solr - what's the next big thing?
If I get it right, Solr can store its data files on HDFS but it will not use map reduce to process the data (e.g. evaluating queries). I was wondering whether Solr could utilize the Hadoop job distribution mechanism to utlize resources better. On the otherhand, maybe this is not needed with the availability of Solr Cloud. Bill Bell, could you elaborate about complex object indexing? On Sat, Oct 26, 2013 at 10:04 PM, Otis Gospodnetic < otis.gospodne...@gmail.com> wrote: > Hi, > > On Sat, Oct 26, 2013 at 5:58 AM, Saar Carmi wrote: > > LOL, Jack. I can imagine Otis saying that. > > Funny indeed, but not really. > > > Otis, with these marriage, are we going to see map reduce based > queries? > > Can you please describe what you mean by that? Maybe with an example. > > Thanks, > Otis > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > > > > > On Oct 25, 2013 10:03 PM, "Jack Krupansky" > wrote: > > > >> But a lot of that big yellow elephant stuff is in 4.x anyway. > >> > >> (Otis: I was afraid that you were going to say that the next big thing > in > >> Solr is... Elasticsearch!) > >> > >> -- Jack Krupansky > >> > >> -Original Message- From: Otis Gospodnetic > >> Sent: Friday, October 25, 2013 2:43 PM > >> To: solr-user@lucene.apache.org > >> Subject: Re: Solr - what's the next big thing? > >> > >> Saar, > >> > >> The marriage with the big yellow elephant is a big deal. It changes the > >> scale. > >> > >> Otis > >> Solr & ElasticSearch Support > >> http://sematext.com/ > >> On Oct 25, 2013 5:32 AM, "Saar Carmi" wrote: > >> > >> If I am not mistaken the most impressive improvement of Solr 4.0 > compared > >>> to previous versions was the Solr Cloud architecture. > >>> > >>> What would be the next big thing in Solr 5.0 ? > >>> > >>> Saar > >>> > >>> > >> > -- Saar Carmi Mobile: 054-7782417 Email: saarca...@gmail.com
Re: Parallelizing warmup queries
Otis, This raises a newbie question - How would one know what query is 1-CPU bounded and what is multi-threaded? Saar On Sat, Nov 16, 2013 at 10:28 AM, Otis Gospodnetic < otis.gospodne...@gmail.com> wrote: > Hi, > > It looks like warmup queries execute sequentially. > > Considering servers have N CPU cores these days, would it make sense > to make them (optionally) run in parallel? This should help with > cases where warmup queries are CPU bound by letting Solr use more than > 1 thread and thus more than 1 CPU core. Should I add to JIRA? > > Thanks, > Otis > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > -- Saar Carmi Mobile: 054-7782417 Email: saarca...@gmail.com
