[
https://issues.apache.org/jira/browse/CONNECTORS-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162035#comment-14162035
]
Alessandro Benedetti commented on CONNECTORS-1066:
--------------------------------------------------
So let me answer you, in Solr is possible to see the difference query side, but
with no benefit, let me explain :
Because Solr is a free text search engine server, your target is to search over
a content.
Of course some field is mandatory or not.
So you have 2 scenarios for a field : you have content or you don't.
Introducing empty field you can have strange behaviours solr sides because from
the human point of view there is no difference between an empty or a null
field, but for solr yes, and the proper way to model that is with a null field.
introducing empty field can lead to inconsistent behaviour mainly sorting side,
or when you want to retrieve documents that have value for that field ( in this
case indexing empty fields you are introducing false positive for that search)
Hope this clarify.
This is my opinion, if you see some problem in this, I can think more on this.
> 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)
