[jira] [Commented] (HIVE-1363) 'SHOW TABLE EXTENDED LIKE' command does not strip single/double quotes
[
https://issues.apache.org/jira/browse/HIVE-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14124348#comment-14124348
]
Pradeep Kamath commented on HIVE-1363:
--
This email account is inactive. Please contact another person at the company or
pe...@fb.com.
'SHOW TABLE EXTENDED LIKE' command does not strip single/double quotes
--
Key: HIVE-1363
URL: https://issues.apache.org/jira/browse/HIVE-1363
Project: Hive
Issue Type: Bug
Affects Versions: 0.5.0
Reporter: Carl Steinbach
Assignee: Chaoyu Tang
{code}
hive SHOW TABLE EXTENDED LIKE pokes;
OK
tableName:pokes
owner:carl
location:hdfs://localhost/user/hive/warehouse/pokes
inputformat:org.apache.hadoop.mapred.TextInputFormat
outputformat:org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat
columns:struct columns { i32 num}
partitioned:false
partitionColumns:
totalNumberFiles:0
totalFileSize:0
maxFileSize:0
minFileSize:0
lastAccessTime:0
lastUpdateTime:1274517075221
hive SHOW TABLE EXTENDED LIKE p*;
FAILED: Error in metadata: MetaException(message:Got exception:
javax.jdo.JDOUserException ')' expected at character 54 in database.name ==
dbName ( tableName.matches((?i)p.*)))
FAILED: Execution Error, return code 1 from
org.apache.hadoop.hive.ql.exec.DDLTask
hive SHOW TABLE EXTENDED LIKE 'p*';
OK
hive SHOW TABLE EXTENDED LIKE `p*`;
OK
tableName:pokes
owner:carl
location:hdfs://localhost/user/hive/warehouse/pokes
inputformat:org.apache.hadoop.mapred.TextInputFormat
outputformat:org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat
columns:struct columns { i32 num}
partitioned:false
partitionColumns:
totalNumberFiles:0
totalFileSize:0
maxFileSize:0
minFileSize:0
lastAccessTime:0
lastUpdateTime:1274517075221
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-3733) Improve Hive's logic for conditional merge
[ https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated HIVE-3733: - Attachment: HIVE-3733.optimizer.patch.txt Uploading a new version (attached as HIVE-3733.optimizer.patch.txt, I have also updated the phabricator review with this new code) based on new logic to work at the physical optimizer level. - I am still running the tests - this is an early preview so I know that I am on the right track - I feel like the wiring between stages is not quite right though I couldn't figure out enough to know - the creation of the ConditionalTask is pretty deep into the guts of task/operator code which I am not very familiar. For example, in the new union19.q.out, one of the stages (stage-6) is missing There maybe room for improving the code - I wanted early feedback - so please do review the code carefully. Improve Hive's logic for conditional merge -- Key: HIVE-3733 URL: https://issues.apache.org/jira/browse/HIVE-3733 Project: Hive Issue Type: Improvement Reporter: Pradeep Kamath Assignee: Pradeep Kamath Attachments: HIVE-3733.1.patch.txt, HIVE-3733.3.patch.txt, HIVE-3733.4.patch.txt, HIVE-3733.optimizer.patch.txt If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles is set to false then when hive encounters a FileSinkOperator when generating map reduce tasks, it will look at the entire job to see if it has a reducer, if it does it will not merge. Instead it should be check if the FileSinkOperator is a child of the reducer. This means that outputs generated in the mapper will be merged, and outputs generated in the reducer will not be, the intended effect of setting those configs. Simple repro: set hive.merge.mapfiles=true; set hive.merge.mapredfiles=false; EXPLAIN FROM input_table INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key INSERT OVERWRITE TABLE output_table2 SELECT *; The output should contain a Conditional Operator, Mapred Stages, and Move tasks -- 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-3733) Improve Hive's logic for conditional merge
[ https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated HIVE-3733: - Attachment: HIVE-3733.4.patch.txt Changed the code which looks in the Operator Stack to look for ReduceSinkOperator instead of the exact CurrWork.getReducer() instance. union19 no longer performs a conditional merge with this change. My hypothesis for this follows: The union19 query is: FROM (select 'tst1' as key, cast(count(1) as string) as value from src s1 UNION ALL select s2.key as key, s2.value as value from src s2) unionsrc INSERT OVERWRITE TABLE DEST1 SELECT unionsrc.key, count(unionsrc.value) group by unionsrc.key INSERT OVERWRITE TABLE DEST2 SELECT unionsrc.key, unionsrc.value, unionsrc.value; The from subquery has an implicit group by/ReduceSink due to the count. So though the second insert in the multi insert by itself does not have a groupby/ReduceSink, the subquery in the from clause causes the groupby/ReduceSink to appear in the stack and hence we decide not to do the conditional merge since the FileSink will be in the reduce. Improve Hive's logic for conditional merge -- Key: HIVE-3733 URL: https://issues.apache.org/jira/browse/HIVE-3733 Project: Hive Issue Type: Improvement Reporter: Pradeep Kamath Assignee: Pradeep Kamath Attachments: HIVE-3733.1.patch.txt, HIVE-3733.3.patch.txt, HIVE-3733.4.patch.txt If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles is set to false then when hive encounters a FileSinkOperator when generating map reduce tasks, it will look at the entire job to see if it has a reducer, if it does it will not merge. Instead it should be check if the FileSinkOperator is a child of the reducer. This means that outputs generated in the mapper will be merged, and outputs generated in the reducer will not be, the intended effect of setting those configs. Simple repro: set hive.merge.mapfiles=true; set hive.merge.mapredfiles=false; EXPLAIN FROM input_table INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key INSERT OVERWRITE TABLE output_table2 SELECT *; The output should contain a Conditional Operator, Mapred Stages, and Move tasks -- 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-3733) Improve Hive's logic for conditional merge
[ https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526161#comment-13526161 ] Pradeep Kamath commented on HIVE-3733: -- Hi Namit - HIVE-3733.4.patch.txt has the most recent full patch. Improve Hive's logic for conditional merge -- Key: HIVE-3733 URL: https://issues.apache.org/jira/browse/HIVE-3733 Project: Hive Issue Type: Improvement Reporter: Pradeep Kamath Assignee: Pradeep Kamath Attachments: HIVE-3733.1.patch.txt, HIVE-3733.3.patch.txt, HIVE-3733.4.patch.txt If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles is set to false then when hive encounters a FileSinkOperator when generating map reduce tasks, it will look at the entire job to see if it has a reducer, if it does it will not merge. Instead it should be check if the FileSinkOperator is a child of the reducer. This means that outputs generated in the mapper will be merged, and outputs generated in the reducer will not be, the intended effect of setting those configs. Simple repro: set hive.merge.mapfiles=true; set hive.merge.mapredfiles=false; EXPLAIN FROM input_table INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key INSERT OVERWRITE TABLE output_table2 SELECT *; The output should contain a Conditional Operator, Mapred Stages, and Move tasks -- 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-3733) Improve Hive's logic for conditional merge
[ https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated HIVE-3733: - Attachment: HIVE-3733.3.patch.txt This is the most recent patch file - please review - I have also uploaded this to the review at https://reviews.facebook.net/D6969 A couple of unit tests fail: 1) testCliDriver_groupby_multi_single_reducer This fails for me locally on trunk as well with a ClassNotFoundException for JSONFactory. 2) testNegativeCliDriver_stats_aggregator_error_1 Apparently this one is known to be flakey. Note that I needed to update union19.q.out to include the extra merge. Please review - Thanks! Improve Hive's logic for conditional merge -- Key: HIVE-3733 URL: https://issues.apache.org/jira/browse/HIVE-3733 Project: Hive Issue Type: Improvement Reporter: Pradeep Kamath Assignee: Pradeep Kamath Attachments: HIVE-3733.1.patch.txt, HIVE-3733.3.patch.txt If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles is set to false then when hive encounters a FileSinkOperator when generating map reduce tasks, it will look at the entire job to see if it has a reducer, if it does it will not merge. Instead it should be check if the FileSinkOperator is a child of the reducer. This means that outputs generated in the mapper will be merged, and outputs generated in the reducer will not be, the intended effect of setting those configs. Simple repro: set hive.merge.mapfiles=true; set hive.merge.mapredfiles=false; EXPLAIN FROM input_table INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key INSERT OVERWRITE TABLE output_table2 SELECT *; The output should contain a Conditional Operator, Mapred Stages, and Move tasks -- 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-3733) Improve Hive's logic for conditional merge
[ https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507055#comment-13507055 ] Pradeep Kamath commented on HIVE-3733: -- Re-running testCliDriver_groupby_multi_single_reducer locally I noticed it is failing because the new code is adding an additional conditional merge. The query is a multi insert one but all with map-reduce phases - so it appears like this is a regression. In the debugger I noticed: currWork.getReducer() is org.apache.hadoop.hive.ql.exec.ExtractOperator@66bb4c22 However stack does not contain it causing the merge operation to be added! Stack has: [org.apache.hadoop.hive.ql.exec.TableScanOperator@476acffa, org.apache.hadoop.hive.ql.exec.SelectOperator@3de76262, org.apache.hadoop.hive.ql.exec.ReduceSinkOperator@61607dda, org.apache.hadoop.hive.ql.exec.ForwardOperator@5e6a528, org.apache.hadoop.hive.ql.exec.FilterOperator@1b97680c, org.apache.hadoop.hive.ql.exec.GroupByOperator@712ff9fa, org.apache.hadoop.hive.ql.exec.SelectOperator@433d44fc, org.apache.hadoop.hive.ql.exec.SelectOperator@2c3b39be, org.apache.hadoop.hive.ql.exec.FileSinkOperator@397bd678] Any ideas why this is happening? Improve Hive's logic for conditional merge -- Key: HIVE-3733 URL: https://issues.apache.org/jira/browse/HIVE-3733 Project: Hive Issue Type: Improvement Reporter: Pradeep Kamath Assignee: Pradeep Kamath Attachments: HIVE-3733.1.patch.txt, HIVE-3733.3.patch.txt If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles is set to false then when hive encounters a FileSinkOperator when generating map reduce tasks, it will look at the entire job to see if it has a reducer, if it does it will not merge. Instead it should be check if the FileSinkOperator is a child of the reducer. This means that outputs generated in the mapper will be merged, and outputs generated in the reducer will not be, the intended effect of setting those configs. Simple repro: set hive.merge.mapfiles=true; set hive.merge.mapredfiles=false; EXPLAIN FROM input_table INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key INSERT OVERWRITE TABLE output_table2 SELECT *; The output should contain a Conditional Operator, Mapred Stages, and Move tasks -- 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-3733) Improve Hive's logic for conditional merge
[ https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated HIVE-3733: - Attachment: HIVE-3733.1.patch.txt Attaching patch to fix the issue (used git diff --no-prefix ...). I tried using arc diff --jira HIVE-3733 Got : PHP Fatal error: Call to undefined method ArcanistGitAPI::amendGitHeadCommit() in /Users/pradeepk/opensource-hive/.arc_jira_lib/arcanist/ArcJIRAConfiguration.php on line 173 I saw some other references to this error in different JIRAs but no solution suggested - is there a fix for this issue? So I manually uploaded a diff (used git diff ..) to create the review - https://reviews.facebook.net/D6969 Improve Hive's logic for conditional merge -- Key: HIVE-3733 URL: https://issues.apache.org/jira/browse/HIVE-3733 Project: Hive Issue Type: Improvement Reporter: Pradeep Kamath Assignee: Pradeep Kamath Attachments: HIVE-3733.1.patch.txt If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles is set to false then when hive encounters a FileSinkOperator when generating map reduce tasks, it will look at the entire job to see if it has a reducer, if it does it will not merge. Instead it should be check if the FileSinkOperator is a child of the reducer. This means that outputs generated in the mapper will be merged, and outputs generated in the reducer will not be, the intended effect of setting those configs. Simple repro: set hive.merge.mapfiles=true; set hive.merge.mapredfiles=false; EXPLAIN FROM input_table INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key INSERT OVERWRITE TABLE output_table2 SELECT *; The output should contain a Conditional Operator, Mapred Stages, and Move tasks -- 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-3733) Improve Hive's logic for conditional merge
[ https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503952#comment-13503952 ] Pradeep Kamath commented on HIVE-3733: -- Also on my Mac, a few tests fails testCliDriver_escape1 testCliDriver_escape2 testCliDriver_join29 testCliDriver_join35 testCliDriver_lineage1 testCliDriver_load_dyn_part14 testCliDriver_union10 testCliDriver_union12 testCliDriver_union18 testCliDriver_union30 testCliDriver_union4 testCliDriver_union6 I spot checked a few of them (union4, union6) and they are due to differences in plan output - the new output seems to have more operators including the conditional operator - I will look more into it - any guidance to help me would be greatly appreciated. Improve Hive's logic for conditional merge -- Key: HIVE-3733 URL: https://issues.apache.org/jira/browse/HIVE-3733 Project: Hive Issue Type: Improvement Reporter: Pradeep Kamath Assignee: Pradeep Kamath Attachments: HIVE-3733.1.patch.txt If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles is set to false then when hive encounters a FileSinkOperator when generating map reduce tasks, it will look at the entire job to see if it has a reducer, if it does it will not merge. Instead it should be check if the FileSinkOperator is a child of the reducer. This means that outputs generated in the mapper will be merged, and outputs generated in the reducer will not be, the intended effect of setting those configs. Simple repro: set hive.merge.mapfiles=true; set hive.merge.mapredfiles=false; EXPLAIN FROM input_table INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key INSERT OVERWRITE TABLE output_table2 SELECT *; The output should contain a Conditional Operator, Mapred Stages, and Move tasks -- 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-3733) Improve Hive's logic for conditional merge
[
https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503960#comment-13503960
]
Pradeep Kamath commented on HIVE-3733:
--
I noticed the following in HiveConf.java:
{code}
HIVEMERGEMAPFILES(hive.merge.mapfiles, true)
{code}
I suspect that with my new changes and the above setting, we are now merging
files for map only tasks where we previously were not - I am very new to the
hive code base - would request some committer to take a look to see if in fact
the new behavior is the expected one given that the default for merge map files
is true.
Improve Hive's logic for conditional merge
--
Key: HIVE-3733
URL: https://issues.apache.org/jira/browse/HIVE-3733
Project: Hive
Issue Type: Improvement
Reporter: Pradeep Kamath
Assignee: Pradeep Kamath
Attachments: HIVE-3733.1.patch.txt
If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles
is set to false then when hive encounters a FileSinkOperator when generating
map reduce tasks, it will look at the entire job to see if it has a reducer,
if it does it will not merge. Instead it should be check if the
FileSinkOperator is a child of the reducer. This means that outputs generated
in the mapper will be merged, and outputs generated in the reducer will not
be, the intended effect of setting those configs.
Simple repro:
set hive.merge.mapfiles=true;
set hive.merge.mapredfiles=false;
EXPLAIN
FROM input_table
INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key
INSERT OVERWRITE TABLE output_table2 SELECT *;
The output should contain a Conditional Operator, Mapred Stages, and Move
tasks
--
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] [Created] (HIVE-3733) Improve Hive's logic for conditional merge
Pradeep Kamath created HIVE-3733: Summary: Improve Hive's logic for conditional merge Key: HIVE-3733 URL: https://issues.apache.org/jira/browse/HIVE-3733 Project: Hive Issue Type: Improvement Reporter: Pradeep Kamath If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles is set to false then when hive encounters a FileSinkOperator when generating map reduce tasks, it will look at the entire job to see if it has a reducer, if it does it will not merge. Instead it should be check if the FileSinkOperator is a child of the reducer. This means that outputs generated in the mapper will be merged, and outputs generated in the reducer will not be, the intended effect of setting those configs. Simple repro: set hive.merge.mapfiles=true; set hive.merge.mapredfiles=false; EXPLAIN FROM input_table INSERT OVERWRITE TABLE output_table1 SELECT key, COUNT(*) group by key INSERT OVERWRITE TABLE output_table2 SELECT *; The output should contain a Conditional Operator, Mapred Stages, and Move tasks -- 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-842) Authentication Infrastructure for Hive
[ https://issues.apache.org/jira/browse/HIVE-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932210#action_12932210 ] Pradeep Kamath commented on HIVE-842: - I have tested this patch after making HIVE-1526 work and with the changes suggested in my earlier comment -https://issues.apache.org/jira/browse/HIVE-842?focusedCommentId=12924020page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12924020. It works well in the testing I have done. Once HIVE-1526 is regenerated, this patch can be regenerated accordingly and hopefully can be committed soon to enable working with Hadoop security Authentication Infrastructure for Hive -- Key: HIVE-842 URL: https://issues.apache.org/jira/browse/HIVE-842 Project: Hive Issue Type: New Feature Components: Security, Server Infrastructure Reporter: Edward Capriolo Assignee: Todd Lipcon Attachments: hive-842.txt, HiveSecurityThoughts.pdf This issue deals with the authentication (user name,password) infrastructure. Not the authorization components that specify what a user should be able to do. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-78) Authorization infrastructure for Hive
[ https://issues.apache.org/jira/browse/HIVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930820#action_12930820 ] Pradeep Kamath commented on HIVE-78: Will there be a way to turn off authorization (through some configuration property) OR is there a way to allow all access OR is authorization implementation going to be pluggable? Since howl is looking at a different authorization model based on dfs permissions, one of these options would be needed for howl. Authorization infrastructure for Hive - Key: HIVE-78 URL: https://issues.apache.org/jira/browse/HIVE-78 Project: Hive Issue Type: New Feature Components: Metastore, Query Processor, Server Infrastructure Reporter: Ashish Thusoo Assignee: He Yongqiang Attachments: createuser-v1.patch, hive-78-metadata-v1.patch, hive-78-syntax-v1.patch, HIVE-78.1.nothrift.patch, HIVE-78.1.thrift.patch, hive-78.diff Allow hive to integrate with existing user repositories for authentication and authorization infromation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1526) Hive should depend on a release version of Thrift
[ https://issues.apache.org/jira/browse/HIVE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12929632#action_12929632 ] Pradeep Kamath commented on HIVE-1526: -- Hi Carl - just wondering if you have had a chance to look at this.. Hive should depend on a release version of Thrift - Key: HIVE-1526 URL: https://issues.apache.org/jira/browse/HIVE-1526 Project: Hive Issue Type: Task Components: Build Infrastructure, Clients Reporter: Carl Steinbach Assignee: Todd Lipcon Fix For: 0.7.0 Attachments: HIVE-1526.2.patch.txt, hive-1526.txt, libfb303.jar, libthrift.jar Hive should depend on a release version of Thrift, and ideally it should use Ivy to resolve this dependency. The Thrift folks are working on adding Thrift artifacts to a maven repository here: https://issues.apache.org/jira/browse/THRIFT-363 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1526) Hive should depend on a release version of Thrift
[ https://issues.apache.org/jira/browse/HIVE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12927549#action_12927549 ] Pradeep Kamath commented on HIVE-1526: -- Hi Carl - just wondering if you have had a chance to look at this - a new patch for this issue will help me create a patch for HIVE-1696 (I suspect we will need to redo HIVE-842 as well - I can take a stab at that once this patch is ready). Hive should depend on a release version of Thrift - Key: HIVE-1526 URL: https://issues.apache.org/jira/browse/HIVE-1526 Project: Hive Issue Type: Task Components: Build Infrastructure, Clients Reporter: Carl Steinbach Assignee: Todd Lipcon Fix For: 0.7.0 Attachments: HIVE-1526.2.patch.txt, hive-1526.txt, libfb303.jar, libthrift.jar Hive should depend on a release version of Thrift, and ideally it should use Ivy to resolve this dependency. The Thrift folks are working on adding Thrift artifacts to a maven repository here: https://issues.apache.org/jira/browse/THRIFT-363 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1264) Make Hive work with Hadoop security
[ https://issues.apache.org/jira/browse/HIVE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919929#action_12919929 ] Pradeep Kamath commented on HIVE-1264: -- The new patch does address the failed test - TestHBaseMinimrCliDriver. I have used this patch against a certain version of hadoop security and have had success running queries. It would be good if this patch can be committed soon since HIVE-1526 and HIVE-842 also depend on this. Aside from that, it would be a great feature to be able to work with hadoop security. Any chance this can be committed soon? Thanks! Make Hive work with Hadoop security --- Key: HIVE-1264 URL: https://issues.apache.org/jira/browse/HIVE-1264 Project: Hadoop Hive Issue Type: Improvement Affects Versions: 0.7.0 Reporter: Jeff Hammerbacher Assignee: Todd Lipcon Attachments: hive-1264-fb-mirror.txt, hive-1264.txt, hive-1264.txt, HiveHadoop20S_patch.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
