[jira] [Created] (SPARK-10170) Writing from data frame into db2 database using jdbc data source api fails with error for string, and boolean column types.

Suresh Thalamati created SPARK-10170: Summary: Writing from data frame into db2 database using jdbc data source api fails with error for string, and boolean column types. Key: SPARK-10170 URL:

[jira] [Commented] (SPARK-10170) Writing from data frame into db2 database using jdbc data source api fails with error for string, and boolean column types.

[ https://issues.apache.org/jira/browse/SPARK-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708124#comment-14708124 ] Suresh Thalamati commented on SPARK-10170: -- Scanning through the code I found

[jira] [Commented] (SPARK-11454) DB2 dialect - map DB2 ROWID and TIMESTAMP with TIMEZONE types into valid Spark types

[ https://issues.apache.org/jira/browse/SPARK-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15004488#comment-15004488 ] Suresh Thalamati commented on SPARK-11454: -- I am looking into fixing this Jira along with

[jira] [Commented] (SPARK-10521) Utilize Docker to test DB2 JDBC Dialect support

[ https://issues.apache.org/jira/browse/SPARK-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14999799#comment-14999799 ] Suresh Thalamati commented on SPARK-10521: -- @Luciano, Jdbc data sources docker tests are

[jira] [Comment Edited] (SPARK-11300) Support for string length when writing to JDBC

[ https://issues.apache.org/jira/browse/SPARK-11300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14983631#comment-14983631 ] Suresh Thalamati edited comment on SPARK-11300 at 10/30/15 11:59 PM: -

[jira] [Commented] (SPARK-11300) Support for string length when writing to JDBC

[ https://issues.apache.org/jira/browse/SPARK-11300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14983631#comment-14983631 ] Suresh Thalamati commented on SPARK-11300: -- Another related issue is Spark-10849, Fix will

[jira] [Created] (SPARK-10655) Enhance DB2 dialect to handle XML, and DECIMAL , and DECFLOAT

Suresh Thalamati created SPARK-10655: Summary: Enhance DB2 dialect to handle XML, and DECIMAL , and DECFLOAT Key: SPARK-10655 URL: https://issues.apache.org/jira/browse/SPARK-10655 Project: Spark

[jira] [Commented] (SPARK-10655) Enhance DB2 dialect to handle XML, and DECIMAL , and DECFLOAT

[ https://issues.apache.org/jira/browse/SPARK-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791440#comment-14791440 ] Suresh Thalamati commented on SPARK-10655: -- I am working on pull request for this issue. >

[jira] [Commented] (SPARK-10664) JDBC DataFrameWriter does not save data to Oracle 11 Database

[ https://issues.apache.org/jira/browse/SPARK-10664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803331#comment-14803331 ] Suresh Thalamati commented on SPARK-10664: -- Table exists case should be fixed as part of

[jira] [Commented] (SPARK-10857) SQL injection bug in JdbcDialect.getTableExistsQuery()

[ https://issues.apache.org/jira/browse/SPARK-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14937732#comment-14937732 ] Suresh Thalamati commented on SPARK-10857: -- One issue I ran into with getSchema() call was even

[jira] [Created] (SPARK-10849) Allow user to specify database column type for data frame fields when writing data to jdbc data sources.

Suresh Thalamati created SPARK-10849: Summary: Allow user to specify database column type for data frame fields when writing data to jdbc data sources. Key: SPARK-10849 URL:

[jira] [Commented] (SPARK-10849) Allow user to specify database column type for data frame fields when writing data to jdbc data sources.

[ https://issues.apache.org/jira/browse/SPARK-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14909972#comment-14909972 ] Suresh Thalamati commented on SPARK-10849: -- I am working on creating pull request for this

[jira] [Commented] (SPARK-10756) DataFrame write to teradata using jdbc not working, tries to create table each time irrespective of table existence

[ https://issues.apache.org/jira/browse/SPARK-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903100#comment-14903100 ] Suresh Thalamati commented on SPARK-10756: -- This issue is similar to

[jira] [Commented] (SPARK-9078) Use of non-standard LIMIT keyword in JDBC tableExists code

[ https://issues.apache.org/jira/browse/SPARK-9078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720747#comment-14720747 ] Suresh Thalamati commented on SPARK-9078: - @Bob, Reynold I ran into the same

[jira] [Created] (SPARK-12504) JDBC data source credentials are not masked in the data frame explain output.

Suresh Thalamati created SPARK-12504: Summary: JDBC data source credentials are not masked in the data frame explain output. Key: SPARK-12504 URL: https://issues.apache.org/jira/browse/SPARK-12504

[jira] [Commented] (SPARK-12504) JDBC data source credentials are not masked in the data frame explain output.

[ https://issues.apache.org/jira/browse/SPARK-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15070002#comment-15070002 ] Suresh Thalamati commented on SPARK-12504: -- I am testing the fix for this issue , will post the

[jira] [Commented] (SPARK-12504) JDBC data source credentials are not masked in the data frame explain output.

[ https://issues.apache.org/jira/browse/SPARK-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15070054#comment-15070054 ] Suresh Thalamati commented on SPARK-12504: -- Pull Request:

[jira] [Created] (SPARK-15538) Truncate table does not work on data source table , and does not raise error either.

Suresh Thalamati created SPARK-15538: Summary: Truncate table does not work on data source table , and does not raise error either. Key: SPARK-15538 URL: https://issues.apache.org/jira/browse/SPARK-15538

[jira] [Commented] (SPARK-15538) Truncate table does not work on data source table , and does not raise error either.

[ https://issues.apache.org/jira/browse/SPARK-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300867#comment-15300867 ] Suresh Thalamati commented on SPARK-15538: -- Working on PR for this issue. > Truncate table

[jira] [Commented] (SPARK-12504) JDBC data source credentials are not masked in the data frame explain output.

[ https://issues.apache.org/jira/browse/SPARK-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301392#comment-15301392 ] Suresh Thalamati commented on SPARK-12504: -- [~srowen] I worked on resolving this issue. For

[jira] [Created] (SPARK-13167) JDBC data source does not include null value partition columns rows in the result.

Suresh Thalamati created SPARK-13167: Summary: JDBC data source does not include null value partition columns rows in the result. Key: SPARK-13167 URL: https://issues.apache.org/jira/browse/SPARK-13167

[jira] [Commented] (SPARK-13167) JDBC data source does not include null value partition columns rows in the result.

[ https://issues.apache.org/jira/browse/SPARK-13167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131258#comment-15131258 ] Suresh Thalamati commented on SPARK-13167: -- I am working on fix for this issue. > JDBC data

[jira] [Commented] (SPARK-13820) TPC-DS Query 10 fails to compile

[ https://issues.apache.org/jira/browse/SPARK-13820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15196419#comment-15196419 ] Suresh Thalamati commented on SPARK-13820: -- This query contains correlated subquery, it is not

[jira] [Created] (SPARK-14218) dataset show() does not display column names in the correct order if underlying data frame schema order is different from the encoder schema order.

Suresh Thalamati created SPARK-14218: Summary: dataset show() does not display column names in the correct order if underlying data frame schema order is different from the encoder schema order. Key: SPARK-14218

[jira] [Commented] (SPARK-14218) dataset show() does not display column names in the correct order if underlying data frame schema order is different from the encoder schema order.

[ https://issues.apache.org/jira/browse/SPARK-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215098#comment-15215098 ] Suresh Thalamati commented on SPARK-14218: -- I am giving a shot at submitting PR for this

[jira] [Commented] (SPARK-13860) TPCDS query 39 returns wrong results compared to TPC official result set

[ https://issues.apache.org/jira/browse/SPARK-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200805#comment-15200805 ] Suresh Thalamati commented on SPARK-13860: -- [~yhuai] [~mengxr] I noticed there is discussion on

[jira] [Commented] (SPARK-13860) TPCDS query 39 returns wrong results compared to TPC official result set

[ https://issues.apache.org/jira/browse/SPARK-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200330#comment-15200330 ] Suresh Thalamati commented on SPARK-13860: -- I looked into this issue and found out NULL values

[jira] [Commented] (SPARK-13699) Spark SQL drops the table in "overwrite" mode while writing into table

[ https://issues.apache.org/jira/browse/SPARK-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183996#comment-15183996 ] Suresh Thalamati commented on SPARK-13699: -- Thank you for providing the reproduction to the

[jira] [Commented] (SPARK-14840) Cannot drop a table which has the name starting with 'or'

[ https://issues.apache.org/jira/browse/SPARK-14840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264616#comment-15264616 ] Suresh Thalamati commented on SPARK-14840: -- On master(2.0) , this issue is fixed recently as

[jira] [Commented] (SPARK-15315) CSV datasource writes garbage for complex types instead of rasing error.

[ https://issues.apache.org/jira/browse/SPARK-15315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283042#comment-15283042 ] Suresh Thalamati commented on SPARK-15315: -- I am working on submitting PR for this issue , will

[jira] [Created] (SPARK-15315) CSV datasource writes garbage for complex types instead of rasing error.

Suresh Thalamati created SPARK-15315: Summary: CSV datasource writes garbage for complex types instead of rasing error. Key: SPARK-15315 URL: https://issues.apache.org/jira/browse/SPARK-15315

[jira] [Created] (SPARK-15125) CSV data source recognizes empty quoted strings in the input as null.

Suresh Thalamati created SPARK-15125: Summary: CSV data source recognizes empty quoted strings in the input as null. Key: SPARK-15125 URL: https://issues.apache.org/jira/browse/SPARK-15125

[jira] [Commented] (SPARK-15112) Dataset filter returns garbage

[ https://issues.apache.org/jira/browse/SPARK-15112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15271576#comment-15271576 ] Suresh Thalamati commented on SPARK-15112: -- I ran into similar issue SPARK-14218 > Dataset

[jira] [Commented] (SPARK-14586) SparkSQL doesn't parse decimal like Hive

[ https://issues.apache.org/jira/browse/SPARK-14586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243702#comment-15243702 ] Suresh Thalamati commented on SPARK-14586: -- Thanks for reporting this issue , Stephane. which

[jira] [Commented] (SPARK-14343) Dataframe operations on a partitioned dataset (using partition discovery) return invalid results

[ https://issues.apache.org/jira/browse/SPARK-14343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246195#comment-15246195 ] Suresh Thalamati commented on SPARK-14343: -- This issue may be related to SPARK-14463. >

[jira] [Resolved] (SPARK-14218) dataset show() does not display column names in the correct order if underlying data frame schema order is different from the encoder schema order.

[ https://issues.apache.org/jira/browse/SPARK-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Thalamati resolved SPARK-14218. -- Resolution: Duplicate verified on 2.0 , and trunk. This issue is resolved. > dataset

[jira] [Commented] (SPARK-19318) Docker test case failure: `SPARK-16625: General data types to be mapped to Oracle`

[ https://issues.apache.org/jira/browse/SPARK-19318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832659#comment-15832659 ] Suresh Thalamati commented on SPARK-19318: -- I am looking into this test failure. > Docker test

[jira] [Commented] (SPARK-17385) Update Data in mySql using spark

[ https://issues.apache.org/jira/browse/SPARK-17385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459827#comment-15459827 ] Suresh Thalamati commented on SPARK-17385: -- Update is not supported from spark. Only option

[jira] [Created] (SPARK-17473) jdbc docker tests are failing with java.lang.AbstractMethodError:

Suresh Thalamati created SPARK-17473: Summary: jdbc docker tests are failing with java.lang.AbstractMethodError: Key: SPARK-17473 URL: https://issues.apache.org/jira/browse/SPARK-17473 Project:

[jira] [Commented] (SPARK-17473) jdbc docker tests are failing with java.lang.AbstractMethodError:

[ https://issues.apache.org/jira/browse/SPARK-17473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477624#comment-15477624 ] Suresh Thalamati commented on SPARK-17473: -- E-mail exchange on dev :

[jira] [Reopened] (SPARK-14536) NPE in JDBCRDD when array column contains nulls (postgresql)

[ https://issues.apache.org/jira/browse/SPARK-14536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Thalamati reopened SPARK-14536: -- SPARK-10186 added array data type support for postgres in 1.6. NPE issues still

[jira] [Commented] (SPARK-14536) NPE in JDBCRDD when array column contains nulls (postgresql)

[ https://issues.apache.org/jira/browse/SPARK-14536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514129#comment-15514129 ] Suresh Thalamati commented on SPARK-14536: -- [~sowen] I am not sure why this issue got closed

[jira] [Commented] (SPARK-14536) NPE in JDBCRDD when array column contains nulls (postgresql)

[ https://issues.apache.org/jira/browse/SPARK-14536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514246#comment-15514246 ] Suresh Thalamati commented on SPARK-14536: -- Yes. SPARK-10186 already added array support for

[jira] [Created] (SPARK-18141) jdbc datasource read fails when quoted columns (eg:mixed case, reserved words) in source table are used in the filter.

Suresh Thalamati created SPARK-18141: Summary: jdbc datasource read fails when quoted columns (eg:mixed case, reserved words) in source table are used in the filter. Key: SPARK-18141 URL:

[jira] [Commented] (SPARK-17916) CSV data source treats empty string as null no matter what nullValue option is

[ https://issues.apache.org/jira/browse/SPARK-17916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651172#comment-15651172 ] Suresh Thalamati commented on SPARK-17916: -- @Eric Liang If it is possible , can you please

[jira] [Commented] (SPARK-17916) CSV data source treats empty string as null no matter what nullValue option is

[ https://issues.apache.org/jira/browse/SPARK-17916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15593119#comment-15593119 ] Suresh Thalamati commented on SPARK-17916: -- Thank you for trying out the different scenarios. I

[jira] [Created] (SPARK-21784) Add ALTER TABLE ADD CONSTRANT DDL to support defining primary key and foreign keys

Suresh Thalamati created SPARK-21784: Summary: Add ALTER TABLE ADD CONSTRANT DDL to support defining primary key and foreign keys Key: SPARK-21784 URL: https://issues.apache.org/jira/browse/SPARK-21784

[jira] [Commented] (SPARK-21784) Add ALTER TABLE ADD CONSTRANT DDL to support defining primary key and foreign keys

[ https://issues.apache.org/jira/browse/SPARK-21784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131900#comment-16131900 ] Suresh Thalamati commented on SPARK-21784: -- I am working on implementation of this task. > Add

[jira] [Created] (SPARK-21823) ALTER TABLE table statements such as RENAME and CHANGE columns should raise error if there are any dependent constraints.

Suresh Thalamati created SPARK-21823: Summary: ALTER TABLE table statements such as RENAME and CHANGE columns should raise error if there are any dependent constraints. Key: SPARK-21823 URL:

[jira] [Created] (SPARK-21824) DROP TABLE should automatically drop any dependent referential constraints or raise error.

Suresh Thalamati created SPARK-21824: Summary: DROP TABLE should automatically drop any dependent referential constraints or raise error. Key: SPARK-21824 URL: