[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120429#comment-15120429 ]
Joel Bernstein commented on SOLR-8602: -------------------------------------- I believe in the case of the /export handler numerics will never be null. This is because numerics are read from NumericDocValues which I believe treats nulls as 0. But as you proven with the test case the /select handler will return null values for numerics. I was surprised to see that you could put a null value in an int field and that would behave properly. I'm assuming the field is not added to the document if the field value is null. > Implement ResultSetImpl.wasNull() > --------------------------------- > > Key: SOLR-8602 > URL: https://issues.apache.org/jira/browse/SOLR-8602 > Project: Solr > Issue Type: Sub-task > Components: SolrJ > Affects Versions: Trunk > Reporter: Kevin Risden > Assignee: Joel Bernstein > Fix For: Trunk > > Attachments: SOLR-8602.patch, SOLR-8602.patch, SOLR-8602.patch > > > ResultSetImpl.wasNull is necessary for SQL clients to display a SQL NULL > instead of 0 or false for certain get* commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org