[jira] [Commented] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997272#comment-13997272
]
Anandha L Ranganathan commented on HIVE-5810:
-
The existing function DATE_ADD did not support to add day , month and year as
Unit. The expr unit is always days.
But this function has the support for DAY,MONTH and YEAR.
ADD_DATE(date, expr unit, INTERVAL).
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Attachments: HIVE-5810.2.patch, HIVE-5810.patch
>
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997273#comment-13997273
]
Anandha L Ranganathan commented on HIVE-5810:
-
I could have implemented in existing function with these feature, but that will
break already existing implementation in production.
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Attachments: HIVE-5810.2.patch, HIVE-5810.patch
>
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-6140) trim udf is very slow
[
https://issues.apache.org/jira/browse/HIVE-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868867#comment-13868867
]
Anandha L Ranganathan commented on HIVE-6140:
-
Here is the system configuration
4 core, 8 GB RAM.
file format: Text
compression : NONE
1) select count(l) from letters where l = 'l ';
around 100 seconds.
2) select count(l) from letters where trim(l) = 'l';
230 seconds
3)I created GenericUDF function for trim and the result was
select count(l) from letters where gentrim(l) = 'l';
220 seconds.
This evaluate function is taking around 1500 nano seconds processing for each
record. This nano seconds accumulates and takes 230 seconds when we use UDF
function for 500M records.
This is the code that is used in evaluate.
if (arguments[0].get() == null) {
return null;
}
input = (Text) converters[0].convert(arguments[0].get());
input.set(input.toString().trim());
[~ehans]]
I haven't tried ORC file format. I will try later.
> trim udf is very slow
> -
>
> Key: HIVE-6140
> URL: https://issues.apache.org/jira/browse/HIVE-6140
> Project: Hive
> Issue Type: Bug
> Components: UDF
>Reporter: Thejas M Nair
>Assignee: Anandha L Ranganathan
> Attachments: temp.pl
>
>
> Paraphrasing what was reported by [~cartershanklin] -
> I used the attached Perl script to generate 500 million two-character strings
> which always included a space. I loaded it using:
> create table letters (l string);
> load data local inpath '/home/sandbox/data.csv' overwrite into table letters;
> Then I ran this SQL script:
> select count(l) from letters where l = 'l ';
> select count(l) from letters where trim(l) = 'l';
> First query = 170 seconds
> Second query = 514 seconds
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HIVE-6140) trim udf is very slow
[ https://issues.apache.org/jira/browse/HIVE-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862177#comment-13862177 ] Anandha L Ranganathan commented on HIVE-6140: - [~thejas]/[~cartershanklin] Could you provide data.csv file that caused the problem. Otherwise provide example of the data. > trim udf is very slow > - > > Key: HIVE-6140 > URL: https://issues.apache.org/jira/browse/HIVE-6140 > Project: Hive > Issue Type: Bug > Components: UDF >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > > Paraphrasing what was reported by [~cartershanklin] - > I used the attached Perl script to generate 500 million two-character strings > which always included a space. I loaded it using: > create table letters (l string); > load data local inpath '/home/sandbox/data.csv' overwrite into table letters; > Then I ran this SQL script: > select count(l) from letters where l = 'l '; > select count(l) from letters where trim(l) = 'l'; > First query = 170 seconds > Second query = 514 seconds -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (HIVE-6140) trim udf is very slow
[ https://issues.apache.org/jira/browse/HIVE-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan reassigned HIVE-6140: --- Assignee: Anandha L Ranganathan > trim udf is very slow > - > > Key: HIVE-6140 > URL: https://issues.apache.org/jira/browse/HIVE-6140 > Project: Hive > Issue Type: Bug > Components: UDF >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > > Paraphrasing what was reported by [~cartershanklin] - > I used the attached Perl script to generate 500 million two-character strings > which always included a space. I loaded it using: > create table letters (l string); > load data local inpath '/home/sandbox/data.csv' overwrite into table letters; > Then I ran this SQL script: > select count(l) from letters where l = 'l '; > select count(l) from letters where trim(l) = 'l'; > First query = 170 seconds > Second query = 514 seconds -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HIVE-6036) A test case for embedded beeline - with URL jdbc:hive2:///default
[ https://issues.apache.org/jira/browse/HIVE-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848818#comment-13848818 ] Anandha L Ranganathan commented on HIVE-6036: - [~prasadm]] Attached test case for embedded beeline. > A test case for embedded beeline - with URL jdbc:hive2:///default > --- > > Key: HIVE-6036 > URL: https://issues.apache.org/jira/browse/HIVE-6036 > Project: Hive > Issue Type: Bug >Reporter: Anandha L Ranganathan >Assignee: Anandha L Ranganathan > Attachments: HIVE-6036.patch > > > A test case for embedded beeline would have been helpful. ie, with URL > jdbc:hive2:///default > This causes beeline (JDBC driver) to invoken embedded hive. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (HIVE-6036) A test case for embedded beeline - with URL jdbc:hive2:///default
[ https://issues.apache.org/jira/browse/HIVE-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-6036: Status: Patch Available (was: Open) > A test case for embedded beeline - with URL jdbc:hive2:///default > --- > > Key: HIVE-6036 > URL: https://issues.apache.org/jira/browse/HIVE-6036 > Project: Hive > Issue Type: Bug >Reporter: Anandha L Ranganathan >Assignee: Anandha L Ranganathan > Attachments: HIVE-6036.patch > > > A test case for embedded beeline would have been helpful. ie, with URL > jdbc:hive2:///default > This causes beeline (JDBC driver) to invoken embedded hive. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (HIVE-6036) A test case for embedded beeline - with URL jdbc:hive2:///default
[ https://issues.apache.org/jira/browse/HIVE-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-6036: Attachment: HIVE-6036.patch > A test case for embedded beeline - with URL jdbc:hive2:///default > --- > > Key: HIVE-6036 > URL: https://issues.apache.org/jira/browse/HIVE-6036 > Project: Hive > Issue Type: Bug >Reporter: Anandha L Ranganathan >Assignee: Anandha L Ranganathan > Attachments: HIVE-6036.patch > > > A test case for embedded beeline would have been helpful. ie, with URL > jdbc:hive2:///default > This causes beeline (JDBC driver) to invoken embedded hive. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848789#comment-13848789 ] Anandha L Ranganathan commented on HIVE-4256: - updated wrong patch > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.3.patch, > HIVE-4256.4.patch, HIVE-4256.5.patch, HIVE-4256.6.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4256: Attachment: HIVE-4256.6.patch > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.3.patch, > HIVE-4256.4.patch, HIVE-4256.5.patch, HIVE-4256.6.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848754#comment-13848754 ] Anandha L Ranganathan commented on HIVE-4256: - [~prasad mu],[~thejas] Modified the code and moved the test case to TestJdbcMiniHS2.java. > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.3.patch, > HIVE-4256.4.patch, HIVE-4256.5.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4256: Attachment: HIVE-4256.5.patch > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.3.patch, > HIVE-4256.4.patch, HIVE-4256.5.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848451#comment-13848451 ] Anandha L Ranganathan commented on HIVE-4256: - looking into this > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.3.patch, > HIVE-4256.4.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848428#comment-13848428 ] Anandha L Ranganathan commented on HIVE-4256: - [~prasadm] Thanks. I just noticed this morning. I was looking into that. > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.3.patch, > HIVE-4256.4.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Assigned] (HIVE-6036) A test case for embedded beeline - with URL jdbc:hive2:///default
[ https://issues.apache.org/jira/browse/HIVE-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan reassigned HIVE-6036: --- Assignee: Anandha L Ranganathan > A test case for embedded beeline - with URL jdbc:hive2:///default > --- > > Key: HIVE-6036 > URL: https://issues.apache.org/jira/browse/HIVE-6036 > Project: Hive > Issue Type: Bug >Reporter: Anandha L Ranganathan >Assignee: Anandha L Ranganathan > > A test case for embedded beeline would have been helpful. ie, with URL > jdbc:hive2:///default > This causes beeline (JDBC driver) to invoken embedded hive. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (HIVE-6036) A test case for embedded beeline - with URL jdbc:hive2:///default
Anandha L Ranganathan created HIVE-6036: --- Summary: A test case for embedded beeline - with URL jdbc:hive2:///default Key: HIVE-6036 URL: https://issues.apache.org/jira/browse/HIVE-6036 Project: Hive Issue Type: Bug Reporter: Anandha L Ranganathan A test case for embedded beeline would have been helpful. ie, with URL jdbc:hive2:///default This causes beeline (JDBC driver) to invoken embedded hive. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848230#comment-13848230 ] Anandha L Ranganathan commented on HIVE-4256: - I rebased and uploaded the code. > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.3.patch, > HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4256: Attachment: HIVE-4256.3.patch > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.3.patch, > HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847926#comment-13847926 ] Anandha L Ranganathan commented on HIVE-4256: - [~prasadm] I didn't get your comment "rebase". How do I do it. Could you explain in steps ? > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4256: Attachment: HIVE-4256.2.patch > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842014#comment-13842014 ] Anandha L Ranganathan commented on HIVE-4256: - attached the patch with indentation comments > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.2.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4256: Attachment: HIVE-4256.1.patch > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841024#comment-13841024 ] Anandha L Ranganathan commented on HIVE-4256: - updated the patch as per comments in RB > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.1.patch, HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839928#comment-13839928 ] Anandha L Ranganathan commented on HIVE-4256: - RB Link https://reviews.apache.org/r/16037/ > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4256: Status: Patch Available (was: Open) > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4256: Attachment: HIVE-4256.patch > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > Attachments: HIVE-4256.patch > > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan reassigned HIVE-4256: --- Assignee: Anandha L Ranganathan (was: Chris Drome) > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Anandha L Ranganathan > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Attachment: HIVE-5810.2.patch
updated patch
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Attachments: HIVE-5810.2.patch, HIVE-5810.patch
>
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830355#comment-13830355
]
Anandha L Ranganathan commented on HIVE-5810:
-
looking into that.
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Attachments: HIVE-5810.patch
>
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Status: Patch Available (was: In Progress)
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Attachments: HIVE-5810.patch
>
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Attachment: HIVE-5810.patch
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Attachments: HIVE-5810.patch
>
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Work started] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HIVE-5810 started by Anandha L Ranganathan.
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Attachments: HIVE-5810.patch
>
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828590#comment-13828590
]
Anandha L Ranganathan commented on HIVE-5810:
-
https://reviews.apache.org/r/15755/
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Description:
MySQL has ADDDATE(date,INTERVAL expr unit).
Similarly in Hive we can have (date,unit,expr).
Here Unit is DAY/Month/Year
For example,
add_date('2013-11-09','DAY',2) will return 2013-11-11.
add_date('2013-11-09','Month',2) will return 2014-01-09.
add_date('2013-11-09','Year',2) will return 2014-11-11.
was:
MySQL has ADDDATE(date,INTERVAL expr unit).
Similarly in Hive we can have (date,unit,expr).
For example,
ADDDATE('2013-11-09','DAY',2) will return 2013-11-11.
ADDDATE('2013-11-09','Month',2) will return 2014-01-09.
ADDDATE('2013-11-09','Year',2) will return 2014-11-09.
Here Unit is DAY/Month/Year
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> Here Unit is DAY/Month/Year
> For example,
> add_date('2013-11-09','DAY',2) will return 2013-11-11.
> add_date('2013-11-09','Month',2) will return 2014-01-09.
> add_date('2013-11-09','Year',2) will return 2014-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function add_date as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Summary: create a function add_date as exists in mysql (was: create a
function ADDDATE as exists in mysql )
> create a function add_date as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> For example,
> ADDDATE('2013-11-09','DAY',2) will return 2013-11-11.
> ADDDATE('2013-11-09','Month',2) will return 2014-01-09.
> ADDDATE('2013-11-09','Year',2) will return 2014-11-09.
> Here Unit is DAY/Month/Year
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828402#comment-13828402 ] Anandha L Ranganathan commented on HIVE-4256: - [~cdrome] If you are not working on this, can I take up this ticket. > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Chris Drome > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-4256) JDBC2 HiveConnection does not use the specified database
[ https://issues.apache.org/jira/browse/HIVE-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828379#comment-13828379 ] Anandha L Ranganathan commented on HIVE-4256: - I can take it up this ticket. > JDBC2 HiveConnection does not use the specified database > > > Key: HIVE-4256 > URL: https://issues.apache.org/jira/browse/HIVE-4256 > Project: Hive > Issue Type: Bug > Components: HiveServer2, JDBC >Affects Versions: 0.11.0 >Reporter: Chris Drome >Assignee: Chris Drome > > HiveConnection ignores the database specified in the connection string when > configuring the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-2974) Add online docs for from_utc_timestamp() and to_utc_timestamp()
[ https://issues.apache.org/jira/browse/HIVE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-2974: Attachment: HIVE-2974.2.patch > Add online docs for from_utc_timestamp() and to_utc_timestamp() > --- > > Key: HIVE-2974 > URL: https://issues.apache.org/jira/browse/HIVE-2974 > Project: Hive > Issue Type: Task > Components: UDF >Reporter: Carl Steinbach >Assignee: Anandha L Ranganathan > Fix For: 0.13.0 > > Attachments: HIVE-2974.1.patch, HIVE-2974.2.patch > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-2974) Add online docs for from_utc_timestamp() and to_utc_timestamp()
[ https://issues.apache.org/jira/browse/HIVE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-2974: Attachment: (was: HIVE-2974.1.patch.txt) > Add online docs for from_utc_timestamp() and to_utc_timestamp() > --- > > Key: HIVE-2974 > URL: https://issues.apache.org/jira/browse/HIVE-2974 > Project: Hive > Issue Type: Task > Components: UDF >Reporter: Carl Steinbach >Assignee: Anandha L Ranganathan > Fix For: 0.13.0 > > Attachments: HIVE-2974.1.patch, HIVE-2974.2.patch > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-2974) Add online docs for from_utc_timestamp() and to_utc_timestamp()
[ https://issues.apache.org/jira/browse/HIVE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823359#comment-13823359 ] Anandha L Ranganathan commented on HIVE-2974: - updated the patch with test case > Add online docs for from_utc_timestamp() and to_utc_timestamp() > --- > > Key: HIVE-2974 > URL: https://issues.apache.org/jira/browse/HIVE-2974 > Project: Hive > Issue Type: Task > Components: UDF >Reporter: Carl Steinbach >Assignee: Anandha L Ranganathan > Fix For: 0.13.0 > > Attachments: HIVE-2974.1.patch, HIVE-2974.2.patch > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-2974) Add online docs for from_utc_timestamp() and to_utc_timestamp()
[ https://issues.apache.org/jira/browse/HIVE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-2974: Attachment: HIVE-2974.1.patch > Add online docs for from_utc_timestamp() and to_utc_timestamp() > --- > > Key: HIVE-2974 > URL: https://issues.apache.org/jira/browse/HIVE-2974 > Project: Hive > Issue Type: Task > Components: UDF >Reporter: Carl Steinbach >Assignee: Anandha L Ranganathan > Fix For: 0.13.0 > > Attachments: HIVE-2974.1.patch, HIVE-2974.1.patch.txt > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function ADDDATE as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Description:
MySQL has ADDDATE(date,INTERVAL expr unit).
Similarly in Hive we can have (date,unit,expr).
For example,
ADDDATE('2013-11-09','DAY',2) will return 2013-11-11.
ADDDATE('2013-11-09','Month',2) will return 2014-01-09.
ADDDATE('2013-11-09','Year',2) will return 2014-11-09.
Here Unit is DAY/Month/Year
was:
MySQL has ADDDATE(date,INTERVAL expr unit).
Similarly in Hive we can have (date,unit,expr).
For example,
ADDDATE('2013-11-09','DAY',2) will return 2013-11-11.
ADDDATE('2013-11-09','Month',2) will return 2014-01-11.
ADDDATE('2013-11-09','Year',2) will return 2014-11-11.
Here Unit is DAY/Month/Year
> create a function ADDDATE as exists in mysql
> ---
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> For example,
> ADDDATE('2013-11-09','DAY',2) will return 2013-11-11.
> ADDDATE('2013-11-09','Month',2) will return 2014-01-09.
> ADDDATE('2013-11-09','Year',2) will return 2014-11-09.
> Here Unit is DAY/Month/Year
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function ADDDATE as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Description:
MySQL has ADDDATE(date,INTERVAL expr unit).
Similarly in Hive we can have (date,unit,expr).
For example,
ADDDATE('2013-11-09','DAY',2) will return 2013-11-11.
ADDDATE('2013-11-09','Month',2) will return 2014-01-11.
ADDDATE('2013-11-09','Year',2) will return 2014-11-11.
Here Unit is DAY/Month/Year
was:
MySQL has ADDDATE(date,INTERVAL expr unit).
Similarly in Hive we can have (date,unit,expr).
For example,
ADDDATE('2013-11-09',2,'DAY') will return 2013-11-11.
> create a function ADDDATE as exists in mysql
> ---
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> For example,
> ADDDATE('2013-11-09','DAY',2) will return 2013-11-11.
> ADDDATE('2013-11-09','Month',2) will return 2014-01-11.
> ADDDATE('2013-11-09','Year',2) will return 2014-11-11.
> Here Unit is DAY/Month/Year
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5810) create a function ADDDATE as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820958#comment-13820958
]
Anandha L Ranganathan commented on HIVE-5810:
-
The existing functiondate_add only able to add based on days.
SELECTdae_add('2009-30-07', 1) FROM src LIMIT 1;\n"
+ " '2009-31-07'")
Here is mysql example,
http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_adddate.
> create a function ADDDATE as exists in mysql
> ---
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> For example,
> ADDDATE('2013-11-09','DAY',2) will return 2013-11-11.
> ADDDATE('2013-11-09','Month',2) will return 2014-01-11.
> ADDDATE('2013-11-09','Year',2) will return 2014-11-11.
> Here Unit is DAY/Month/Year
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) ADDDATE function as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Summary: ADDDATE function as exists in mysql (was: AATE function as
exists in mysql )
> ADDDATE function as exists in mysql
>
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> For example,
> ADDDATE('2013-11-09',2,'DAY') will return 2013-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function ADDDATE function as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Summary: create a function ADDDATE function as exists in mysql (was:
ADDDATE function as exists in mysql )
> create a function ADDDATE function as exists in mysql
> --
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> For example,
> ADDDATE('2013-11-09',2,'DAY') will return 2013-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) ADDDDATE function as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Remaining Estimate: 40h (was: 168h)
Original Estimate: 40h (was: 168h)
> AATE function as exists in mysql
> -
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> For example,
> ADDDATE('2013-11-09',2,'DAY') will return 2013-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5810) create a function ADDDATE as exists in mysql
[
https://issues.apache.org/jira/browse/HIVE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anandha L Ranganathan updated HIVE-5810:
Summary: create a function ADDDATE as exists in mysql (was: create a
function ADDDATE function as exists in mysql )
> create a function ADDDATE as exists in mysql
> ---
>
> Key: HIVE-5810
> URL: https://issues.apache.org/jira/browse/HIVE-5810
> Project: Hive
> Issue Type: Improvement
>Reporter: Anandha L Ranganathan
>Assignee: Anandha L Ranganathan
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> MySQL has ADDDATE(date,INTERVAL expr unit).
> Similarly in Hive we can have (date,unit,expr).
> For example,
> ADDDATE('2013-11-09',2,'DAY') will return 2013-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (HIVE-5810) ADDDDATE function as exists in mysql
Anandha L Ranganathan created HIVE-5810:
---
Summary: AATE function as exists in mysql
Key: HIVE-5810
URL: https://issues.apache.org/jira/browse/HIVE-5810
Project: Hive
Issue Type: Improvement
Reporter: Anandha L Ranganathan
Assignee: Anandha L Ranganathan
MySQL has ADDDATE(date,INTERVAL expr unit).
Similarly in Hive we can have (date,unit,expr).
For example,
ADDDATE('2013-11-09',2,'DAY') will return 2013-11-11.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-2974) Add online docs for from_utc_timestamp() and to_utc_timestamp()
[ https://issues.apache.org/jira/browse/HIVE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-2974: Fix Version/s: 0.13.0 Release Note: patch available for this Status: Patch Available (was: Open) > Add online docs for from_utc_timestamp() and to_utc_timestamp() > --- > > Key: HIVE-2974 > URL: https://issues.apache.org/jira/browse/HIVE-2974 > Project: Hive > Issue Type: Task > Components: UDF >Reporter: Carl Steinbach >Assignee: Anandha L Ranganathan > Fix For: 0.13.0 > > Attachments: HIVE-2974.1.patch.txt > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-2974) Add online docs for from_utc_timestamp() and to_utc_timestamp()
[ https://issues.apache.org/jira/browse/HIVE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-2974: Attachment: HIVE-2974.1.patch.txt Carl, can you review this patch. > Add online docs for from_utc_timestamp() and to_utc_timestamp() > --- > > Key: HIVE-2974 > URL: https://issues.apache.org/jira/browse/HIVE-2974 > Project: Hive > Issue Type: Task > Components: UDF >Reporter: Carl Steinbach >Assignee: Anandha L Ranganathan > Attachments: HIVE-2974.1.patch.txt > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-2974) Add online docs for from_utc_timestamp() and to_utc_timestamp()
[ https://issues.apache.org/jira/browse/HIVE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820941#comment-13820941 ] Anandha L Ranganathan commented on HIVE-2974: - Here is the RB link. https://reviews.apache.org/r/15471/ > Add online docs for from_utc_timestamp() and to_utc_timestamp() > --- > > Key: HIVE-2974 > URL: https://issues.apache.org/jira/browse/HIVE-2974 > Project: Hive > Issue Type: Task > Components: UDF >Reporter: Carl Steinbach >Assignee: Anandha L Ranganathan > Attachments: HIVE-2974.1.patch.txt > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (HIVE-2974) Add online docs for from_utc_timestamp() and to_utc_timestamp()
[ https://issues.apache.org/jira/browse/HIVE-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan reassigned HIVE-2974: --- Assignee: Anandha L Ranganathan > Add online docs for from_utc_timestamp() and to_utc_timestamp() > --- > > Key: HIVE-2974 > URL: https://issues.apache.org/jira/browse/HIVE-2974 > Project: Hive > Issue Type: Task > Components: UDF >Reporter: Carl Steinbach >Assignee: Anandha L Ranganathan > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5162) Add mod(a, b) semantic for modular function
[ https://issues.apache.org/jira/browse/HIVE-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800220#comment-13800220 ] Anandha L Ranganathan commented on HIVE-5162: - It seems we already have pmod function available. select 44.22 %22,44.22%22.22,pmod(44.22,22),pmod(44.22,22.22) from dual limit 2; OK 0.21886 22.00.21886 22.0 0.21886 22.00.21886 22.0 Time taken: 20.954 seconds This will solve your requirement. Please let me know if we can close this ticket. > Add mod(a, b) semantic for modular function > --- > > Key: HIVE-5162 > URL: https://issues.apache.org/jira/browse/HIVE-5162 > Project: Hive > Issue Type: Improvement > Components: UDF >Affects Versions: 0.11.0 >Reporter: Xiu >Assignee: Anandha L Ranganathan >Priority: Minor > > Currently Hive is supporting 'a % b' as modular function, not mod(a, b). > Unlike MySQL which supports both. > It would be a good idea to support both. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (HIVE-5162) Add mod(a, b) semantic for modular function
[ https://issues.apache.org/jira/browse/HIVE-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan reassigned HIVE-5162: --- Assignee: Anandha L Ranganathan > Add mod(a, b) semantic for modular function > --- > > Key: HIVE-5162 > URL: https://issues.apache.org/jira/browse/HIVE-5162 > Project: Hive > Issue Type: Improvement > Components: UDF >Affects Versions: 0.11.0 >Reporter: Xiu >Assignee: Anandha L Ranganathan >Priority: Minor > > Currently Hive is supporting 'a % b' as modular function, not mod(a, b). > Unlike MySQL which supports both. > It would be a good idea to support both. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653594#comment-13653594 ] Anandha L Ranganathan commented on HIVE-4406: - updated the patch with test case. > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > Attachments: hive-4406.patch > > > When the jdbc uri does not have a / or "/default" after the hostname:port, > and the principal is specified, it ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:;principal=<>." results HS2 embedded mode > getting used. > "jdbc:hive2://:/;principal=<>" or > "jdbc:hive2://:/default;principal=<>" results in it connecting to > the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4406: Attachment: (was: hive_4406.patch) > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > Attachments: hive-4406.patch > > > When the jdbc uri does not have a / or "/default" after the hostname:port, > and the principal is specified, it ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:;principal=<>." results HS2 embedded mode > getting used. > "jdbc:hive2://:/;principal=<>" or > "jdbc:hive2://:/default;principal=<>" results in it connecting to > the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4406: Attachment: hive-4406.patch > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > Attachments: hive-4406.patch > > > When the jdbc uri does not have a / or "/default" after the hostname:port, > and the principal is specified, it ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:;principal=<>." results HS2 embedded mode > getting used. > "jdbc:hive2://:/;principal=<>" or > "jdbc:hive2://:/default;principal=<>" results in it connecting to > the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4406: Release Note: patch available for review Status: Patch Available (was: Open) > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > Attachments: hive_4406.patch > > > When the jdbc uri does not have a / or "/default" after the hostname:port, > and the principal is specified, it ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:;principal=<>." results HS2 embedded mode > getting used. > "jdbc:hive2://:/;principal=<>" or > "jdbc:hive2://:/default;principal=<>" results in it connecting to > the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646661#comment-13646661 ] Anandha L Ranganathan commented on HIVE-4406: - Please review the changes. https://reviews.apache.org/r/10859/ > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > Attachments: hive_4406.patch > > > When the jdbc uri does not have a / or "/default" after the hostname:port, > and the principal is specified, it ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:;principal=<>." results HS2 embedded mode > getting used. > "jdbc:hive2://:/;principal=<>" or > "jdbc:hive2://:/default;principal=<>" results in it connecting to > the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646660#comment-13646660 ] Anandha L Ranganathan commented on HIVE-4406: - https://reviews.apache.org/r/10859/ > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > Attachments: hive_4406.patch > > > When the jdbc uri does not have a / or "/default" after the hostname:port, > and the principal is specified, it ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:;principal=<>." results HS2 embedded mode > getting used. > "jdbc:hive2://:/;principal=<>" or > "jdbc:hive2://:/default;principal=<>" results in it connecting to > the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-4406: Attachment: hive_4406.patch attached patch for this bug. > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > Attachments: hive_4406.patch > > > When the jdbc uri does not have a / or "/default" after the hostname:port, > and the principal is specified, it ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:;principal=<>." results HS2 embedded mode > getting used. > "jdbc:hive2://:/;principal=<>" or > "jdbc:hive2://:/default;principal=<>" results in it connecting to > the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641390#comment-13641390 ] Anandha L Ranganathan commented on HIVE-4406: - thanks [~thejas]. I will let you know if I need more info. > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Anandha L Ranganathan > > When the jdbc uri does not have a / or "/default" after the hostname:port, > and the principal is specified, it ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:;principal=<>." results HS2 embedded mode > getting used. > "jdbc:hive2://:/;principal=<>" or > "jdbc:hive2://:/default;principal=<>" results in it connecting to > the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4406) Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode
[ https://issues.apache.org/jira/browse/HIVE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639787#comment-13639787 ] Anandha L Ranganathan commented on HIVE-4406: - thejas , If you are not working, I would like to assign this bug to myself. Can anyone add me into the contributors list so that I can assign it myself. > Missing "/" or "/" in hs2 jdbc uri switches mode to embedded mode > - > > Key: HIVE-4406 > URL: https://issues.apache.org/jira/browse/HIVE-4406 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair > > When the jdbc uri does not have a / or "/default" after the hostname:port, it > ends up launching HS2 in embedded mode. > This is because the parsing of uri in such case does not end up extracting > the hostname. > eg . "jdbc:hive2://:" results HS2 embedded mode getting used. > "jdbc:hive2://:/" or "jdbc:hive2://:/default" results > in it connecting to the standalone hive server 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589169#comment-13589169 ] Anandha L Ranganathan commented on HIVE-3850: - review request. https://reviews.apache.org/r/9673/ > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: hive-3850_1.patch, HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-3850: Attachment: hive-3850_1.patch > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: hive-3850_1.patch, HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-3850: Attachment: (was: hive-3850.patch_1.txt) > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: hive-3850_1.patch, HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-3850: Attachment: (was: hive-3850.patch) > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: hive-3850.patch_1.txt, HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-3850: Attachment: hive-3850.patch_1.txt > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: hive-3850.patch_1.txt, HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-3850: Attachment: hive-3850.patch re-attaching the patch > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: hive-3850.patch, HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandha L Ranganathan updated HIVE-3850: Attachment: (was: hive-3850.patch) > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588055#comment-13588055 ] Anandha L Ranganathan commented on HIVE-3850: - Arun, Still I didn't get it. If the test cases are okay, can you raise a review request. I don't have permission to raise a review request. ( I don't know how to raise a review request). > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: hive-3850.patch, HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3850) hour() function returns 12 hour clock value when using timestamp datatype
[ https://issues.apache.org/jira/browse/HIVE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577298#comment-13577298 ] Anandha L Ranganathan commented on HIVE-3850: - Hello Arun, Justification: You should read all the comments and the ticket was re-opened. Also, I added .q and .q.out in the patch. > hour() function returns 12 hour clock value when using timestamp datatype > - > > Key: HIVE-3850 > URL: https://issues.apache.org/jira/browse/HIVE-3850 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.9.0, 0.10.0 >Reporter: Pieterjan Vriends > Fix For: 0.11.0 > > Attachments: hive-3850.patch, HIVE-3850.patch.txt > > > Apparently UDFHour.java does have two evaluate() functions. One that does > accept a Text object as parameter and one that does use a TimeStampWritable > object as parameter. The first function does return the value of > Calendar.HOUR_OF_DAY and the second one of Calendar.HOUR. In the > documentation I couldn't find any information on the overload of the > evaluation function. I did spent quite some time finding out why my statement > didn't return a 24 hour clock value. > Shouldn't both functions return the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
