[jira] [Commented] (HIVE-2019) Implement NOW() UDF

2011-12-15 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170801#comment-13170801
 ] 

Priyadarshini commented on HIVE-2019:
-

I will implement 2 possible uses
One with default - now()
Other that takes a format as an argument and supports adding integer to it
i.e 
seelct now("format string") + 1 from 

> Implement NOW() UDF
> ---
>
> Key: HIVE-2019
> URL: https://issues.apache.org/jira/browse/HIVE-2019
> Project: Hive
>  Issue Type: New Feature
>  Components: UDF
>Reporter: Carl Steinbach
>
> Reference: 
> http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_now

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2019) Implement NOW() UDF

2011-12-15 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170798#comment-13170798
 ] 

Priyadarshini commented on HIVE-2019:
-

I am working on this.
I have few doubts to clarify with respect to this.
select now(),now() from 
The above query shud return the same time in both ofthe columns ? I find that 
in the reference link it does it.
One more doubt is if we want of this format,
select now()+0 from 
i.e adding some integers to the now() function, it shuould be possible that 
now() fucntion should take argument like which format user want.
So for operations for adding some integer to now() funciton, we may hav to pass 
the format also

> Implement NOW() UDF
> ---
>
> Key: HIVE-2019
> URL: https://issues.apache.org/jira/browse/HIVE-2019
> Project: Hive
>  Issue Type: New Feature
>  Components: UDF
>Reporter: Carl Steinbach
>
> Reference: 
> http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_now

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-1892) show functions also returns internal operators

2011-12-15 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170198#comment-13170198
 ] 

Priyadarshini commented on HIVE-1892:
-

FunctionRegistry.getFunctionNames() will return the set of all registered 
functions including the primitive constants.
So before sending to outstream, primitives will be removed and only the 
registered function names will be wriiten to outStream.

> show functions also returns internal operators
> --
>
> Key: HIVE-1892
> URL: https://issues.apache.org/jira/browse/HIVE-1892
> Project: Hive
>  Issue Type: Bug
>  Components: Security
>Reporter: Namit Jain
> Attachments: HIVE-1892.patch
>
>
> show functions: returns bigint etc. in its outputs, which are not valid 
> external functions

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2351) Partition names are not printed when hive.cli.print.header is set to 'true'

2011-12-14 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169982#comment-13169982
 ] 

Priyadarshini commented on HIVE-2351:
-

With the partitioned table, after setting hive.cli.print.header to true 
partition header is printed..
I think this issue is invalid

> Partition names are not printed when hive.cli.print.header is set to 'true' 
> 
>
> Key: HIVE-2351
> URL: https://issues.apache.org/jira/browse/HIVE-2351
> Project: Hive
>  Issue Type: Bug
>  Components: CLI
>Reporter: Amar Kamat
>
> When hive.cli.print.header is set to true, header information gets printed 
> along with the query output. With _select *_, the partition information also 
> gets printed along with the query result but the partition header (label) is 
> missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2558) Timestamp comparisons don't work

2011-12-13 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168407#comment-13168407
 ] 

Priyadarshini commented on HIVE-2558:
-

Hi Robert,

In the above query, timestamp is used as a column datatype of the table rrt.
So when u want to use the timestamp in the where clause of select statement, we 
should be able to tell that the data we are searching is a timestamp value.
Giving the field value in single/double quote will be treated as a string value 
and not timestamp value.
So when u wanted to retreive the results that satisfy the timestamp value you 
are specifying in where clause, the query should be

select * from rrt where r = unix_timestamp('1970-01-01 00:00:01');

This would be interpreted as data u r searching is a timestamp. 
Hope it helps 


Thanks,
Priya

> Timestamp comparisons don't work
> 
>
> Key: HIVE-2558
> URL: https://issues.apache.org/jira/browse/HIVE-2558
> Project: Hive
>  Issue Type: Bug
>Reporter: Robert Surówka
>
> I may be missing something, but:
> After performing:
> create table rrt (r timestamp);
> insert into table rrt select '1970-01-01 00:00:01' from src limit 1;
> Following queries give undesirable results:
> select * from rrt where r in ('1970-01-01 00:00:01');
> select * from rrt where r in (0); 
> select * from rrt where r = 0; 
> select * from rrt where r = '1970-01-01 00:00:01';
> At least for the first two, the reason may be the lack of timestamp in 
> numericTypes Map from FunctionRegistry.java (591) . Yet whether we really 
> want to have a linear hierarchy of primitive types in the end, is another 
> question.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2526) "lastAceesTime" is always zero when executed through "describe extended " unlike "show table extende like " where lastAccessTime is updated.

2011-12-12 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167438#comment-13167438
 ] 

Priyadarshini commented on HIVE-2526:
-

Thanks for the comments Namit..

In org.apache.hadoop.hive.metastore.api.Table, the field lastAccessTime has the 
datatype as int.
This field should be of type long for capturing the time information. So thrift 
side changes has to be done for changing the type.
Also "show table extended like " needs to be changed where it 
dynamically calculates the lastAccessTime from HDFS.
Now lastAccessTime has to be updated into metadata also.


> "lastAceesTime" is always zero when executed through "describe extended 
> " unlike "show table extende like "  where 
> lastAccessTime is updated.
> -
>
> Key: HIVE-2526
> URL: https://issues.apache.org/jira/browse/HIVE-2526
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.9.0
> Environment: Linux : SuSE 11 SP1
>Reporter: rohithsharma
>Assignee: Priyadarshini
>Priority: Minor
> Attachments: HIVE-2526.patch
>
>
> When the table is accessed(load),lastAccessTime is displaying updated 
> accessTime in 
> "show table extended like ".But "describe extended " 
> is always displaying zero.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2422) remove the intermediate dir when the hive query finish

2011-11-30 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160067#comment-13160067
 ] 

Priyadarshini commented on HIVE-2422:
-

I have executed this query.

select a.rollNo,b.rollNo from student a join student b on a.rollNo=b.rollNo 
group by a.rollNo,b.rollNo;

The above query has spawned 2 MR jobs.
After the execution of the query, org.apache.hadoop.hive.ql.Context.clear() 
method is deleting the ScratchDir of the query.

> remove the intermediate dir when the hive query finish 
> ---
>
> Key: HIVE-2422
> URL: https://issues.apache.org/jira/browse/HIVE-2422
> Project: Hive
>  Issue Type: Bug
>Reporter: He Yongqiang
>Assignee: He Yongqiang
>
> right now if one hive query got compiled to 2 mr jobs, and the first job's 
> output feed the second job. When the query finish, the first job's output 
> should be removed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2526) "lastAceesTime" is always zero when executed through "describe extended " unlike "show table extende like " where lastAccessTime is updated.

2011-11-20 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153997#comment-13153997
 ] 

Priyadarshini commented on HIVE-2526:
-

When "describe extended " is executed, lastAccessTime is always zero 
because its not gtting updated.
Now we have updated the lastAccessTime using the HDFS FileStatus api.


> "lastAceesTime" is always zero when executed through "describe extended 
> " unlike "show table extende like "  where 
> lastAccessTime is updated.
> -
>
> Key: HIVE-2526
> URL: https://issues.apache.org/jira/browse/HIVE-2526
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.9.0
> Environment: Linux : SuSE 11 SP1
>Reporter: rohithsharma
>Priority: Minor
> Attachments: HIVE-2526.patch
>
>
> When the table is accessed(load),lastAccessTime is displaying updated 
> accessTime in 
> "show table extended like ".But "describe extended " 
> is always displaying zero.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2235) Getting an SQLException when requesting Metadata about column 5 of Connection.getColumns()

2011-11-14 Thread Priyadarshini (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149635#comment-13149635
 ] 

Priyadarshini commented on HIVE-2235:
-

For repro3.java, I have verified with the trunk code. 
After getting the ColumnType from the ResultSetMetaData, i am not getting any 
SQL Exception.


> Getting an SQLException when requesting Metadata about column 5 of 
> Connection.getColumns()
> --
>
> Key: HIVE-2235
> URL: https://issues.apache.org/jira/browse/HIVE-2235
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Affects Versions: 0.7.0
> Environment: Connecting from 32bit Windows via JDBC to a Hive 
> installation on Linux Kernel-2.6.18-glibc-2.5 x86_64 64bit
>Reporter: Alex Piyevsky
> Attachments: repro3.class, repro3.java, repro3.log
>
>
> Getting an SQLException when requesting Metadata about column 5 of 
> Connection.getColumns() answer set.
> Failure occurs when invoking DatabaseMetaData.getColumnType(5), resulting in:
> java.sql.SQLException: Unrecognized column type: I32
> Repro materials are attached, please let me know if more info is required
> Here is the log that the repro generates:
> BUG SYNOPSIS: Getting error
>  "Unrecognized column type: I32" 
> returned by
> DatabaseMetadata.getColumnType(5) method call
> *
> DriverManager.getConnection
> Back from connecting
> Executing DatabaseMetaData.getColumns(null,null,"sergio",null)
> Print column types for columns of getColumns() answer set
> Column Type for column 1 is 12
> Column Type for column 2 is 12
> Column Type for column 3 is 12
> Column Type for column 4 is 12
> *** SQLException caught ***
> SQLState: null
> Message:  Unrecognized column type: I32
> Vendor:   0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira