You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2016/05/11 15:51:12 UTC
[jira] [Updated] (SOLR-8613) SolrJ JDBC - SQL queries with limit do
not fail when a bad column is provided
[ https://issues.apache.org/jira/browse/SOLR-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Risden updated SOLR-8613:
-------------------------------
Fix Version/s: (was: 6.0)
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org