Mailing-List: contact user-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hive.apache.org
Received-SPF: error (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAD-Ua_gyzrXqFDb1VnkNqM1pDH0LmwTWopO9R_X+nPPW_p2v+g@mail.gmail.com>
References: 
 <CAD-Ua_jx52mnrJrG8FoV6J2G4XhRH0ZPjCMmizRkj4i6Q8ngSQ@mail.gmail.com>
	<CAD-Ua_gyzrXqFDb1VnkNqM1pDH0LmwTWopO9R_X+nPPW_p2v+g@mail.gmail.com>
Date: Thu, 25 Jul 2013 17:01:32 +0900
Message-ID: 
 <CACQ46vFEfrKSy5JUrH8orYw_V0TAUiGXFt3FPJAKDn250LbKaA@mail.gmail.com>
Subject: Re: Problem with the windowing function ntile (Exceptions)
From: =?EUC-KR?B?TmF2aXO3+b3Cv+w=?= <navis.ryu@nexr.com>
To: user@hive.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I've booked this and attached patch for it.

https://issues.apache.org/jira/browse/HIVE-4932

Could you test with that? thanks.

2013/7/25 Lars Francke <lars.francke@gmail.com>:
> We're still being bitten by this problem without a workaround. Does
> anyone have an idea?
>
> Thanks,
> Lars
>
> On Wed, Jul 17, 2013 at 11:24 PM, Lars Francke <lars.francke@gmail.com> wrote:
>> Hi,
>>
>> I'm running a query like this:
>>
>> CREATE TABLE foo
>>   STORED AS ORC
>> AS
>> SELECT
>>   id,
>>   season,
>>   amount,
>>   ntile(10)
>> OVER (
>>   PARTITION BY season
>>   ORDER BY amount DESC
>> )
>> FROM bar;
>>
>> On a small enough dataset that works fine but when switching to a
>> larger sample we're seeing exceptions like this:
>>
>> "Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: Reset on
>> PersistentByteBasedList not supported"
>>
>> Looking at the code (without really understanding it) we tried setting:
>> SET hive.ptf.partition.persistence='org.apache.hadoop.hive.ql.exec.PTFPersistence$PartitionedByteBasedList';
>>
>> because that List supports reset but we are seeing a
>> ClassNotFoundException so we're doing that wrong.
>>
>> Next try was setting hive.ptf.partition.persistence.memsize higher
>> which worked but first of all we don't really understand what all of
>> that stuff is doing and second of all we fear that it just might break
>> down again.
>>
>> Any hints as to what that error really means and how to deal with it
>> would be greatly appreciated.
>>
>> Thanks!
>>
>> Lars