[ https://issues.apache.org/jira/browse/SOLR-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-5231: --------------------------- Affects Version/s: 4.2 4.3 4.3.1 Fix Version/s: 5.0 4.5 Assignee: Hoss Man > When a boolean field is missing from a doc it is sometimes treated as "true" > by the "if" function (based on other docs in segment?) > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: SOLR-5231 > URL: https://issues.apache.org/jira/browse/SOLR-5231 > Project: Solr > Issue Type: Bug > Affects Versions: 4.2, 4.3, 4.3.1, 4.4 > Reporter: Hoss Man > Assignee: Hoss Man > Fix For: 4.5, 5.0 > > Attachments: SOLR-5231.patch > > > This issue is hard to explain with out a long example. > crux of the problem is that the behavior of the if function, wrapped arround > a boolean field (ie: "{{if(fieldName,x,y)}}" ) is not consistent for > documents that do not have any value for that functio -- the behavior seems > to depend on whether or not other documents in the same segment have a value > for that field. > for brevity, details will follow in a comment - but i've been able to > reproduce on trunk, 4.3, and 4.3 (didn't look back farther then that) > the work around is to explicitly use the {{exists()}} function in the if > condition (ie: "{{if(exists(fieldName),x,y)}}" ) > (Thanks to Elodie Sannier for reporting the initial symptoms of this on the > mailing list) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org