[
https://issues.apache.org/jira/browse/SOLR-14330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris M. Hostetter updated SOLR-14330:
--------------------------------------
Attachment: SOLR-14330.patch
Assignee: Chris M. Hostetter
Status: Open (was: Open)
Attaching a strawman patch with some tests.
The patch introduces an {{expand.nullGroup=true|false}} option to control
if/when this behavior happens, and works with both nullPolicy=collapse and
nullPolicy=expand (although obviously it only creates a single group for null
docs in the {{expanded}} section). It should also work fine with
{{expand.field}} and {{expand.q}} type situations, but there's nocommits to
actually test that.
wanted to put the patch out before getting too deep into new tests incase
people have concerns about the semantics/behavior/UX and wanted to discuss if
it should behave or be implemented differently.
> Return docs with null value in expand for field when collapse has
> nullPolicy=collapse
> -------------------------------------------------------------------------------------
>
> Key: SOLR-14330
> URL: https://issues.apache.org/jira/browse/SOLR-14330
> Project: Solr
> Issue Type: Wish
> Reporter: Munendra S N
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-14330.patch
>
>
> When documents doesn't contain value for field then, with collapse either
> those documents could be either ignored(default), collapsed(one document is
> chosen) or expanded(all are returned). This is controlled by {{nullPolicy}}
> When {{nullPolicy}} is {{collapse}}, it would be nice to return all documents
> with {{null}} value in expand block if {{expand=true}}
> Also, when used with {{expand.field}}, even then we should return such
> documents
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
