[ https://issues.apache.org/jira/browse/SPARK-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605078#comment-14605078 ]
Gergely Svigruha edited comment on SPARK-8616 at 6/29/15 3:43 AM: ------------------------------------------------------------------ Thanks for working on this! FYI, MYSQL may allow double quotes if the ANSI_QUOTES mode is enabled: https://dev.mysql.com/doc/refman/5.0/en/identifiers.html was (Author: gsvigruha): FYI, MYSQL may allow double quotes if the ANSI_QUOTES mode is enabled: https://dev.mysql.com/doc/refman/5.0/en/identifiers.html > SQLContext doesn't handle tricky column names when loading from JDBC > -------------------------------------------------------------------- > > Key: SPARK-8616 > URL: https://issues.apache.org/jira/browse/SPARK-8616 > Project: Spark > Issue Type: Bug > Components: SQL > Affects Versions: 1.4.0 > Environment: Ubuntu 14.04, Sqlite 3.8.7, Spark 1.4.0 > Reporter: Gergely Svigruha > > Reproduce: > - create a table in a relational database (in my case sqlite) with a column > name containing a space: > CREATE TABLE my_table (id INTEGER, "tricky column" TEXT); > - try to create a DataFrame using that table: > sqlContext.read.format("jdbc").options(Map( > "url" -> "jdbs:sqlite:...", > "dbtable" -> "my_table")).load() > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > column: tricky) > According to the SQL spec this should be valid: > http://savage.net.au/SQL/sql-99.bnf.html#delimited%20identifier -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org