[
https://issues.apache.org/jira/browse/SOLR-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123605#comment-15123605
]
Joel Bernstein commented on SOLR-8613:
--------------------------------------
SOLR-8285 will clear up some of the differences around NULL field handling. But
invalid fields will continue to be accepted by the /select handler. The /export
handler has a step which throws an exception for an invalid field. The /select
handler quietly ignores invalid fields, either by design or just because it's
always been that way.
> SolrJ JDBC - SQL queries with limit do not fail when a bad column is provided
> -----------------------------------------------------------------------------
>
> Key: SOLR-8613
> URL: https://issues.apache.org/jira/browse/SOLR-8613
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Affects Versions: Trunk
> Reporter: Kevin Risden
> Fix For: Trunk
>
>
> This was found exporting SOLR-8602. Without a limit, the query fails with
> unable to read the first tuple due to a bad column being provided. When using
> a limit, there is no error and the column is returned as all nulls.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
