[
https://issues.apache.org/jira/browse/CONNECTORS-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163584#comment-14163584
]
Alessandro Benedetti commented on CONNECTORS-1066:
--------------------------------------------------
So let me try to understand ...
The only way you can break the solr sort ( that allow you to configure
sortMissingLast=true or sortMissingStart=true) is with blank fields, because in
this way you are confusing solr that returns a sorting that the user will not
understand.
Related to the second point we have to think in a Solr way when we are talking
about rendering of search results. And in Solr an expected behaviour for a
search result is to not show a field that is not present with content.
In your usecase you wanted to show all the fields for a document, also the null
ones ? So you decided to index the blank values ?
>From a search point of view it doesn't make any sense but if you were using
>Solr as a sort of nosql database maybe it did.
By the way I agree to keep it as optional ( but default to remove blank fields).
I was only curious to understand better your usecase :)
> Don't send empty fields to Solr
> -------------------------------
>
> Key: CONNECTORS-1066
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1066
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Lucene/SOLR connector
> Affects Versions: Manifold 1.7.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Labels: solr
> Fix For: ManifoldCF 2.0
>
> Attachments: CONNECTORS-1066.patch
>
>
> Don't transmit empty fields to Solr.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
