[
https://issues.apache.org/jira/browse/SOLR-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123557#comment-15123557
]
Kevin Risden edited comment on SOLR-8613 at 1/29/16 3:09 PM:
-------------------------------------------------------------
[~joel.bernstein] This might be related to the differences with and without a
limit. SOLR-8285
was (Author: risdenk):
[~joel.bernstein] This might be related to the differences with and without a
limit. SOLR-8613
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
