Re: modify query response plugin

2019-08-08 Thread Maria Muslea
rew Carnegie Blvd | 4th floor > Charlotte, NC 28263 > Tel: 704.988.4508 > Fax: 704.988.4907 > bmo...@tiaa.org > > > -Original Message- > From: Maria Muslea > Sent: Thursday, August 8, 2019 1:28 PM > To: solr-user@lucene.apache.org > Subject: Re: modify quer

Re: modify query response plugin

2019-08-08 Thread Maria Muslea
https://lucidworks.com/post/solr-tagger-improving-relevancy/ > > > On Aug 6, 2019, at 16:04, Maria Muslea wrote: > > > > Hi, > > > > I am trying to implement a plugin that will modify my query response. For > > example, I would like to ex

modify query response plugin

2019-08-06 Thread Maria Muslea
Hi, I am trying to implement a plugin that will modify my query response. For example, I would like to execute a query that will return something like: {... "description":"flights at LAX", "highlight":"airport;11;3" ...} This is information that I have in my document, so I can return it. Now, I

Re: SolrPlugin update existing documents in newSearcher()

2019-05-06 Thread Maria Muslea
hat reads all docs using cursorMark and > indexes them into the new collection. > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > > 2. mai 2019 kl. 19:39 skrev Maria Muslea : > > > > Yes, I will want to also do that, but init

Re: SolrPlugin update existing documents in newSearcher()

2019-05-02 Thread Maria Muslea
being added and > modify them as you wish. > https://lucene.apache.org/solr/guide/7_7/update-request-processors.html > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > > 1. mai 2019 kl. 22:31 skrev Maria Muslea : > >

SolrPlugin update existing documents in newSearcher()

2019-05-01 Thread Maria Muslea
Hi, I have a plugin that extends the AbstractSolrEventListener. I override the newSearcher() method and the plan is to add some extra functionality, namely updating existing documents by setting new values for existing fields as well as adding new fields to the documents. I can see that the

Re: prefix facet performance

2017-04-21 Thread Maria Muslea
I see. Once I specify a prefix the number of terms is MUCH smaller. Thank you again for all your help. Maria On Fri, Apr 21, 2017 at 1:46 PM, Yonik Seeley <ysee...@gmail.com> wrote: > On Fri, Apr 21, 2017 at 4:25 PM, Maria Muslea <maria.mus...@gmail.com> > wr

Re: prefix facet performance

2017-04-21 Thread Maria Muslea
The field is: and using unique() I found that it has 700K+ unique values. The query before (that takes ~10s): wt=json=true=*:*=0=true=concept=A/ the query after (that is almost instant): wt=json=true=*:*=0=true=concept=A/=enum' Maria On Fri, Apr 21, 2017 at 8:59 AM, alessandro.benedetti

Re: prefix facet performance

2017-04-21 Thread Maria Muslea
Actually using facet.method=enum made a HUGE difference even in my case where I have many unique values. I am happy with the query response time now. Is there a way in SOLR to count the unique values for a field? If not, I could run the reindexing and count the unique values while I add them to

Re: prefix facet performance

2017-04-18 Thread Maria Muslea
, Yonik Seeley <ysee...@gmail.com> wrote: > How many unique values in the index? > You could try facet.method=enum > > -Yonik > > > On Tue, Apr 18, 2017 at 8:16 PM, Maria Muslea <maria.mus...@gmail.com> > wrote: > > Hi, > > > > I have ~40K docu

prefix facet performance

2017-04-18 Thread Maria Muslea
Hi, I have ~40K documents in SOLR (not many) and a multivalued facet field that contains at least 2K values per document. The values of the facet field look like: A/B, A/C, A/D, C/E, M/F, etc, and I use facet.prefix. q=*:*=0=true=concept=A/ with "concept" defined as: This generates the

Re: field with stored="false" is still stored

2017-04-17 Thread Maria Muslea
Thank you so much. This is the setting that I was missing. It is working as expected now. Maria On Mon, Apr 17, 2017 at 8:10 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 4/17/2017 4:40 PM, Maria Muslea wrote: > > I just upgraded to SOLR 6.4.1 from SOLR 4.10, and am

Re: field with stored="false" is still stored

2017-04-17 Thread Maria Muslea
have upgraded directly from Solr 4 to Solr 6. > If I'm not wrong, I don't think we can upgrade the index with a direct jump > of 2 version. > > Was the field set to stored="false" before you upgrade? > > Regards, > Edwin > > > > On 18 April 2017 at 06

Re: field with stored="false" is still stored

2017-04-17 Thread Maria Muslea
t I could see which schema it is using? Thank you, Maria On Mon, Apr 17, 2017 at 7:33 PM, Zheng Lin Edwin Yeo <edwinye...@gmail.com> wrote: > Hi Maria, > > From what you mentioned, you have upgraded directly from Solr 4 to Solr 6. > If I'm not wrong, I don't think we can upgr

field with stored="false" is still stored

2017-04-17 Thread Maria Muslea
Hi, I just upgraded to SOLR 6.4.1 from SOLR 4.10, and am having trouble with fields set as stored="false". I edited solrconfig.xml according to the documentation, so I could edit the schema using schema api. true managed-schema I added a field using "Add Field" from the Schema GUI,