Feedback
Did this article resolve your question/issue?

   

Article

Type VARCHAR(x) not properly reported with Connect for ODBC Spark Driver

Information

 
TitleType VARCHAR(x) not properly reported with Connect for ODBC Spark Driver
URL NameType-VARCHAR-x-not-properly-reported-with-Connect-for-ODBC-Spark-Driver
Article Number000182397
EnvironmentProduct : Connect for ODBC Apache Spark SQL driver
Version : All supported versions
Database : Apache Spark 1.3.1
OS : All supported platforms
Application : All supported applications
Question/Problem Description
When connected to Spark 1.3.1, a varchar is always returned as Varchar(65535)
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberDefect 31274
Enhancement Number
Cause
Resolution
This is a database problem.
The native catalog is returning the wrong value so the driver does not know the correct value and therefore returns the default value.
Workaround
Set UseNativeCatalogFunctions=0 in the datasource
Notes
Last Modified Date2/3/2016 12:04 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.