[jira] [Commented] (HIVE-2848) Add validation to HiveConf ConfVars
[ https://issues.apache.org/jira/browse/HIVE-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244001#comment-13244001 ] Phabricator commented on HIVE-2848: --- navis has commented on the revision "HIVE-2848 [jira] Add validation to HiveConf ConfVars". INLINE COMMENTS common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:534 I'll try to test with this option set 'true'. common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:600 Ok, I'll try. ql/src/java/org/apache/hadoop/hive/ql/processors/SetProcessor.java:138 I'm always misspelling 'hive.~' configuration, so it was added for me. Agree on this is not a common case and will be removed. REVISION DETAIL https://reviews.facebook.net/D2313 > Add validation to HiveConf ConfVars > --- > > Key: HIVE-2848 > URL: https://issues.apache.org/jira/browse/HIVE-2848 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.9.0 >Reporter: Kevin Wilfong >Assignee: Navis > Attachments: HIVE-2848.D2313.1.patch, HIVE-2848.D2313.2.patch > > > It would be good if we could add some validation to ConfVars in the HiveConf > when they are set. > At least if a variable is supposed to be boolean, numeric, or > strict/nonstrict, it shouldn't be too difficult to check for these. -- 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] [Updated] (HIVE-2860) TestNegativeCliDriver autolocal1.q fails on 0.23
[ https://issues.apache.org/jira/browse/HIVE-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2860: -- Attachment: HIVE-2860.D2565.1.patch cwsteinbach requested code review of "HIVE-2860 [jira] TestNegativeCliDriver autolocal1.q fails on 0.23". Reviewers: JIRA HIVE-2860. TestNegativeCliDriver autolocal1.q fails on 0.23 TEST PLAN NONE REVISION DETAIL https://reviews.facebook.net/D2565 AFFECTED FILES ql/src/test/org/apache/hadoop/hive/ql/QTestUtil.java MANAGE HERALD DIFFERENTIAL RULES https://reviews.facebook.net/herald/view/differential/ WHY DID I GET THIS EMAIL? https://reviews.facebook.net/herald/transcript/5823/ Tip: use the X-Herald-Rules header to filter Herald messages in your client. > TestNegativeCliDriver autolocal1.q fails on 0.23 > > > Key: HIVE-2860 > URL: https://issues.apache.org/jira/browse/HIVE-2860 > Project: Hive > Issue Type: Bug > Components: Testing Infrastructure >Affects Versions: 0.9.0 >Reporter: Carl Steinbach >Assignee: Carl Steinbach > Fix For: 0.9.0 > > Attachments: HIVE-2860.D2253.1.patch, HIVE-2860.D2253.1.patch, > HIVE-2860.D2565.1.patch > > -- 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-2858) Cache remote map reduce job stack traces for additional logging
[ https://issues.apache.org/jira/browse/HIVE-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243998#comment-13243998 ] Phabricator commented on HIVE-2858: --- njain has commented on the revision "HIVE-2858 [jira] Cache remote map reduce job stack traces for additional logging". can you refresh and re-apply the patch ? It is not applying cleanly for me. REVISION DETAIL https://reviews.facebook.net/D2223 > Cache remote map reduce job stack traces for additional logging > --- > > Key: HIVE-2858 > URL: https://issues.apache.org/jira/browse/HIVE-2858 > Project: Hive > Issue Type: Improvement > Components: Logging >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2858.D2223.1.patch > > > Currently we are parsing the task logs for failed jobs for information to > display to the user in the CLI. In addition, we could parse those logs for > stack traces and store e them in the SessionState. This way, when we log > failed queries, these will give us a decent idea of why those queries failed. -- 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] [Updated] (HIVE-2858) Cache remote map reduce job stack traces for additional logging
[ https://issues.apache.org/jira/browse/HIVE-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2858: - Status: Open (was: Patch Available) > Cache remote map reduce job stack traces for additional logging > --- > > Key: HIVE-2858 > URL: https://issues.apache.org/jira/browse/HIVE-2858 > Project: Hive > Issue Type: Improvement > Components: Logging >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2858.D2223.1.patch > > > Currently we are parsing the task logs for failed jobs for information to > display to the user in the CLI. In addition, we could parse those logs for > stack traces and store e them in the SessionState. This way, when we log > failed queries, these will give us a decent idea of why those queries failed. -- 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-2848) Add validation to HiveConf ConfVars
[ https://issues.apache.org/jira/browse/HIVE-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243994#comment-13243994 ] Phabricator commented on HIVE-2848: --- njain has commented on the revision "HIVE-2848 [jira] Add validation to HiveConf ConfVars". INLINE COMMENTS common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:600 Looks good - a minor change, can you change the type to a ENUM ? It will just make the code easier. Otherwise, the changes look good. ql/src/java/org/apache/hadoop/hive/ql/processors/SetProcessor.java:138 Is this check valid ? I mean, aren't there hive parameters which dont start with "hive." ? common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:534 What will it take to change the default to true ? It should work - right, or will anything break ? REVISION DETAIL https://reviews.facebook.net/D2313 > Add validation to HiveConf ConfVars > --- > > Key: HIVE-2848 > URL: https://issues.apache.org/jira/browse/HIVE-2848 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.9.0 >Reporter: Kevin Wilfong >Assignee: Navis > Attachments: HIVE-2848.D2313.1.patch, HIVE-2848.D2313.2.patch > > > It would be good if we could add some validation to ConfVars in the HiveConf > when they are set. > At least if a variable is supposed to be boolean, numeric, or > strict/nonstrict, it shouldn't be too difficult to check for these. -- 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] [Updated] (HIVE-2848) Add validation to HiveConf ConfVars
[ https://issues.apache.org/jira/browse/HIVE-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2848: - Status: Open (was: Patch Available) Comments on arc diff > Add validation to HiveConf ConfVars > --- > > Key: HIVE-2848 > URL: https://issues.apache.org/jira/browse/HIVE-2848 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.9.0 >Reporter: Kevin Wilfong >Assignee: Navis > Attachments: HIVE-2848.D2313.1.patch, HIVE-2848.D2313.2.patch > > > It would be good if we could add some validation to ConfVars in the HiveConf > when they are set. > At least if a variable is supposed to be boolean, numeric, or > strict/nonstrict, it shouldn't be too difficult to check for these. -- 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] [Updated] (HIVE-2881) Remove redundant key comparing in SMBMapJoinOperator
[ https://issues.apache.org/jira/browse/HIVE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2881: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed. Thanks Navis > Remove redundant key comparing in SMBMapJoinOperator > > > Key: HIVE-2881 > URL: https://issues.apache.org/jira/browse/HIVE-2881 > Project: Hive > Issue Type: Improvement > Components: Query Processor >Reporter: Navis >Assignee: Navis >Priority: Minor > Attachments: HIVE-2881.D2379.1.patch > > > Currently, SMBJoin compares keys twice in #findSmallestKey and #joinObject. -- 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-2881) Remove redundant key comparing in SMBMapJoinOperator
[ https://issues.apache.org/jira/browse/HIVE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243986#comment-13243986 ] Phabricator commented on HIVE-2881: --- njain has accepted the revision "HIVE-2881 [jira] Remove redundant key comparing in SMBMapJoinOperator". Looks good - I know this did not have good comments to start with, but it would be great if you can add more comments for changes like this. It took me a very long time to go over the code and make sure we are not missing any boundary condition. An example would have really helped. REVISION DETAIL https://reviews.facebook.net/D2379 BRANCH DPAL-988 > Remove redundant key comparing in SMBMapJoinOperator > > > Key: HIVE-2881 > URL: https://issues.apache.org/jira/browse/HIVE-2881 > Project: Hive > Issue Type: Improvement > Components: Query Processor >Reporter: Navis >Assignee: Navis >Priority: Minor > Attachments: HIVE-2881.D2379.1.patch > > > Currently, SMBJoin compares keys twice in #findSmallestKey and #joinObject. -- 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-2711) Make the header of RCFile unique
[ https://issues.apache.org/jira/browse/HIVE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243920#comment-13243920 ] Ashutosh Chauhan commented on HIVE-2711: Patch fails to apply. Needs to be rebased. > Make the header of RCFile unique > > > Key: HIVE-2711 > URL: https://issues.apache.org/jira/browse/HIVE-2711 > Project: Hive > Issue Type: Bug > Components: Serializers/Deserializers >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Attachments: HIVE-2711.D2115.1.patch > > > The RCFile implementation was copied from Hadoop's SequenceFile and copied > the 'magic' string in the header. This means that you can't use the header to > distinguish between RCFiles and SequenceFiles. > I'd propose that we create a new header for RCFiles (RCF?) to replace the > current SEQ. To maintain compatibility, we'll need to continue to accept the > current 'SEQ\06' and just make new files contain the new header. -- 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-2711) Make the header of RCFile unique
[ https://issues.apache.org/jira/browse/HIVE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243918#comment-13243918 ] Ashutosh Chauhan commented on HIVE-2711: I see. Yeah, very first commit of RCFile http://svn.apache.org/viewvc/hadoop/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/io/RCFile.java?view=markup&pathrev=770548 started with SEQ6 so there could possibly be no data written in RCFile format with version SEQ5 or earlier. So, backward compatibility with SEQ6 suffices. So, +1 will commit if tests pass. > Make the header of RCFile unique > > > Key: HIVE-2711 > URL: https://issues.apache.org/jira/browse/HIVE-2711 > Project: Hive > Issue Type: Bug > Components: Serializers/Deserializers >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Attachments: HIVE-2711.D2115.1.patch > > > The RCFile implementation was copied from Hadoop's SequenceFile and copied > the 'magic' string in the header. This means that you can't use the header to > distinguish between RCFiles and SequenceFiles. > I'd propose that we create a new header for RCFiles (RCF?) to replace the > current SEQ. To maintain compatibility, we'll need to continue to accept the > current 'SEQ\06' and just make new files contain the new header. -- 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-2711) Make the header of RCFile unique
[ https://issues.apache.org/jira/browse/HIVE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243910#comment-13243910 ] Phabricator commented on HIVE-2711: --- omalley has commented on the revision "HIVE-2711 [jira] Make the header of RCFile unique". Ashutosh, My point is that RCFile was *always* distinct from Sequence Files. RCFile was a fork of Sequence File when the Sequence File version was 6, therefore nothing before version 6 can possibly be an RCFile. Headers: Sequence Files: SEQ1, SEQ2, SEQ3, SEQ4, SEQ5, SEQ6 RCFiles: SEQ6, RCF1 Also note that SEQ5 was last written by Hadoop 0.10 back in Feb 2007, a year and a half before Hive was created. REVISION DETAIL https://reviews.facebook.net/D2115 > Make the header of RCFile unique > > > Key: HIVE-2711 > URL: https://issues.apache.org/jira/browse/HIVE-2711 > Project: Hive > Issue Type: Bug > Components: Serializers/Deserializers >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Attachments: HIVE-2711.D2115.1.patch > > > The RCFile implementation was copied from Hadoop's SequenceFile and copied > the 'magic' string in the header. This means that you can't use the header to > distinguish between RCFiles and SequenceFiles. > I'd propose that we create a new header for RCFiles (RCF?) to replace the > current SEQ. To maintain compatibility, we'll need to continue to accept the > current 'SEQ\06' and just make new files contain the new header. -- 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
Hive-trunk-h0.21 - Build # 1345 - Fixed
Changes for Build #1342 [namit] HIVE-2676 The row count that loaded to a table may not right (binlijin via namit) Changes for Build #1343 [namit] HIVE-2866 Cache local map reduce job errors for additional logging (Kevin Wilfong via namit) Changes for Build #1344 Changes for Build #1345 All tests passed The Apache Jenkins build system has built Hive-trunk-h0.21 (build #1345) Status: Fixed Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1345/ to view the results.
Debugging hive tasks?
Hey hive gurus - On the wiki I found a section about running Hive jobs in local mode, however, it uses a separate JVM. Is it possible to run the map reduce jobs inside the current process? I'm able to attach a debugger to the CLI process but haven't been able to figure out debugging the MR tasks. Any tips would be appreciated (and I'll update the wiki). https://cwiki.apache.org/confluence/display/Hive/GettingStarted#GettingStarted-Hive%2CMapReduceandLocalMode Thanks! Travis
[jira] [Updated] (HIVE-2910) Improve the HWI interface
[ https://issues.apache.org/jira/browse/HIVE-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers updated HIVE-2910: - Status: Patch Available (was: Open) > Improve the HWI interface > - > > Key: HIVE-2910 > URL: https://issues.apache.org/jira/browse/HIVE-2910 > Project: Hive > Issue Type: Improvement > Components: Web UI >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers >Priority: Minor > Labels: newbie, patch > Attachments: hive-2910.3.patch.log, hive-2910.3.patch.txt, > hive-hwi-2.patch, hive-hwi.patch, screenie001.PNG, screenie002.PNG > > > I've made some improvements to the HWI interface with the Twitter bootstrap > system. I'm looking for feedback on the new design. -- 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] [Updated] (HIVE-2910) Improve the HWI interface
[ https://issues.apache.org/jira/browse/HIVE-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers updated HIVE-2910: - Attachment: hive-2910.3.patch.txt hive-2910.3.patch.log This patch applies cleanly to revision 1308170. See patch.log > Improve the HWI interface > - > > Key: HIVE-2910 > URL: https://issues.apache.org/jira/browse/HIVE-2910 > Project: Hive > Issue Type: Improvement > Components: Web UI >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers >Priority: Minor > Labels: newbie, patch > Attachments: hive-2910.3.patch.log, hive-2910.3.patch.txt, > hive-hwi-2.patch, hive-hwi.patch, screenie001.PNG, screenie002.PNG > > > I've made some improvements to the HWI interface with the Twitter bootstrap > system. I'm looking for feedback on the new design. -- 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-2910) Improve the HWI interface
[
https://issues.apache.org/jira/browse/HIVE-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243739#comment-13243739
]
Edward Capriolo commented on HIVE-2910:
---
@Huge
Can you please regenerate the patch, so it can apply cleanly with patch -p0 <
../path-to-patch
{noformat}
--
|Index: hwi/web/session_list.jsp
|===
|--- hwi/web/session_list.jsp (revision 1305928)
|+++ hwi/web/session_list.jsp (working copy)
--
Patching file hwi/web/session_list.jsp using Plan A...
Hunk #1 succeeded at 14.
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
{noformat}
The best way to do this is:
cd hive-trunk
svn diff > /tmp/hive-2910.3.patch.txt
Then please mark this issue as patch available, and I will commit.
> Improve the HWI interface
> -
>
> Key: HIVE-2910
> URL: https://issues.apache.org/jira/browse/HIVE-2910
> Project: Hive
> Issue Type: Improvement
> Components: Web UI
>Reporter: Hugo Trippaers
>Assignee: Hugo Trippaers
>Priority: Minor
> Labels: newbie, patch
> Attachments: hive-hwi-2.patch, hive-hwi.patch, screenie001.PNG,
> screenie002.PNG
>
>
> I've made some improvements to the HWI interface with the Twitter bootstrap
> system. I'm looking for feedback on the new design.
--
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-2910) Improve the HWI interface
[ https://issues.apache.org/jira/browse/HIVE-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243731#comment-13243731 ] Edward Capriolo commented on HIVE-2910: --- +1. Very nice. As a follow up we might want to trim the QUERY box as it seems to have funky white space issues, but those were probably around before this patch. > Improve the HWI interface > - > > Key: HIVE-2910 > URL: https://issues.apache.org/jira/browse/HIVE-2910 > Project: Hive > Issue Type: Improvement > Components: Web UI >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers >Priority: Minor > Labels: newbie, patch > Attachments: hive-hwi-2.patch, hive-hwi.patch, screenie001.PNG, > screenie002.PNG > > > I've made some improvements to the HWI interface with the Twitter bootstrap > system. I'm looking for feedback on the new design. -- 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] [Updated] (HIVE-2917) Add support for various charsets in LazySimpleSerDe
[ https://issues.apache.org/jira/browse/HIVE-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Zhang updated HIVE-2917: Attachment: HIVE-2917.2.patch.txt Fixed a mistake in the last patch > Add support for various charsets in LazySimpleSerDe > --- > > Key: HIVE-2917 > URL: https://issues.apache.org/jira/browse/HIVE-2917 > Project: Hive > Issue Type: New Feature > Components: CLI, Serializers/Deserializers >Affects Versions: 0.9.0 >Reporter: Kai Zhang > Attachments: HIVE-2917.1.patch.txt, HIVE-2917.2.patch.txt > > > Currently hive can only serialize/deserialize data encoded in utf-8. > It would be useful to specify the data's charset when creating the table. > The idea is to add a new keyword CHARSET to set charset at table level. > For example: > CREATE TABLE tbl1 (col1 STRING) ROW FORMAT CHARET "GBK" DELIMITED FIELDS > TERMINATED BY '\t'; > Another place to use CHARSET is in TRANSFORM clause. > For example: > SELECT TRANSFORM(col1, col2) ROW FORMAT CHARSET 'gbk' > USING 'some_script' > AS (col3, col4) ROW FORMAT CHARSET 'utf-8'; -- 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] [Updated] (HIVE-2917) Add support for various charsets in LazySimpleSerDe
[ https://issues.apache.org/jira/browse/HIVE-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Zhang updated HIVE-2917: Attachment: HIVE-2917.1.patch.txt > Add support for various charsets in LazySimpleSerDe > --- > > Key: HIVE-2917 > URL: https://issues.apache.org/jira/browse/HIVE-2917 > Project: Hive > Issue Type: New Feature > Components: CLI, Serializers/Deserializers >Affects Versions: 0.9.0 >Reporter: Kai Zhang > Attachments: HIVE-2917.1.patch.txt > > > Currently hive can only serialize/deserialize data encoded in utf-8. > It would be useful to specify the data's charset when creating the table. > The idea is to add a new keyword CHARSET to set charset at table level. > For example: > CREATE TABLE tbl1 (col1 STRING) ROW FORMAT CHARET "GBK" DELIMITED FIELDS > TERMINATED BY '\t'; > Another place to use CHARSET is in TRANSFORM clause. > For example: > SELECT TRANSFORM(col1, col2) ROW FORMAT CHARSET 'gbk' > USING 'some_script' > AS (col3, col4) ROW FORMAT CHARSET 'utf-8'; -- 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] [Created] (HIVE-2917) Add support for various charsets in LazySimpleSerDe
Add support for various charsets in LazySimpleSerDe --- Key: HIVE-2917 URL: https://issues.apache.org/jira/browse/HIVE-2917 Project: Hive Issue Type: New Feature Components: CLI, Serializers/Deserializers Affects Versions: 0.9.0 Reporter: Kai Zhang Currently hive can only serialize/deserialize data encoded in utf-8. It would be useful to specify the data's charset when creating the table. The idea is to add a new keyword CHARSET to set charset at table level. For example: CREATE TABLE tbl1 (col1 STRING) ROW FORMAT CHARET "GBK" DELIMITED FIELDS TERMINATED BY '\t'; Another place to use CHARSET is in TRANSFORM clause. For example: SELECT TRANSFORM(col1, col2) ROW FORMAT CHARSET 'gbk' USING 'some_script' AS (col3, col4) ROW FORMAT CHARSET 'utf-8'; -- 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
