[
https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121365#comment-15121365
]
Joel Bernstein commented on SOLR-8602:
--------------------------------------
I was just reviewing the exception handling in ResultSetImpl constructor. It
looks ok but wanted to check to make sure the underlying error was being thrown
properly in the driver. For example did the DBVisualizer debug panel display
the message about the numWorkers error.
The way this works is that the SolrStream recognizes errors coming from the
server through a flag in the Tuple. If it sees this flag it throws an Exception
with the message. This should have been thrown on the first call to read() with
the numWorker error.
> 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,
> 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: [email protected]
For additional commands, e-mail: [email protected]