Possible bug with AnalyzingInfixLookupFactory, FileDictionaryFactory and Context Filtering

hinkit is a bug. Essentially, context filtering is being applied to a suggester that is backed by a FileDictionaryFactory. According to the docs, this should not happen, and context filters should be ignored. This is my config: location AnalyzingInfixLookupFactory FileDictionaryF

Filtering Parent documents based on Child documents Facets selection

I have a nested documents which I am syncing in Solr : { "id":"NCT04372953", "title":"Positive End-Expiratory Pressure (PEEP) Levels During Resuscitation of Preterm Infants at Birth (The POLAR Trial) ", "phase":"N/A", "status":"Not yet recruiting", "studytype":"Interventional",

Solr Server Context Filtering in Auto Suggester not working

=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel And below you'll find again the same information in case it's deleted or you do not have access to it anymore. I'm experiencing problem when I try to use Context Filtering with auto suggester. What I want is to filter the suggestions based on *url field

Re: Filtering Solr pivot facet values

This works: =hockey|soccer -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Filtering large amount of values

hed. > Thanks, > Artur Rudenko > > -Original Message- > From: Mikhail Khludnev > Sent: Thursday, May 14, 2020 2:57 PM > To: solr-user > Subject: Re: Filtering large amount of values > > Hi, Artur. > > Please, don't tell me that you obtain docValues per

RE: Filtering large amount of values

e? Thanks, Artur Rudenko -Original Message- From: Mikhail Khludnev Sent: Thursday, May 14, 2020 2:57 PM To: solr-user Subject: Re: Filtering large amount of values Hi, Artur. Please, don't tell me that you obtain docValues per every doc? It's deadly slow see https://issues.apach

Re: Filtering large amount of values

Hi, Artur. Please, don't tell me that you obtain docValues per every doc? It's deadly slow see https://issues.apache.org/jira/browse/LUCENE-9328 for related problem. Make sure you obtain them once per segment, when leaf reader is injected. Recently there are some new method(s) for {!terms} I'm

Filtering large amount of values

Hi, We have a requirement of implementing a boolean filter with up to 500k values. We took the approach of post filter. Our environment has 7 servers of 128gb ram and 64cpus each server. We have 20-40m very large documents. Each solr instance has 64 shards with 2 replicas and JVM memory xms

Filtering point fields filters everything.

My company has been using solr for searching our product catalog. We migrated the data from Solr 6.6 to Solr 7.2. I am investigating the changes needed to migrate to Solr 8.*. Our current schema has a number of fields using the trie data types which are deprecated in 7 and gone in 8. I went

Clarification on Solr BlendedInfixLookupFactory with context filtering (suggest.cfq)

Hi Team, In our project we are using the Apache Solr and we really thankful to the framework. We need a clarification on solr's Blended Infix Lookup Factory with context filtering. We checked the documentation seems its supporting the context filtering and we tried to integrate in our

Re: Filtering children of parent doc from the input domain

Hello, Srijan. It's hard to grasp the problem without particular query and expected/actual results. On top of my head, it's possible to refine children by nesting query facet instruction under blockChildren one. On Tue, Jun

Filtering children of parent doc from the input domain

Hello, We're on Solr 6.2.1 and have a requirement where we need to facet on nested docs. So far we'd been using two pass query approach, where the first query searches within the parent domain and gets all the matching nested doc ids as facets (parent docs keep track of nested docs they contain)

Re: Group by and filtering on child documents.

On Wed, Jun 5, 2019 at 12:23 PM Jai Jamba wrote: > Can you help me with the subquery way, i tried that long back but it was > giving me some exception (can't remember that). > Well... me either. > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html > --

Re: Group by and filtering on child documents.

Can you help me with the subquery way, i tried that long back but it was giving me some exception (can't remember that). -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Group by and filtering on child documents.

Hello, Jai. It seems like sort functionality needs to be developed for https://lucene.apache.org/solr/guide/7_4/transforming-result-documents.html#child-childdoctransformerfactory However, it might be already reachable via more comprehensive

Re: Group by and filtering on child documents.

Hello Mikhail, I am sorry, I forgot to include below in my main query json (*"fields": "* [child limit=-1]"*) . I am extracting all the fields along with its nested docs. So I want as a part of results and not part of facet. I would expect out of the docs that i listed, it should return only

Re: Group by and filtering on child documents.

y related to filtering where I am not > sure how can I get the child documents having some field value equivalent > to maximum value of that field in the available child docs ("Price" field > for eg., need to get the child documents having maximum Price value, just > like groupin

Group by and filtering on child documents.

Hi, Below is my document structure and underneath I have mentioned my multi select facet query. I have one query related to filtering where I am not sure how can I get the child documents having some field value equivalent to maximum value of that field in the available child docs ("Price&q

Terms Component with filtering

table and unwanted matches can occur." title:"xyz" author:"xyz" data:"i need is filtering with terms component like terms.fl=data=wr.*=title:"xyz". iam not getting expected result when i exec." title:"xyz" author:"xyz" now im using t

Re: Terms Query Parser: filtering on null and strings with whitespace.

ere > I am filtering on documents that has no value for a given field(null) and > strings with whitespaces. > > I can filter on documents not having a value OR having some specific > values for the field as long as the value does not have a > whitespace(example 1). I can also filt

Terms Query Parser: filtering on null and strings with whitespace.

I am experiencing some weird behaviour when using terms query parser where I am filtering on documents that has no value for a given field(null) and strings with whitespaces. I can filter on documents not having a value OR having some specific values for the field as long as the value does

Re: Filtering group query results

. In essence, we want to return results only where numFound=1. I don't think this is possible in Solr.  I'm reasonably sure that the document count isn't calculated until after all the querying and filtering is done. It would be easy enough to do on the client side -- just skip over any group where

Filtering group query results

Hi, We have a requirement where we need to perform a group query in Solr where results are grouped by user-name (which is a field in our indexes) . We then need to filter the results based on numFound response parameter present under each group. In essence, we want to return results only where

Re: Filtering solr suggest results

ggester.html > > Cheers, > Peter. > > -Original Message- > From: Arunan Sugunakumar [mailto:arunans...@cse.mrt.ac.lk] > Sent: 03 July 2018 12:17 > To: solr-user@lucene.apache.org > Subject: Filtering solr suggest results > > Hi, > > I would like to kn

RE: Filtering solr suggest results

Hi Arunan, You can use a context filter query as described https://lucene.apache.org/solr/guide/6_6/suggester.html Cheers, Peter. -Original Message- From: Arunan Sugunakumar [mailto:arunans...@cse.mrt.ac.lk] Sent: 03 July 2018 12:17 To: solr-user@lucene.apache.org Subject: Filtering

Filtering solr suggest results

Hi, I would like to know whether it is possible to filter the suggestions returned by the suggest component according to a field. For example I have a list of books published by different publications. I want to show suggestions for a book title under a specific publication. Thanks in Advance,

Re: Getting the error - The field '*********' does not support spatial filtering

uot;location", >> >>"stored":true, >> >>"indexed":true >> >> } >> >> }' http://localhost:8983/solr/core/schema >> >> >> >> We are running Solr 7.1.0. >> >> >> >

Re: Getting the error - The field '*********' does not support spatial filtering

tp://localhost:8983/solr/core/schema > > > > We are running Solr 7.1.0. > > > > Hope this helps. > > > > Regards, > > > > David > > > > > > *From:* Aakanksha Gupta [mailto:aakankshagupta2...@gmail.com] > *Sent:* Monday, 19 February 2

RE: Getting the error - The field '*********' does not support spatial filtering

e.apache.org Subject: Getting the error - The field '*' does not support spatial filtering Hi all, I'm a newbie to Solr. I'm trying to use it for GeoSpatial Search and I'm facing an issue while using it. I've tried using the new 'location' field type()

Getting the error - The field '*********' does not support spatial filtering

latlong does not support spatial filtering Here's a snippet of my field definition in schema.xml in the conf folder of my core: And here are the field type definitions: Here's the Query I'm running: http://localhost:8983/solr/geo2

RE: Pass field value through function for filtering

value through function for filtering : : Forget about it, i just remember PostFilters! : : Thanks! : Markus : : -Original message- : > From:Markus Jelsma <markus.jel...@openindex.io> : > Sent: Tuesday 12th December 2017 12:54 : > To: Solr-user <solr-user@lucene.apache.org> : &

Re: Filtering Solr pivot facet values

It seems that there is something in latest Solr version that you might be able to use. From release notes: “The new facet.matches parameter returns facet buckets only for terms that match a regular expression.” HTH, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr &

Re: Filtering Solr pivot facet values

You might be able to do some interesting with the JSON faceting approach, but I confess I don't know for sure. Best, Erick On Thu, Dec 21, 2017 at 8:17 AM, Shawn Heisey wrote: > On 12/20/2017 2:40 PM, Arun Rangarajan wrote: >> >> I think multi-select faceting does the

Re: Filtering Solr pivot facet values

On 12/20/2017 2:40 PM, Arun Rangarajan wrote: I think multi-select faceting does the opposite of what I want. I want the facet to include the filters. You don't have any filters to include or exclude. You would need fq parameters to use multi-select faceting. But as you say, it doesn't do

Re: Filtering Solr pivot facet values

Thanks for your reply, Shawn. I think multi-select faceting does the opposite of what I want. I want the facet to include the filters. Example: The following 8 documents are the only ones in my Solr core: [ {"id": "1", "hierarchy": ["1", "16", "169"], "interests": ["soccer", "futbol"]},

Re: Filtering Solr pivot facet values

On 12/20/2017 1:31 PM, Arun Rangarajan wrote: > Sorry to bother you again on this. Is there no way in Solr to filter pivot > facets? > [Or did I attract the wrath of the group by posting the question first on > StackOverflow? :-)] StackOverflow and this list are pretty much unaware of each other

Re: Filtering Solr pivot facet values

/guide/6_6/faceting.html#Faceting-Limitingfacetwithcertainterms for > pivot facet query? Or are there alternate formats like JSON faceting that > may help here? > > (Full disclosure: I asked the question on StackOverflow and got no > response so far: https://stackoverflow.com/questions/47838619/ > filtering-solr-pivot-facet-values ) > > Thanks. >

Filtering Solr pivot facet values

that may help here? (Full disclosure: I asked the question on StackOverflow and got no response so far: https://stackoverflow.com/questions/47838619/filtering-solr-pivot-facet-values ) Thanks.

RE: Pass field value through function for filtering

Forget about it, i just remember PostFilters! Thanks! Markus -Original message- > From:Markus Jelsma <markus.jel...@openindex.io> > Sent: Tuesday 12th December 2017 12:54 > To: Solr-user <solr-user@lucene.apache.org> > Subject: Pass field value through function

Pass field value through function for filtering

Hello, I have a function and a lot of documents, i want to select all documents that give a certain value when i pass a document's field through the function, i just want to filter by function, how? I am thinking of implementing Collector. Get the docId, make a field look-up and discard if it

origFreq/freq ratio for filtering spell-check suggestions

Hi Solr users, I can see there are some parameters that can help in controlling the trigger condition for spellcheck mechanism or filter the spell suggestions like maxQueryFrequency or thresholdTokenFrequency. I could not find a parameter that will filter the suggestions based on (origFreq/freq)

Re: Is it possible to support context filtering for FuzzyLookupFactory?

ll. > > context filtering is also great, as we can only show suggestions based on > user's languages, doc types etc > > But its a pity that (seems) FuzzyLookupFactory and context filtering don't > work together. > > https://cwiki.apache.org/confluence/display/solr/Sugges

Is it possible to support context filtering for FuzzyLookupFactory?

FuzzyLookupFactory is great as it can still find matches even if users mis-spell. context filtering is also great, as we can only show suggestions based on user's languages, doc types etc But its a pity that (seems) FuzzyLookupFactory and context filtering don't work together. https

Re: TrieIntField vs IntPointField performance only for equality comparison (no range filtering)

Hi Shawn, I forgot that legacy-int-fields were deprecated. Point fields it is then. Thanks, Dorian On Tue, May 16, 2017 at 3:01 PM, Shawn Heisey wrote: > On 5/16/2017 3:33 AM, Dorian Hoxha wrote: > > Has anyone measured which is more efficient/performant between the 2 > >

Re: TrieIntField vs IntPointField performance only for equality comparison (no range filtering)

On 5/16/2017 3:33 AM, Dorian Hoxha wrote: > Has anyone measured which is more efficient/performant between the 2 > intfields if we don't need to do range-checking ? (precisionStep=0) Point field support in Solr is *BRAND NEW*. Very little information is available yet on the Solr implementation.

TrieIntField vs IntPointField performance only for equality comparison (no range filtering)

Hi, Has anyone measured which is more efficient/performant between the 2 intfields if we don't need to do range-checking ? (precisionStep=0) Regards, Dorian

Re: Filtering results by minimum relevancy score

gt; - just display less results ? >>>> you can easily do at search client time, cutting after a certain amount >>>> - make search faster returning less results ? >>>> This is not going to work, as you need to score all of them as Erick >>>> explained. >>>> >>>> Fun

Re: Filtering results by minimum relevancy score

] http://math.stackexchange.com/questions/610165/prove-that-the-bm25-scoring-function-is-probabilistic - --- Alessandro Benedetti Search Consultant, R Software Engineer, Director Sease Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/Filtering-r

Re: Filtering results by minimum relevancy score

ase Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3. nabble.com/Filtering-results-by-minimum-relevancy-score- tp4329180p4329295.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Filtering results by minimum relevancy score

Thank you! That worked. From: Ahmet Arslan <iori...@yahoo.com> Date: Wednesday, April 12, 2017 at 3:15 PM To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>, David Kramer <david.kra...@shoebuy.com> Subject: Re: Filtering results by minimum relevan

Re: Filtering results by minimum relevancy score

is to have more relevant docs. > > If your concern is just to not show that many pages, you can limit > that > > client side. > > > > > > > > > > > > > > - > > --- > >

Re: Filtering results by minimum relevancy score

    > If your concern is just to not show that many pages, you can limit that     > client side.     >     >     >     >     >     >     > -     > ---     > Alessandro Benedetti     > Search Consultant, R Software Engineer, Director     > Sease Ltd. - www.sease.

Re: Filtering results by minimum relevancy score

mprove relevancy if your >> concern is to have more relevant docs. >> If your concern is just to not show that many pages, you can limit that >> client side. >> >> >> >> >> >> >> - >> --- >> Alessandro Benedetti >> Search Consultant, R Software Engineer, Director >> Sease Ltd. - www.sease.io >> -- >> View this message in context: http://lucene.472066.n3. >> nabble.com/Filtering-results-by-minimum-relevancy-score- >> tp4329180p4329295.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > >

Re: Filtering results by minimum relevancy score

ti     > Search Consultant, R Software Engineer, Director     > Sease Ltd. - www.sease.io     > --     > View this message in context: http://lucene.472066.n3.     > nabble.com/Filtering-results-by-minimum-relevancy-score-     > tp4329180p4329295.html     > Sent from the Solr - User mailing list archive at Nabble.com.     >    

Re: Filtering results by minimum relevancy score

rn is just to not show that many pages, you can limit that > client side. > > > > > > > - > --- > Alessandro Benedetti > Search Consultant, R Software Engineer, Director > Sease Ltd. - www.sease.io > --

Re: Filtering results by minimum relevancy score

Well, just because ES has it doesn't mean it's A Good Thing. IMO, it's just a "feel good" kind of thing for people who don't really understand scoring. >From that page: "Note, most times, this does not make much sense, but is provided for advanced use cases." I've written enough weasel-worded

Re: Filtering results by minimum relevancy score

On 4/10/2017 8:59 AM, David Kramer wrote: > I’ve done quite a bit of searching on this. Pretty much every page I > find says it’s a bad idea and won’t work well, but I’ve been asked to > at least try it to reduce the number of completely unrelated results > returned. We are not trying to normalize

Re: Filtering results by minimum relevancy score

less docs in > sharded pagination overcomes the additional time needed to apply the > filtering function query. > I would need to investigate more in details the frange internals. > > Cheers > > > > - > --- > Alessandro Benedetti > Search Consulta

Re: Filtering results by minimum relevancy score

I am not completely sure that the potential benefit of merging less docs in sharded pagination overcomes the additional time needed to apply the filtering function query. I would need to investigate more in details the frange internals. Cheers - --- Alessandro Benedetti Search

Re: Filtering results by minimum relevancy score

> - > --- > Alessandro Benedetti > Search Consultant, R Software Engineer, Director > Sease Ltd. - www.sease.io > -- > View this message in context: http://lucene.472066.n3. > nabble.com/Filtering-results-by-minimum-relevancy-score- > tp4329180p4329295.html > Sent from the Solr - User mailing list archive at Nabble.com. >

Re: Filtering results by minimum relevancy score

concern is just to not show that many pages, you can limit that client side. - --- Alessandro Benedetti Search Consultant, R Software Engineer, Director Sease Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/Filtering-results-by-minimum

Re: Filtering results by minimum relevancy score

Here we go https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-FunctionRangeQueryParser . But it's %100 YAGNI. You'd better tweak search to be more precise. On Mon, Apr 10, 2017 at 7:12 PM, Ahmet Arslan wrote: > Hi, > I remember that this is

Re: Filtering results by minimum relevancy score

Hi, I remember that this is possible via frange query parser.But I don't have the query string at hand. Ahmet On Monday, April 10, 2017, 9:00:09 PM GMT+3, David Kramer wrote: I’ve done quite a bit of searching on this.  Pretty much every page I find says it’s a bad

Re: Filtering results by minimum relevancy score

Well, that's rather the point, the low-scoring docs aren't unrelated, someone just thinks they are. Flippancy aside, the score is, as you've researched, a bad gauge. Since Lucene has to compute the score of a doc before it knows the score, at any point in the collection process you may get a doc

Filtering results by minimum relevancy score

I’ve done quite a bit of searching on this. Pretty much every page I find says it’s a bad idea and won’t work well, but I’ve been asked to at least try it to reduce the number of completely unrelated results returned. We are not trying to normalize the number, or display it as a percentage,

Re: Filtering a field when some of the documents don't have the value

Thanks Erick, it works exactly as required! Gintas On Mon, Nov 14, 2016 at 7:02 PM, Erick Erickson wrote: > You want something like: > name:x=population:[10 TO *] OR (*:* -population:*:*) > > Best, > Erick > > On Mon, Nov 14, 2016 at 10:29 AM, Gintautas Sulskus >

Re: Filtering a field when some of the documents don't have the value

You want something like: name:x=population:[10 TO *] OR (*:* -population:*:*) Best, Erick On Mon, Nov 14, 2016 at 10:29 AM, Gintautas Sulskus wrote: > Hi, > > I have an index with two fields "name" and "population". Some of the > documents have the "population"

Filtering a field when some of the documents don't have the value

Hi, I have an index with two fields "name" and "population". Some of the documents have the "population" field empty. I would like to search for a value X in field "name" with the following condition: 1. if the field is empty - return results for name:X 2. else set the minimum value for the

Re: Filtering on nGroups

You may want to check this out: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62693238 It does aggregations that might work for you. Joel Bernstein http://joelsolr.blogspot.com/ On Fri, May 6, 2016 at 2:31 PM, Nick Vasilyev wrote: > I guess it

Re: Filtering on nGroups

I guess it would also work if I could facet on the group counts. I just need to know how many groups of different sizes there are. On Fri, May 6, 2016 at 2:10 PM, Nick Vasilyev wrote: > I am on 6.1 preview, I just need this to gather some one time metrics so >

Re: Filtering on nGroups

I am on 6.1 preview, I just need this to gather some one time metrics so performance isn't an issue. On May 6, 2016 1:13 PM, "Erick Erickson" wrote: What version of Solr? Regardless, if you can pre-process at index time it'll be faster than anything else (probably).

Re: Filtering on nGroups

What version of Solr? Regardless, if you can pre-process at index time it'll be faster than anything else (probably). pre-processing isn't very dynamic though so there are lots of situations where that's just not viable. Best, Erick On Thu, May 5, 2016 at 6:05 PM, Nick Vasilyev

Filtering on nGroups

I am grouping documents on a field and would like to retrieve documents where the number of items in a group matches a specific value or a range. I haven't been able to experiment with all new functionality, but I wanted to see if this is possible without having to calculate the count and add it

Re: Cannot use Phrase Queries in eDisMax and filtering

%20discription^5& > >> pf3=1& > >> pf2=1& > >> ps=1& > >> qroup=true& > >> group.field=member_id& > >> group.limit=10& > >> sort=score desc& > >> group.ngroups=true > >> > >> > >> > >> > >> q=bmw& > >> fl=score,*& > >> wt=json& > >> fq=city_id:59& > >> qt=/query& > >> defType=edismax& > >> pf=title^15%20discription^5& > >> pf3=1& > >> pf2=1& > >> ps=1& > >> qroup=true& > >> group.field=member_id& > >> group.limit=10& > >> group.ngroups=true& > >> sort=score desc& > >> fq=category_id:1777 > >> > >> > >> > >> -- > >> View this message in context: > >> > http://lucene.472066.n3.nabble.com/Cannot-use-Phrase-Queries-in-eDisMax-and-filtering-tp4167302p4167338.html > >> Sent from the Solr - User mailing list archive at Nabble.com. > >> >

Re: Cannot use Phrase Queries in eDisMax and filtering

city_id:59& > >> qt=/query& > >> defType=edismax& > >> pf=title^15%20discription^5& > >> pf3=1& > >> pf2=1& > >> ps=1& > >> qroup=true& > >> group.field=member_id& > >> grou

Re: Cannot use Phrase Queries in eDisMax and filtering

gt;> fl=score,*& >> wt=json& >> fq=city_id:59& >> qt=/query& >> defType=edismax& >> pf=title^15%20discription^5& >> pf3=1& >> pf2=1& >> ps=1& >> qroup=true& >> group.field=member_id& >> group.limit=10& >> group.ngroups=true& >> sort=score desc& >> fq=category_id:1777 >> >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Cannot-use-Phrase-Queries-in-eDisMax-and-filtering-tp4167302p4167338.html >> Sent from the Solr - User mailing list archive at Nabble.com. >>

Re: Cannot use Phrase Queries in eDisMax and filtering

ty_id:59& > qt=/query& > defType=edismax& > pf=title^15%20discription^5& > pf3=1& > pf2=1& > ps=1& > qroup=true& > group.field=member_id& > group.limit=10& > group.ngroups=true& > sort=score desc& > fq=category_id:1777 > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Cannot-use-Phrase-Queries-in-eDisMax-and-filtering-tp4167302p4167338.html > Sent from the Solr - User mailing list archive at Nabble.com. >

Re: using tokens to influence boost and score rather than filtering

> > > > -Original message- > > From:John Blythe <j...@curvolabs.com> > > Sent: Tuesday 5th April 2016 15:36 > > To: solr-user <solr-user@lucene.apache.org> > > Subject: using tokens to influence boost and score rather than filtering > > &

RE: using tokens to influence boost and score rather than filtering

l 2016 15:36 > To: solr-user <solr-user@lucene.apache.org> > Subject: using tokens to influence boost and score rather than filtering > > hi all, > > i'm trying to do something similar to a simple fq=x on my query. i'm using > the regular ol' select handler. instead of blocki

using tokens to influence boost and score rather than filtering

hi all, i'm trying to do something similar to a simple fq=x on my query. i'm using the regular ol' select handler. instead of blocking out all items not related to x via the filter query i'd like to simply give them priority. is there a way to do this? it seems like the dismax bq function may be

Re: Restricting/Filtering facet results

The facet.query parameter is what you're looking for. Use it like so: =field:(UserB OR UserC) Check out the wiki for more details On Thu, 21 Jan 2016, 14:41 Achim Domma wrote: > Hi, > > is there some way to restrict/filter the facetting results? Our use case > is the

Restricting/Filtering facet results

Hi, is there some way to restrict/filter the facetting results? Our use case is the following: Our documents have a multi value field, which holds user ids, so the values might be like this: doc1 = ['UserA', 'UserB', 'UserC'] doc2 = ['UserA', 'UserB'] doc3 = ['UserA', 'UserC'] Now I execute a

Re: Restricting/Filtering facet results

If I specify the query like this, I will get only one facet back. Or am I wrong? I would have to specify one query for UserB and one for UserC. My filter list can contain thousands of users, so specifying individual queries is not an option. On 21.01.2016 11:43, Binoy Dalal wrote: > The

Re: Restricting/Filtering facet results

Yes, you'll get one facet back, but you can specify multiple facet.query clauses, as =field:UserB =field:UserC and get two back. Best, Erick On Thu, Jan 21, 2016 at 7:43 AM, Achim Domma wrote: > If I specify the query like this, I will get only one facet back. Or am > I

Re: Securing field level access permission by filtering the query itself

ay want to also scan >>>>> that >>>>>> for fielded query clauses (eg "badfield:value") and localParams (eg >>>>>> "{!dismax qf=badfield}value"). >>>>>> >>>>>> Secondly, you can map internal Solr fiel

Re: Securing field level access permission by filtering the query itself

ist before you send the request to Solr. > >> The > >>>>>> easy part will be to do that on URL parameters like fl. Depending on > >>> how > >>>>>> your app generates the actual query string, you may want to also > scan > >>>>>

Re: Securing field level access permission by filtering the query itself

ng the whitelist), and then in the fl > >>> parameter supply the aliases you want sent in the response. > >>> > >>> > >>> k/r, > >>> Scott > >>> > >>> On Wed, Oct 28, 2015 at 6:58 PM, Douglas McGilvray <d...@weemo

Re: Securing field level access permission by filtering the query itself

ses using this > syntax > > >> in > > >>> the fl parameter: "display_name:real_solr_name". So when the request > > >> comes > > >>> in from your app, first you'll map from the requested field alias > names > > >>

Re: Securing field level access permission by filtering the query itself

eemondo.com> > wrote: > > > >> Hi all, > >> > >> First I’d like to say the nested facets and the json facet api in > >> particular have made my world much better, I thank everyone involved, > you > >> are all awesome. > >> > &

Re: Securing field level access permission by filtering the query itself

;> >>> >>> k/r, >>> Scott >>> >>> On Wed, Oct 28, 2015 at 6:58 PM, Douglas McGilvray <d...@weemondo.com> >> wrote: >>> >>>> Hi all, >>>> >>>> First I’d like to say the nested facets and the

Re: Securing field level access permission by filtering the query itself

of the solr query building working on the > browser, solr is behind a php server which acts as “proxy” and doorman, > filtering at the document level according to user role and supplying some > sensible maximums … > > However we now wish to filter just one or two potentially sensi

Re: Securing field level access permission by filtering the query itself

6:58 PM, Douglas McGilvray <d...@weemondo.com> wrote: > >> Hi all, >> >> First I’d like to say the nested facets and the json facet api in >> particular have made my world much better, I thank everyone involved, you >> are all awesome. >> >>

Securing field level access permission by filtering the query itself

” and doorman, filtering at the document level according to user role and supplying some sensible maximums … However we now wish to filter just one or two potentially sensitive fields in one document type according to user role (as determined in the php proxy). Duplicating documents (or cores

Re: Filtering on a Field with Suggestion

Thanks for pointing out as I am using Solr cloud 5.3. However, it looks like they are talking about boolean operation in context field and not the support of context field itself. Are you sure that context filtering is not supported with any lookup prior to 5.4? On Oct 16, 2015 12:47 PM

Re: Filtering on a Field with Suggestion

of the article (about Context Filtering) but still could not get the filter > working. > > My Solr configuration for suggestion is > > > > mySuggester > AnalyzingInfixLookupFactory > DocumentDictionaryFactory > entity_autocomplete > type

Re: Filtering on a Field with Suggestion

Yes, as Jan confirmed, I am sure it was not there in 5.3 :) Cheers On 16 October 2015 at 12:10, Jan Høydahl <jan@cominvent.com> wrote: > Yesm > > Context filtering is a new feature in yet-to-be-released Solr5.4. > So you have to build branch_5x from source your

Re: Filtering on a Field with Suggestion

Yesm Context filtering is a new feature in yet-to-be-released Solr5.4. So you have to build branch_5x from source yourself to try it out. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 16. okt. 2015 kl. 12.35 skrev Salman Ansari <salman.rah...@gma

Filtering on a Field with Suggestion

(about Context Filtering) but still could not get the filter working. My Solr configuration for suggestion is mySuggester AnalyzingInfixLookupFactory DocumentDictionaryFactory entity_autocomplete type text_auto false I have two entries for "Bill

Re: Join with faceting and filtering

Hello Troy, What a challenge!! On Thu, Oct 1, 2015 at 3:42 PM, Troy Edwards wrote: > > 2) It appears that I cannot have fromIndex=Contracts because it is very > large and has to be sharded. Per my understanding SolrCloud join does not > support multiple shards > ..

Re: Join with faceting and filtering

1. i'd say it's challenge. 2. can't you do the opposite filter active contracts, join them back to items, and facet then? q=(Description:colgate OR Categories:colgate OR Sellers:colgate)={!join from=ItemId to=ItemId fromIndex=Contracts)Active:true=SellersString 3. note: there is {!terms} QParser

  1   2   3   4   5   >