Hudson build is back to normal : Hive-trunk-h0.17 #565

2010-10-11 Thread Apache Hudson Server 
See

[jira] Commented: (HIVE-307) "LOAD DATA LOCAL INPATH" fails when the table already contains a file of the same name

2010-10-11 Thread Namit Jain (JIRA) 

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

Namit Jain commented on HIVE-307:
-

@Kirk, please go ahead and make the change.

Yongqiang was just trying to get an svn compatible patch from your patch

> "LOAD DATA LOCAL INPATH" fails when the table already contains a file of the 
> same name
> --
>
> Key: HIVE-307
> URL: https://issues.apache.org/jira/browse/HIVE-307
> Project: Hadoop Hive
>  Issue Type: Bug
>  Components: Query Processor
>Affects Versions: 0.5.0
>Reporter: Zheng Shao
>Assignee: Kirk True
>Priority: Critical
> Attachments: hive-307.1.svn.patch, HIVE-307.patch, HIVE-307.patch
>
>
> Failed with exception checkPaths: 
> /user/zshao/warehouse/tmp_user_msg_history/test_user_msg_history already 
> exists
> FAILED: Execution Error, return code 1 from 
> org.apache.hadoop.hive.ql.exec.MoveTask

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Build failed in Hudson: Hive-trunk-h0.19 #566

2010-10-11 Thread Apache Hudson Server 
See 

--
[...truncated 12225 lines...]
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src
[junit] POSTHOOK: Output: defa...@src
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src1
[junit] POSTHOOK: Output: defa...@src1
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_sequencefile
[junit] POSTHOOK: Output: defa...@src_sequencefile
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_thrift
[junit] POSTHOOK: Output: defa...@src_thrift
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_json
[junit] POSTHOOK: Output: defa...@src_json
[junit] OK
[junit] diff 

 

[junit] Done query: unknown_table1.q
[junit] Begin query: unknown_table2.q
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-08, hr=11)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-08/hr=11
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-08, hr=12)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-08/hr=12
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-09, hr=11)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-09/hr=11
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-09, hr=12)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-09/hr=12
[junit] OK
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src
[junit] POSTHOOK: Output: defa...@src
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src1
[junit] POSTHOOK: Output: defa...@src1
[junit] OK
[junit] Copying data from 

[

Build failed in Hudson: Hive-trunk-h0.18 #566

2010-10-11 Thread Apache Hudson Server 
See 

--
[...truncated 30973 lines...]
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src
[junit] POSTHOOK: Output: defa...@src
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src1
[junit] POSTHOOK: Output: defa...@src1
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_sequencefile
[junit] POSTHOOK: Output: defa...@src_sequencefile
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_thrift
[junit] POSTHOOK: Output: defa...@src_thrift
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_json
[junit] POSTHOOK: Output: defa...@src_json
[junit] OK
[junit] diff 

 

[junit] Done query: unknown_table1.q
[junit] Begin query: unknown_table2.q
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-08, hr=11)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-08/hr=11
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-08, hr=12)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-08/hr=12
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-09, hr=11)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-09/hr=11
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-09, hr=12)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-09/hr=12
[junit] OK
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src
[junit] POSTHOOK: Output: defa...@src
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src1
[junit] POSTHOOK: Output: defa...@src1
[junit] OK
[junit] Copying data from 

[

[jira] Commented: (HIVE-1264) Make Hive work with Hadoop security

2010-10-11 Thread Pradeep Kamath (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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.

Build failed in Hudson: Hive-trunk-h0.20 #389

2010-10-11 Thread Apache Hudson Server 
See 

--
[...truncated 14197 lines...]
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src
[junit] POSTHOOK: Output: defa...@src
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src1
[junit] POSTHOOK: Output: defa...@src1
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_sequencefile
[junit] POSTHOOK: Output: defa...@src_sequencefile
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_thrift
[junit] POSTHOOK: Output: defa...@src_thrift
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src_json
[junit] POSTHOOK: Output: defa...@src_json
[junit] OK
[junit] diff 

 

[junit] Done query: unknown_table1.q
[junit] Begin query: unknown_table2.q
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-08, hr=11)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-08/hr=11
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-08, hr=12)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-08/hr=12
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-09, hr=11)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-09/hr=11
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcpart partition (ds=2008-04-09, hr=12)
[junit] POSTHOOK: Output: defa...@srcpart@ds=2008-04-09/hr=12
[junit] OK
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket
[junit] POSTHOOK: Output: defa...@srcbucket
[junit] OK
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table srcbucket2
[junit] POSTHOOK: Output: defa...@srcbucket2
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src
[junit] POSTHOOK: Output: defa...@src
[junit] OK
[junit] Copying data from 

[junit] Loading data to table src1
[junit] POSTHOOK: Output: defa...@src1
[junit] OK
[junit] Copying data from 

[

[jira] Commented: (HIVE-1264) Make Hive work with Hadoop security

2010-10-11 Thread John Sichi (JIRA) 

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

John Sichi commented on HIVE-1264:
--

I'm back from vacation; I'll retry tests with the latest patch.

> 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.

[jira] Commented: (HIVE-1501) when generating reentrant INSERT for index rebuild, quote identifiers using backticks

2010-10-11 Thread John Sichi (JIRA) 

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

John Sichi commented on HIVE-1501:
--

Yes, a simple test such as the one above should be good enough.

> when generating reentrant INSERT for index rebuild, quote identifiers using 
> backticks
> -
>
> Key: HIVE-1501
> URL: https://issues.apache.org/jira/browse/HIVE-1501
> Project: Hadoop Hive
>  Issue Type: Bug
>  Components: Indexing
>Affects Versions: 0.7.0
>Reporter: John Sichi
>Assignee: Skye Berghel
> Fix For: 0.7.0
>
> Attachments: 1501.patch
>
>
> Yongqiang, you mentioned that you weren't able to do this due to SORT BY not 
> accepting them.  The SORT BY is gone now as of HIVE-1494 (and SORT BY needs 
> to be fixed anyway).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (HIVE-1694) Accelerate query execution using indexes

2010-10-11 Thread John Sichi (JIRA) 

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

John Sichi commented on HIVE-1694:
--

Note that we have a team of students from Harvey Mudd planning to work on this 
one.

> Accelerate query execution using indexes
> 
>
> Key: HIVE-1694
> URL: https://issues.apache.org/jira/browse/HIVE-1694
> Project: Hadoop Hive
>  Issue Type: New Feature
>  Components: Indexing, Query Processor
>Affects Versions: 0.7.0
>Reporter: Nikhil Deshpande
>
> The index building patch (Hive-417) is checked into trunk, this JIRA issue 
> tracks supporting indexes in Hive compiler & execution engine for SELECT 
> queries.
> This is in ref. to John's comment at
> https://issues.apache.org/jira/browse/HIVE-417?focusedCommentId=12884869&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12884869
> on creating separate JIRA issue for tracking index usage in optimizer & query 
> execution.
> The aim of this effort is to use indexes to accelerate query execution (for 
> certain class of queries). E.g.
> - Filters and range scans (already being worked on by He Yongqiang as part of 
> HIVE-417?)
> - Joins (index based joins)
> - Group By, Order By and other misc cases
> The proposal is multi-step:
> 1. Building index based operators, compiler and execution engine changes
> 2. Optimizer enhancements (e.g. cost-based optimizer to compare and choose 
> between index scans, full table scans etc.)
> This JIRA initially focuses on the first step. This JIRA is expected to hold 
> the information about index based plans & operator implementations for above 
> mentioned cases. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (HIVE-1498) support IDXPROPERTIES on CREATE/ALTER INDEX

2010-10-11 Thread John Sichi (JIRA) 

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

John Sichi commented on HIVE-1498:
--

Looks good.  Once the ALTER INDEX support is added, this one should be good to 
go.


> support IDXPROPERTIES on CREATE/ALTER INDEX
> ---
>
> Key: HIVE-1498
> URL: https://issues.apache.org/jira/browse/HIVE-1498
> Project: Hadoop Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.7.0
>Reporter: John Sichi
>Assignee: Marquis Wang
> Fix For: 0.7.0
>
> Attachments: hive-1498.prelim.patch, hive-1498.prelim.patch
>
>
> It's partially there in the grammar but not hooked in; should work pretty 
> much the same as TBLPROPERTIES.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

HIVE-1669

2010-10-11 Thread John Sichi 
The build has been broken because of this for days...

https://hudson.apache.org/hudson/job/Hive-trunk-h0.20/

If it's going to take more time to resolve HIVE-1658, could we get a patch for 
HIVE-1669 committed so that we can eliminate spurious failures when testing 
other patches?

JVS

[jira] Resolved: (HIVE-1264) Make Hive work with Hadoop security

2010-10-11 Thread John Sichi (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Sichi resolved HIVE-1264.
--

   Resolution: Fixed
Fix Version/s: 0.7.0
 Hadoop Flags: [Reviewed]

Committed.  Thanks Todd!


> 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
> Fix For: 0.7.0
>
> 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.

Re: [howldev] RE: Howl Authorization proposal

2010-10-11 Thread John Sichi 
Hi Pradeep,

Namit and I took a look at the doc; thanks for the clear writeup.

Coincidentally, we've been starting to think about some Hive authorization use 
cases within Facebook as well.  However, the approach we're thinking about is 
more along the lines of traditional SQL ACL's (role-based GRANT/REVOKE with 
persistence in the metastore) rather than HDFS-based.  HIVE-78 touches on this 
(plus a lot of unrelated stuff).

So, one question is whether you would still need HDFS-based approach if a 
metastore-level ACL solution were available?

And if the answer to that is no, then would you prefer to skip the HDFS-based 
work and just join forces on the ACL solution?

If it turns out that you're going to need the HDFS-based approach, then I can 
see how both can coexist (either as alternatives, or as one overlayed on top of 
the other).  The HDFS-based approach can be useful for controlling how HDFS 
permissions are managed in the case where users are allowed direct access to 
HDFS, or when multiple clients are used for access (which is one of the main 
reasons for Howl to exist).

Regarding development of the HDFS-based approach, it would make sense to start 
off with enforcement via hooks.  I think now that we have the semantic analyzer 
hooks, it should be possible to do it either all there or via a combination of 
that and execution hooks.

The code for the hook implementations can start out in Howl, and then if 
there's consensus on adopting it within Hive, we can move it at that time.

JVS

On Oct 5, 2010, at 1:19 PM, Pradeep Kamath wrote:



Also, if this proposal looks reasonable, it would be nice if hive would also 
adopt it – so comments from hive developers/committers on the feasibility would 
be much appreciated!

Thanks,
Pradeep


From: Pradeep Kamath
Sent: Tuesday, October 05, 2010 1:14 PM
To: 
'howl...@yahoogroups.com'
Subject: Howl Authorization proposal

Hi,
   I have posted a proposal for implementing authorization in howl based on 
hdfs file permission at 
http://wiki.apache.org/pig/Howl/HowlAuthorizationProposal. Please provide any 
comments/feedback on the proposal.

Thanks,
Pradeep


__._,_.___


Your email settings: Individual Email|Traditional
Change settings via the 
Web
 (Yahoo! ID required)
Change settings via email: Switch delivery to Daily 
Digest
 | Switch to Fully 
Featured
Visit Your Group 

 | Yahoo! Groups Terms of Use  | Unsubscribe 


__,_._,___

[jira] Updated: (HIVE-846) move hive tables from one database to another

2010-10-11 Thread He Yongqiang (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

He Yongqiang updated HIVE-846:
--

Assignee: (was: He Yongqiang)

> move hive tables from one database to another
> -
>
> Key: HIVE-846
> URL: https://issues.apache.org/jira/browse/HIVE-846
> Project: Hadoop Hive
>  Issue Type: New Feature
>Reporter: Namit Jain
>
> The support for moving tables from one database to another is not present

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (HIVE-848) support mutilpe databse support in HWI

2010-10-11 Thread He Yongqiang (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

He Yongqiang updated HIVE-848:
--

Assignee: (was: He Yongqiang)

> support mutilpe databse support in HWI
> --
>
> Key: HIVE-848
> URL: https://issues.apache.org/jira/browse/HIVE-848
> Project: Hadoop Hive
>  Issue Type: New Feature
>Reporter: Namit Jain
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: HIVE-1669

2010-10-11 Thread Ning Zhang 
I will take a look at HIVE-1669.

On Oct 11, 2010, at 4:00 PM, John Sichi wrote:

> The build has been broken because of this for days...
> 
> https://hudson.apache.org/hudson/job/Hive-trunk-h0.20/
> 
> If it's going to take more time to resolve HIVE-1658, could we get a patch 
> for HIVE-1669 committed so that we can eliminate spurious failures when 
> testing other patches?
> 
> JVS
>

[jira] Assigned: (HIVE-1669) non-deterministic display of storage parameter in test

2010-10-11 Thread Ning Zhang (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ning Zhang reassigned HIVE-1669:


Assignee: Thiruvel Thirumoolan

> non-deterministic display of storage parameter in test
> --
>
> Key: HIVE-1669
> URL: https://issues.apache.org/jira/browse/HIVE-1669
> Project: Hadoop Hive
>  Issue Type: Sub-task
>Reporter: Ning Zhang
>Assignee: Thiruvel Thirumoolan
> Attachments: HIVE-1669.patch
>
>
> With the change to beautify the 'desc extended table', the storage parameters 
> are displayed in non-deterministic manner (since its implementation is 
> HashMap). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (HIVE-1669) non-deterministic display of storage parameter in test

2010-10-11 Thread Ning Zhang (JIRA) 

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

Ning Zhang commented on HIVE-1669:
--

Thiruvel, changes look good in general. Some minor comments:
 1) can you expand 'import java.util.*' with the class names used in the file, 
just to make the coding style consistent.
 2) can you run the full test with overwrite option: 'ant test -Doverwrite 
...'. There should be a lot of .out file changes and upload the full patch? You 
may need to run both -Dhadoop.version=0.20.0 and -Dhadoop.version=0.17.2.1


> non-deterministic display of storage parameter in test
> --
>
> Key: HIVE-1669
> URL: https://issues.apache.org/jira/browse/HIVE-1669
> Project: Hadoop Hive
>  Issue Type: Sub-task
>Reporter: Ning Zhang
>Assignee: Thiruvel Thirumoolan
> Attachments: HIVE-1669.patch
>
>
> With the change to beautify the 'desc extended table', the storage parameters 
> are displayed in non-deterministic manner (since its implementation is 
> HashMap). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (HIVE-1699) incorrect partition pruning ANALYZE TABLE

2010-10-11 Thread Ning Zhang (JIRA) 
incorrect partition pruning ANALYZE TABLE
-

 Key: HIVE-1699
 URL: https://issues.apache.org/jira/browse/HIVE-1699
 Project: Hadoop Hive
  Issue Type: Bug
Reporter: Ning Zhang
Assignee: Ning Zhang


If table T is partitioned, ANALYZE TABLE T PARTITION (...) COMPUTE STATISTICS; 
will gather stats for all partitions even though partition spec only chooses a 
subset. 



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.