[
https://issues.apache.org/jira/browse/CONNECTORS-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165056#comment-14165056
]
Alessandro Benedetti commented on CONNECTORS-1066:
--------------------------------------------------
Only to give my final thought again also regarding back compatibilityand to
answer last questions.
In this case I would call it "back bug compatibility" as I believe with this
change we are only going to fix bugs we introduced in systems with the previous
version :)
Trying to think a usecase where we should introduce the ambiguity Solr side on
purpose( indexing blank and indexing null) I can still not find it.
Because the system should provide both empty and null fields only if any
usecase exists.
A use case is the description of an user interaction with the system.
And for a human user there is no difference between empty and null.
-> no use case can exist and no need to implement the ambiguity .
This is my last observation because I can still not see the reason to keep both
empty and null values for a field :D
So let's use the approach you want without problem, but I am still really
curious of discovering a possible usecase that make sense to any user :)
Cheers
> 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)
