[jira] [Created] (SPARK-11817) insert of timestamp with factional seconds inserts a NULL

2015-11-18 Thread Chip Sands (JIRA) 
Chip Sands created SPARK-11817:
--

 Summary: insert of timestamp with factional seconds inserts a NULL
 Key: SPARK-11817
 URL: https://issues.apache.org/jira/browse/SPARK-11817
 Project: Spark
  Issue Type: Bug
Affects Versions: 1.5.1
Reporter: Chip Sands


Using the Thrift jdbc interface.

The insert of  the value of  "1970-01-01 00:00:00.123456789" to a timestamp 
column, inserts a NULL into the database. I am aware the of the change 
>From 1.5 releases notes  Timestamp Type’s precision is reduced to 1 
>microseconds (1us). However, to be compatible  with previous versions, I would 
>suggest either rounding or truncating the fractional seconds not inserting a 
>NULL. 



--
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

[jira] [Created] (SPARK-11660) Spark Thrift GetResultSetMetadata describes a VARCHAR as a STRING

2015-11-11 Thread Chip Sands (JIRA) 
Chip Sands created SPARK-11660:
--

 Summary: Spark Thrift GetResultSetMetadata describes a VARCHAR as 
a STRING
 Key: SPARK-11660
 URL: https://issues.apache.org/jira/browse/SPARK-11660
 Project: Spark
  Issue Type: Bug
Affects Versions: 1.5.0, 1.4.0
Reporter: Chip Sands


In the Spark SQL  thrift interface the GetResultSetMetadata reply packet that 
describes the result set metadata, reports a column that is defined as a 
VARCHAR in the database, as Native type of STRING. Data still returns correctly 
in the thrift string type but ODBC/JDBC is not able to correctly describe the 
data type being return or its defined maximum length.

FYI Hive returns it correctly.



--
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

[jira] [Created] (SPARK-11643) inserting date with leading zero inserts null example '0001-12-10'

2015-11-10 Thread Chip Sands (JIRA) 
Chip Sands created SPARK-11643:
--

 Summary: inserting date with leading zero inserts null example 
'0001-12-10'
 Key: SPARK-11643
 URL: https://issues.apache.org/jira/browse/SPARK-11643
 Project: Spark
  Issue Type: Bug
Reporter: Chip Sands


inserting date with leading zero inserts null value, example '0001-12-10'.
This worked until 1.5/1.5.1



--
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

[jira] [Commented] (SPARK-11643) inserting date with leading zero inserts null example '0001-12-10'

2015-11-10 Thread Chip Sands (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14999538#comment-14999538
 ] 

Chip Sands commented on SPARK-11643:


This is using beeline and thrift interface.

> inserting date with leading zero inserts null example '0001-12-10'
> --
>
> Key: SPARK-11643
> URL: https://issues.apache.org/jira/browse/SPARK-11643
> Project: Spark
>  Issue Type: Bug
>Reporter: Chip Sands
>
> inserting date with leading zero inserts null value, example '0001-12-10'.
> This worked until 1.5/1.5.1



--
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

[jira] [Commented] (SPARK-8181) date/time function: hour

2015-11-05 Thread Chip Sands (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991957#comment-14991957
 ] 

Chip Sands commented on SPARK-8181:
---

Using  Spark Thrift Server  hour( '1961-08-30 06:06:10')  is returning  (-17)  
for the hour in 1.5 and 1.5.1

> date/time function: hour
> 
>
> Key: SPARK-8181
> URL: https://issues.apache.org/jira/browse/SPARK-8181
> Project: Spark
>  Issue Type: Sub-task
>  Components: SQL
>Reporter: Reynold Xin
>Assignee: Tarek Auel
> Fix For: 1.5.0
>
>
> hour(string|date|timestamp): int
> Returns the hour of the timestamp: hour('2009-07-30 12:58:59') = 12, 
> hour('12:58:59') = 12.



--
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

[jira] [Commented] (SPARK-4496) smallint (16 bit value) is being send as a 32 bit value in the thrift interface.

2015-03-10 Thread Chip Sands (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14354978#comment-14354978
 ] 

Chip Sands commented on SPARK-4496:
---

getSchema() is describing a  result column  as a  smallint  (16 bit value).   
On the fetch()  the values is coming back as a 32 bit value.

So you allocate a  16 bit space for the result column and then a 32 bit value 
is coming back.  You should be returning smallint as a 16 bit value in the 
fetch.

 smallint (16 bit value)  is being send as a  32 bit  value in the thrift 
 interface.
 ---

 Key: SPARK-4496
 URL: https://issues.apache.org/jira/browse/SPARK-4496
 Project: Spark
  Issue Type: Bug
  Components: Input/Output
Affects Versions: 1.1.0
Reporter: Chip Sands





--
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

[jira] [Commented] (SPARK-4496) smallint (16 bit value) is being send as a 32 bit value in the thrift interface.

2015-03-10 Thread Chip Sands (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14355084#comment-14355084
 ] 

Chip Sands commented on SPARK-4496:
---

I have not look at the spark code. But it would be in the code that send the 
result set to thrift. My guess is a smallint is defined somewhere as and int 
(32 bit)
Hive does it correctly so maybe you can look there.

Just create a table with a smallint  datatype. 
Insert a row and select it back.

If you look at the packet trace you will see the getSchema, describes it 
correctly as the smallint , but the  select returns the data in a 32 bit thrift 
value..


 smallint (16 bit value)  is being send as a  32 bit  value in the thrift 
 interface.
 ---

 Key: SPARK-4496
 URL: https://issues.apache.org/jira/browse/SPARK-4496
 Project: Spark
  Issue Type: Bug
  Components: Input/Output
Affects Versions: 1.1.0
Reporter: Chip Sands





--
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

[jira] [Created] (SPARK-4496) smallint (16 bit value) is being send as a 32 bit value in the thrift interface.

2014-11-19 Thread Chip Sands (JIRA) 
Chip Sands created SPARK-4496:
-

 Summary: smallint (16 bit value)  is being send as a  32 bit  
value in the thrift interface.
 Key: SPARK-4496
 URL: https://issues.apache.org/jira/browse/SPARK-4496
 Project: Spark
  Issue Type: Bug
  Components: Input/Output
Affects Versions: 1.1.0
Reporter: Chip Sands






--
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