[
https://issues.apache.org/jira/browse/SOLR-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896012#comment-15896012
]
Kevin Risden commented on SOLR-8613:
------------------------------------
I think this is resolved with SOLR-8593. Calcite is checking valid columns
before executing the plan.
> 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: Bug
> Components: SolrJ
> Affects Versions: 6.0
> Reporter: Kevin Risden
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
