[jira] Created: (HIVE-1505) Support non-UTF8 data
Support non-UTF8 data - Key: HIVE-1505 URL: https://issues.apache.org/jira/browse/HIVE-1505 Project: Hadoop Hive Issue Type: New Feature Components: Serializers/Deserializers Affects Versions: 0.5.0 Reporter: bc Wong I'd like to work with non-UTF8 data easily. Suppose I have data in latin1. Currently, doing a "select *" will return the upper ascii characters in '\xef\xbf\xbd', which is the replacement character '\ufffd' encoded in UTF-8. Would be nice for Hive to understand different encodings, or to have a concept of byte string. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1211) Tapping logs from child processes
[
https://issues.apache.org/jira/browse/HIVE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1211:
--
Attachment: HIVE-1211-2.patch
> Tapping logs from child processes
> -
>
> Key: HIVE-1211
> URL: https://issues.apache.org/jira/browse/HIVE-1211
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Logging
>Reporter: bc Wong
>Assignee: bc Wong
> Fix For: 0.6.0
>
> Attachments: HIVE-1211-2.patch, HIVE-1211.1.patch
>
>
> Stdout/stderr from child processes (e.g. {{MapRedTask}}) are redirected to
> the parent's stdout/stderr. There is little one can do to to sort out which
> log is from which query.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1211) Tapping logs from child processes
[
https://issues.apache.org/jira/browse/HIVE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1211:
--
Status: Patch Available (was: Open)
Updated patch on 0.6 branch.
> Tapping logs from child processes
> -
>
> Key: HIVE-1211
> URL: https://issues.apache.org/jira/browse/HIVE-1211
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Logging
>Reporter: bc Wong
>Assignee: bc Wong
> Fix For: 0.6.0
>
> Attachments: HIVE-1211-2.patch, HIVE-1211.1.patch
>
>
> Stdout/stderr from child processes (e.g. {{MapRedTask}}) are redirected to
> the parent's stdout/stderr. There is little one can do to to sort out which
> log is from which query.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1261) ql.metadata.Hive#close() should check for null metaStoreClient
[
https://issues.apache.org/jira/browse/HIVE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1261:
--
Attachment: HIVE-1261-2.patch
Attaching HIVE-1261-2.patch, which fixes some style issues.
> ql.metadata.Hive#close() should check for null metaStoreClient
> --
>
> Key: HIVE-1261
> URL: https://issues.apache.org/jira/browse/HIVE-1261
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
>Reporter: bc Wong
>Assignee: bc Wong
> Attachments: HIVE-1261-1.patch, HIVE-1261-2.patch
>
>
> {{ql.metadata.Hive#close()}} always does a {{metaStoreClient.close()}}, even
> though it might be null.
> I'd like to reuse the same thread for multiple queries from different users.
> Since it's a different user, {{HiveConf}} has a new ugi. But it's not easy to
> get rid of (or update) the cached {{ql.metadata.Hive}}. The cleanest way
> seems to be {{Hive.closeCurrent()}}, which unfortunately doesn't check for
> the {{metaStoreClient}} being {{null}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1268) Cannot start metastore thrift server on a specific port
[
https://issues.apache.org/jira/browse/HIVE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1268:
--
Status: Patch Available (was: Open)
> Cannot start metastore thrift server on a specific port
> ---
>
> Key: HIVE-1268
> URL: https://issues.apache.org/jira/browse/HIVE-1268
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Metastore
>Reporter: bc Wong
>Assignee: bc Wong
> Attachments: HIVE-1268-1.patch
>
>
> The code to get the port number is broken. Doh.
> {code}
> 14:07:55[dsom:dist]$ METASTORE_PORT=12345 bin/hive --service metastore
> Starting Hive Metastore Server
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore.main(HiveMetaStore.java:960)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:156)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1268) Cannot start metastore thrift server on a specific port
[
https://issues.apache.org/jira/browse/HIVE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1268:
--
Attachment: HIVE-1268-1.patch
> Cannot start metastore thrift server on a specific port
> ---
>
> Key: HIVE-1268
> URL: https://issues.apache.org/jira/browse/HIVE-1268
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Metastore
>Reporter: bc Wong
>Assignee: bc Wong
> Attachments: HIVE-1268-1.patch
>
>
> The code to get the port number is broken. Doh.
> {code}
> 14:07:55[dsom:dist]$ METASTORE_PORT=12345 bin/hive --service metastore
> Starting Hive Metastore Server
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore.main(HiveMetaStore.java:960)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:156)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-1268) Cannot start metastore thrift server on a specific port
Cannot start metastore thrift server on a specific port
---
Key: HIVE-1268
URL: https://issues.apache.org/jira/browse/HIVE-1268
Project: Hadoop Hive
Issue Type: Bug
Components: Metastore
Reporter: bc Wong
Assignee: bc Wong
The code to get the port number is broken. Doh.
{code}
14:07:55[dsom:dist]$ METASTORE_PORT=12345 bin/hive --service metastore
Starting Hive Metastore Server
Exception in thread "main" java.lang.NullPointerException
at
org.apache.hadoop.hive.metastore.HiveMetaStore.main(HiveMetaStore.java:960)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.util.RunJar.main(RunJar.java:156)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1261) ql.metadata.Hive#close() should check for null metaStoreClient
[
https://issues.apache.org/jira/browse/HIVE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847750#action_12847750
]
bc Wong commented on HIVE-1261:
---
The new test in the patch would currently fail.
> ql.metadata.Hive#close() should check for null metaStoreClient
> --
>
> Key: HIVE-1261
> URL: https://issues.apache.org/jira/browse/HIVE-1261
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
>Reporter: bc Wong
> Attachments: HIVE-1261-1.patch
>
>
> {{ql.metadata.Hive#close()}} always does a {{metaStoreClient.close()}}, even
> though it might be null.
> I'd like to reuse the same thread for multiple queries from different users.
> Since it's a different user, {{HiveConf}} has a new ugi. But it's not easy to
> get rid of (or update) the cached {{ql.metadata.Hive}}. The cleanest way
> seems to be {{Hive.closeCurrent()}}, which unfortunately doesn't check for
> the {{metaStoreClient}} being {{null}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1261) ql.metadata.Hive#close() should check for null metaStoreClient
[
https://issues.apache.org/jira/browse/HIVE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1261:
--
Assignee: bc Wong
Status: Patch Available (was: Open)
> ql.metadata.Hive#close() should check for null metaStoreClient
> --
>
> Key: HIVE-1261
> URL: https://issues.apache.org/jira/browse/HIVE-1261
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
>Reporter: bc Wong
>Assignee: bc Wong
> Attachments: HIVE-1261-1.patch
>
>
> {{ql.metadata.Hive#close()}} always does a {{metaStoreClient.close()}}, even
> though it might be null.
> I'd like to reuse the same thread for multiple queries from different users.
> Since it's a different user, {{HiveConf}} has a new ugi. But it's not easy to
> get rid of (or update) the cached {{ql.metadata.Hive}}. The cleanest way
> seems to be {{Hive.closeCurrent()}}, which unfortunately doesn't check for
> the {{metaStoreClient}} being {{null}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1261) ql.metadata.Hive#close() should check for null metaStoreClient
[
https://issues.apache.org/jira/browse/HIVE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1261:
--
Attachment: HIVE-1261-1.patch
> ql.metadata.Hive#close() should check for null metaStoreClient
> --
>
> Key: HIVE-1261
> URL: https://issues.apache.org/jira/browse/HIVE-1261
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
>Reporter: bc Wong
> Attachments: HIVE-1261-1.patch
>
>
> {{ql.metadata.Hive#close()}} always does a {{metaStoreClient.close()}}, even
> though it might be null.
> I'd like to reuse the same thread for multiple queries from different users.
> Since it's a different user, {{HiveConf}} has a new ugi. But it's not easy to
> get rid of (or update) the cached {{ql.metadata.Hive}}. The cleanest way
> seems to be {{Hive.closeCurrent()}}, which unfortunately doesn't check for
> the {{metaStoreClient}} being {{null}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-1261) ql.metadata.Hive#close() should check for null metaStoreClient
ql.metadata.Hive#close() should check for null metaStoreClient
--
Key: HIVE-1261
URL: https://issues.apache.org/jira/browse/HIVE-1261
Project: Hadoop Hive
Issue Type: Bug
Components: Query Processor
Reporter: bc Wong
{{ql.metadata.Hive#close()}} always does a {{metaStoreClient.close()}}, even
though it might be null.
I'd like to reuse the same thread for multiple queries from different users.
Since it's a different user, {{HiveConf}} has a new ugi. But it's not easy to
get rid of (or update) the cached {{ql.metadata.Hive}}. The cleanest way seems
to be {{Hive.closeCurrent()}}, which unfortunately doesn't check for the
{{metaStoreClient}} being {{null}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-49) [Hive] display column header on CLI
[ https://issues.apache.org/jira/browse/HIVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847580#action_12847580 ] bc Wong commented on HIVE-49: - +1 At least a programmatic interface to get to the column names would be nice. > [Hive] display column header on CLI > --- > > Key: HIVE-49 > URL: https://issues.apache.org/jira/browse/HIVE-49 > Project: Hadoop Hive > Issue Type: Bug > Components: Clients >Reporter: YoungWoo Kim >Assignee: Edward Capriolo >Priority: Minor > > The result row(s) on CLI are displayed without column header. > It would be useful to be able to set header on or off by users. > for example, > hive> SET HEAD [ON|OFF]/* similar to oracle sql*plus syntax */ > or > hive> SET [GLOBAL|SESSION] HEADER=[ON|OFF]/* similar to mysql's "SET" > syntax */ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1211) Tapping logs from child processes
[
https://issues.apache.org/jira/browse/HIVE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842346#action_12842346
]
bc Wong commented on HIVE-1211:
---
I'd like to retrieve the logs related to a particular query.
SessionState.out and SessionState.err are meant for that exact purpose.
Unfortunately, they don't capture the child processes' output, which currently
goes directly to System.out and System.err. Therefore this patch introduces
SessionState.childout and SessionState.childerr, which by default (null) do
nothing. But it allows anyone to hook a stream there to get the child's output.
> Tapping logs from child processes
> -
>
> Key: HIVE-1211
> URL: https://issues.apache.org/jira/browse/HIVE-1211
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Logging
>Reporter: bc Wong
>Assignee: bc Wong
> Attachments: HIVE-1211.1.patch
>
>
> Stdout/stderr from child processes (e.g. {{MapRedTask}}) are redirected to
> the parent's stdout/stderr. There is little one can do to to sort out which
> log is from which query.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1211) Tapping logs from child processes
[
https://issues.apache.org/jira/browse/HIVE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1211:
--
Status: Patch Available (was: Open)
> Tapping logs from child processes
> -
>
> Key: HIVE-1211
> URL: https://issues.apache.org/jira/browse/HIVE-1211
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Logging
>Reporter: bc Wong
> Attachments: HIVE-1211.1.patch
>
>
> Stdout/stderr from child processes (e.g. {{MapRedTask}}) are redirected to
> the parent's stdout/stderr. There is little one can do to to sort out which
> log is from which query.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1211) Tapping logs from child processes
[
https://issues.apache.org/jira/browse/HIVE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bc Wong updated HIVE-1211:
--
Attachment: HIVE-1211.1.patch
> Tapping logs from child processes
> -
>
> Key: HIVE-1211
> URL: https://issues.apache.org/jira/browse/HIVE-1211
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Logging
>Reporter: bc Wong
> Attachments: HIVE-1211.1.patch
>
>
> Stdout/stderr from child processes (e.g. {{MapRedTask}}) are redirected to
> the parent's stdout/stderr. There is little one can do to to sort out which
> log is from which query.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1211) Tapping logs from child processes
[
https://issues.apache.org/jira/browse/HIVE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840834#action_12840834
]
bc Wong commented on HIVE-1211:
---
I'd like to change it to go through the {{SessionState}} first.
{{SessionState}} will have two new {{PrintStream}}, called {{childOut}} and
{{childErr}}, which are similar to the current {{out}} and {{err}}. They let
users tap into the child's output. If they're null, then the child's out will
continue on to stdout/stderr.
And this doesn't break any existing users who aren't interested in the child's
output. They can tap into {{SessionState.out|err}} and ignore the new fields.
> Tapping logs from child processes
> -
>
> Key: HIVE-1211
> URL: https://issues.apache.org/jira/browse/HIVE-1211
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Logging
>Reporter: bc Wong
>
> Stdout/stderr from child processes (e.g. {{MapRedTask}}) are redirected to
> the parent's stdout/stderr. There is little one can do to to sort out which
> log is from which query.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-1211) Tapping logs from child processes
Tapping logs from child processes
-
Key: HIVE-1211
URL: https://issues.apache.org/jira/browse/HIVE-1211
Project: Hadoop Hive
Issue Type: Improvement
Components: Logging
Reporter: bc Wong
Stdout/stderr from child processes (e.g. {{MapRedTask}}) are redirected to the
parent's stdout/stderr. There is little one can do to to sort out which log is
from which query.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-1206) Return row results in a list instead of a tab-delimited string
Return row results in a list instead of a tab-delimited string -- Key: HIVE-1206 URL: https://issues.apache.org/jira/browse/HIVE-1206 Project: Hadoop Hive Issue Type: Bug Reporter: bc Wong Driver.getResults() returns each row as a string, with fields tab delimited always. This breaks for data with tabs. It'd be really nice if the interface allows returning the row as a list of fields. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
