[
https://issues.apache.org/jira/browse/SOLR-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123614#comment-15123614
]
Joel Bernstein commented on SOLR-8613:
--------------------------------------
I think the resolution of this ticket will involve checking for valid fields
during the SQL parse. We can easily do this once the SQL Catalog is put in
place to support the JDBC driver and the eventual SQL Optimizer.
> 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]
