[jira] [Created] (SPARK-19971) Wired SELECT equal behaviour.

["Tom Tang (JIRA)" <ji...@apache.org>]

Tom Tang created SPARK-19971:
--------------------------------

             Summary: Wired SELECT equal behaviour. 
                 Key: SPARK-19971
                 URL: https://issues.apache.org/jira/browse/SPARK-19971
             Project: Spark
          Issue Type: Bug
          Components: SQL
    Affects Versions: 2.1.0
         Environment: macOS Sierra
            Reporter: Tom Tang
            Priority: Critical


Let say we have a csv /tmp/1.csv :
{quote}
cid,name
-100224910923912596,jack
-100224910923912595,tom
-1,rose
-2,marry
-100,rose1
-101,rose2
{quote}

Use following SQL to define a view in Spark-SQL:
CREATE TEMPORARY VIEW T
(
  `cid` string,
  `name` string
)
USING CSV
OPTIONS (
  path "/tmp/1.csv"
);

Statement 1:
{quote}select * from T where cid = -100224910923912596; {quote}

Returns:
{quote}
-100224910923912596	jack
-100224910923912595	tom
{quote}

Statement 2:
{quote}select * from T where cid = -100224910923912599;{quote}
it also returns:
{quote}
-100224910923912596	jack
-100224910923912595	tom
{quote}

Unless you do, 
{quote}select * from T where cid = '-100224910923912596';{quote}
It returns: 
{quote}
-100224910923912596	jack
{quote}

However, i think the expected behaviour for statement 1 and 2 is pretty wired.

Statement 4
{quote}select * from T where cid = -100;{quote}
Returns:
{quote}-100	rose1{quote}

And this just affect the large number, the smaller one seemed to be good.

Does that look like a bug to you folks ?

Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org