[ 
https://issues.apache.org/jira/browse/SOLR-10132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169878#comment-16169878
 ] 

Christine Poerschke commented on SOLR-10132:
--------------------------------------------

Hi Gus, thanks for returning to this!

bq. ... the MATCH_ALL_TERMS idea has missed the boat. ...  so I think now 
returning null as before is the only path forward. ...

I agree.

bq. ... Also the new ascii doc stuff has come in since the last patch here so I 
probably should add some documentation for this feature too, now that that is 
something I can do myself :-). ...

Yes please.

bq. ... Should I do the patch vs trunk since it seems I just barely missed the 
boat for 7?

Yes please. Almost always patches would be against trunk/master and then from 
there any back porting would be done via cherry-pick to the branches, branch_7x 
at present.

> Support facet.matches to cull facets returned with a regex
> ----------------------------------------------------------
>
>                 Key: SOLR-10132
>                 URL: https://issues.apache.org/jira/browse/SOLR-10132
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: faceting
>    Affects Versions: 6.4.1
>            Reporter: Gus Heck
>            Assignee: Christine Poerschke
>         Attachments: SOLR-10132.patch, SOLR-10132.patch, SOLR-10132.patch
>
>
> I recently ran into a case where I really wanted to only return the next 
> level of a hierarchical facet, and while I was able to do that with a 
> coordinated set of dynamic fields, it occurred to me that this would have 
> been much much easier if I could have simply used PathHierarchyTokenizer and 
> written
> &facet.matches="/my/current/prefix/[^/]+$"
> thereby limiting the returned facets to the next level down and not return 
> the  additional  N levels I didn't (yet) want to display (numbering in the 
> thousands near the top of the tree). I suspect there are other good use 
> cases, and the patch seemed relatively tractable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to