[jira] Resolved: (HIVE-971) allow more tables in union all
[ https://issues.apache.org/jira/browse/HIVE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Liu resolved HIVE-971. -- Resolution: Fixed fixed already. > allow more tables in union all > --- > > Key: HIVE-971 > URL: https://issues.apache.org/jira/browse/HIVE-971 > Project: Hadoop Hive > Issue Type: Bug > Components: Query Processor >Reporter: Hao Liu > > We used to union more than 128 tables in hive, which did not work. But it is > a useful feature to support query aggregating multi fct tables. > (not sue if it is fixed already, pls. close the task if it is not true any > longer) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-971) allow more tables in union all
[ https://issues.apache.org/jira/browse/HIVE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789854#action_12789854 ] Hao Liu commented on HIVE-971: -- Try it again and It works, thanks! > allow more tables in union all > --- > > Key: HIVE-971 > URL: https://issues.apache.org/jira/browse/HIVE-971 > Project: Hadoop Hive > Issue Type: Bug > Components: Query Processor >Reporter: Hao Liu > > We used to union more than 128 tables in hive, which did not work. But it is > a useful feature to support query aggregating multi fct tables. > (not sue if it is fixed already, pls. close the task if it is not true any > longer) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-971) allow more tables in union all
allow more tables in union all --- Key: HIVE-971 URL: https://issues.apache.org/jira/browse/HIVE-971 Project: Hadoop Hive Issue Type: Bug Components: Query Processor Reporter: Hao Liu We used to union more than 128 tables in hive, which did not work. But it is a useful feature to support query aggregating multi fct tables. (not sue if it is fixed already, pls. close the task if it is not true any longer) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-667) Provide hive ql to check table/partition status, including size, creation and access timestamp
[ https://issues.apache.org/jira/browse/HIVE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735131#action_12735131 ] Hao Liu commented on HIVE-667: -- we can follow prev. naming convention: total number of files => totalNumberFiles or add "_", which is mysal way: total number of files => total_number_files > Provide hive ql to check table/partition status, including size, creation and > access timestamp > -- > > Key: HIVE-667 > URL: https://issues.apache.org/jira/browse/HIVE-667 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Hao Liu >Assignee: He Yongqiang > Attachments: hive-667-2009-07-24.patch, hive-667-2009-07-25.patch, > indented.txt, localtest-2009-07-24.txt > > > Those information will be helpful both for data management tasks, and users > who send adhoc queries against big data set in the cluster. . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-667) Provide hive ql to check table/partition status, including size, creation and access timestamp
[ https://issues.apache.org/jira/browse/HIVE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734896#action_12734896 ] Hao Liu commented on HIVE-667: -- "Describe extended" provides some static metadata informatio. But for those table info like size and access/update time, one needs to contact hdfs (or whatever storage layer hive use). I am thinking in terms of implementation, hive clik can provides this function? It can be part of metastore function though, which will work, but not necessary though if we want to decouple metastore and hdfs. My sql provide similar function: http://dev.mysql.com/doc/refman/5.1/en/show-table-status.html > Provide hive ql to check table/partition status, including size, creation and > access timestamp > -- > > Key: HIVE-667 > URL: https://issues.apache.org/jira/browse/HIVE-667 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Hao Liu >Assignee: He Yongqiang > > Those information will be helpful both for data management tasks, and users > who send adhoc queries against big data set in the cluster. . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-667) Provide hive ql to check table/partition status, including size, creation and access timestamp
Provide hive ql to check table/partition status, including size, creation and access timestamp -- Key: HIVE-667 URL: https://issues.apache.org/jira/browse/HIVE-667 Project: Hadoop Hive Issue Type: New Feature Components: Query Processor Reporter: Hao Liu Those information will be helpful both for data management tasks, and users who send adhoc queries against big data set in the cluster. . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-665) Allow to query hadoop/mapreduce cluster status from hive server
Allow to query hadoop/mapreduce cluster status from hive server --- Key: HIVE-665 URL: https://issues.apache.org/jira/browse/HIVE-665 Project: Hadoop Hive Issue Type: New Feature Components: Server Infrastructure Reporter: Hao Liu Tools/infra around hadoop/hive need to check cluster status in many cases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-319) add UDF UNIX_TIMESTAMP
[ https://issues.apache.org/jira/browse/HIVE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Liu updated HIVE-319: - Attachment: HIVE-319.3.patch I've moved the comments up to formatter. there are some tailing spaces in FunctionRegistry.java, I removed them when I add new udf. > add UDF UNIX_TIMESTAMP > -- > > Key: HIVE-319 > URL: https://issues.apache.org/jira/browse/HIVE-319 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor >Affects Versions: 0.3.0 >Reporter: Zheng Shao >Assignee: Hao Liu > Attachments: HIVE-319.2.patch, HIVE-319.3.patch, HIVE-319.patch > > > See > http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#function_unix-timestamp > For now, just use the default time zone. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-319) add UDF UNIX_TIMESTAMP
[
https://issues.apache.org/jira/browse/HIVE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Liu updated HIVE-319:
-
Attachment: HIVE-319.2.patch
add another version so user can specify time pattern, for example:
unix_timestamp('2009 Mar 20 11:30:01 am', ' MMM dd h:mm:ss a')
> add UDF UNIX_TIMESTAMP
> --
>
> Key: HIVE-319
> URL: https://issues.apache.org/jira/browse/HIVE-319
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
>Affects Versions: 0.3.0
>Reporter: Zheng Shao
>Assignee: Hao Liu
> Attachments: HIVE-319.2.patch, HIVE-319.patch
>
>
> See
> http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#function_unix-timestamp
> For now, just use the default time zone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-319) add UDF UNIX_TIMESTAMP
[
https://issues.apache.org/jira/browse/HIVE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Liu updated HIVE-319:
-
Attachment: HIVE-319.patch
add Unix_TimeStamp() and Unix_TimeStamp('-MM-dd HH:mm:ss')
> add UDF UNIX_TIMESTAMP
> --
>
> Key: HIVE-319
> URL: https://issues.apache.org/jira/browse/HIVE-319
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
>Affects Versions: 0.3.0
>Reporter: Zheng Shao
>Assignee: Hao Liu
> Attachments: HIVE-319.patch
>
>
> See
> http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#function_unix-timestamp
> For now, just use the default time zone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-319) add UDF UNIX_TIMESTAMP
[
https://issues.apache.org/jira/browse/HIVE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Liu updated HIVE-319:
-
Comment: was deleted
(was: add Unix_TimeStamp() and Unix_TimeStamp('-MM-dd HH:mm:ss'))
> add UDF UNIX_TIMESTAMP
> --
>
> Key: HIVE-319
> URL: https://issues.apache.org/jira/browse/HIVE-319
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
>Affects Versions: 0.3.0
>Reporter: Zheng Shao
>Assignee: Hao Liu
> Attachments: HIVE-319.patch
>
>
> See
> http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#function_unix-timestamp
> For now, just use the default time zone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-319) add UDF UNIX_TIMESTAMP
[
https://issues.apache.org/jira/browse/HIVE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Liu updated HIVE-319:
-
Status: Patch Available (was: Open)
add Unix_TimeStamp() and Unix_TimeStamp('-MM-dd HH:mm:ss')
> add UDF UNIX_TIMESTAMP
> --
>
> Key: HIVE-319
> URL: https://issues.apache.org/jira/browse/HIVE-319
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
>Affects Versions: 0.3.0
>Reporter: Zheng Shao
>Assignee: Hao Liu
>
> See
> http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#function_unix-timestamp
> For now, just use the default time zone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-261) union all query hangs
union all query hangs - Key: HIVE-261 URL: https://issues.apache.org/jira/browse/HIVE-261 Project: Hadoop Hive Issue Type: Bug Components: Query Processor Reporter: Hao Liu we have this query: SELECT a.u, b.id FROM ( SELECT a1.u, a1.id as id FROM t_1 a1 WHERE a1.date = '2009-01-01' UNION ALL SELECT a2.u, a2.id as id FROM t_2 a2 WHERE a2.date = '2009-01-01' UNION ALL ... SELECT aN.u, aN.id as id FROM t_N an WHERE aN.date = '2009-01-01' ) a JOIN t b ON a.id = b.id WHERE b.date='2009-01-01' GROUP BY a.u, b.id When we union more than 20 tables, the query will hang. It looks like something wrong in the compiler. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-163) support loading json data into hive
[ https://issues.apache.org/jira/browse/HIVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Liu updated HIVE-163: - Attachment: HIVE-163.4.patch add patch to .classpath. also it looks like build-common.xml was not in HIVE-163.3.patch, so add to this one. > support loading json data into hive > --- > > Key: HIVE-163 > URL: https://issues.apache.org/jira/browse/HIVE-163 > Project: Hadoop Hive > Issue Type: New Feature > Components: Serializers/Deserializers >Reporter: Hao Liu >Assignee: Hao Liu > Fix For: 0.2.0 > > Attachments: HIVE-163.2.patch, HIVE-163.3.patch, HIVE-163.4.patch, > HIVE-163.patch, json.jar > > Original Estimate: 168h > Remaining Estimate: 168h > > The JSON format is commonly used for transmitting structured data over a > network, especially for ajax web applications. People also choose json format > to store log data. > Support loading and query json format data will be a desirable features in > Hive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HIVE-163) support loading json data into hive
[ https://issues.apache.org/jira/browse/HIVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Liu reassigned HIVE-163: Assignee: Hao Liu > support loading json data into hive > --- > > Key: HIVE-163 > URL: https://issues.apache.org/jira/browse/HIVE-163 > Project: Hadoop Hive > Issue Type: New Feature > Components: Serializers/Deserializers >Reporter: Hao Liu >Assignee: Hao Liu > Attachments: HIVE-163.patch, json.jar > > Original Estimate: 168h > Remaining Estimate: 168h > > The JSON format is commonly used for transmitting structured data over a > network, especially for ajax web applications. People also choose json format > to store log data. > Support loading and query json format data will be a desirable features in > Hive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-163) support loading json data into hive
[
https://issues.apache.org/jira/browse/HIVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Liu updated HIVE-163:
-
Attachment: json.jar
json.jar from hadoop project. It should be included in ${hive.root}/lib
> support loading json data into hive
> ---
>
> Key: HIVE-163
> URL: https://issues.apache.org/jira/browse/HIVE-163
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Serializers/Deserializers
>Reporter: Hao Liu
> Attachments: HIVE-163.patch, json.jar
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The JSON format is commonly used for transmitting structured data over a
> network, especially for ajax web applications. People also choose json format
> to store log data.
> Support loading and query json format data will be a desirable features in
> Hive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-163) support loading json data into hive
[ https://issues.apache.org/jira/browse/HIVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Liu updated HIVE-163: - Attachment: HIVE-163.patch add a patch to support json udf as suggested. > support loading json data into hive > --- > > Key: HIVE-163 > URL: https://issues.apache.org/jira/browse/HIVE-163 > Project: Hadoop Hive > Issue Type: New Feature > Components: Serializers/Deserializers >Reporter: Hao Liu > Attachments: HIVE-163.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > The JSON format is commonly used for transmitting structured data over a > network, especially for ajax web applications. People also choose json format > to store log data. > Support loading and query json format data will be a desirable features in > Hive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-163) support loading json data into hive
support loading json data into hive --- Key: HIVE-163 URL: https://issues.apache.org/jira/browse/HIVE-163 Project: Hadoop Hive Issue Type: New Feature Components: Serializers/Deserializers Reporter: Hao Liu The JSON format is commonly used for transmitting structured data over a network, especially for ajax web applications. People also choose json format to store log data. Support loading and query json format data will be a desirable features in Hive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-141) drop table partition behaving oddly - does not create subdirectories
drop table partition behaving oddly - does not create subdirectories Key: HIVE-141 URL: https://issues.apache.org/jira/browse/HIVE-141 Project: Hadoop Hive Issue Type: Bug Components: Metastore Affects Versions: 0.20.0 Reporter: Hao Liu for example, I have a table, which has two partitions: tmp_table_name/dt=2008-11-01 tmp_table_name/dt=2008-11-02 When we use hive metastore to drop the first partition (as root), I expect the data file will be moved to user/root/.Trash/081103/tmp_table_name/dt=2008-11-01 by default. However, directory tmp_table_name was not created, the data was moved to user/root/.Trash/081103/dt=2008-11-01, which makes data recovery a very difficult task. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
