Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hive >> mail # user >> What is this windowing query supposed to do?


Copy link to this message
-
Re: What is this windowing query supposed to do?
> The problem is if you follow our site from the main page you find the
broken docs, not the confluence ones.

Let's take this to a separate thread, since it isn't about the windowing
query.

-- Lefty
On Mon, Sep 2, 2013 at 11:44 AM, Edward Capriolo <[EMAIL PROTECTED]>wrote:

> The problem is if you follow our site from the main page you find the
> broken docs, not the confluence ones.
>
>
> On Mon, Sep 2, 2013 at 4:21 AM, Lefty Leverenz <[EMAIL PROTECTED]>wrote:
>
>> Once again the /confluence/display version of the wiki is fine while the
>> non-display version is glitchy.  First the {code} tags gave invisible
>> sample code, and now some of the doc links don't work -- but they're fine
>> here:  https://cwiki.apache.org/confluence/display/Hive/LanguageManual.
>>
>> Can anyone explain this, or better yet solve it?  Until it's solved,
>> should we include a link to the display version at the top of each wikidoc?
>>  (And I suppose that's the royal "we" unless someone else volunteers.)
>>
>> For the windowing doc<https://cwiki.apache.org/confluence/display/Hive/LanguageManual+WindowingAndAnalytics>,
>> I've added a link to Harish's PDF file in the first paragraph:
>>
>>    - See "Windowing Specifications in HQL<https://issues.apache.org/jira/secure/attachment/12575830/WindowingSpecification.pdf>"
>>    (attached to HIVE-4197<https://issues.apache.org/jira/browse/HIVE-4197>)
>>    for details.
>>
>> Happy Labor Day, everyone.  -- Lefty
>>
>>
>>
>> On Sun, Sep 1, 2013 at 8:36 PM, Harish Butani <[EMAIL PROTECTED]>wrote:
>>
>>> In your 3rd query the OVER clause is being ignored because there is no
>>> associated Aggregation Function.
>>> This has been fixed in HIVE-4214. The query fails with the following
>>> error:
>>> 'cannot recognize input near 'range' 'OVER' '(' in select expression'
>>>
>>> The Windowing behavior in Hive is documented in HIVE-4197
>>>
>>> https://issues.apache.org/jira/secure/attachment/12575830/WindowingSpecification.pdf
>>>
>>> On Sep 1, 2013, at 2:04 PM, Edward Capriolo <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>> hive> select * from field_goal;
>>> OK
>>> tynes    44    miss
>>> tynes    40    miss
>>> tynes    33    make
>>> pete    20    make
>>> pete    21    make
>>> arnold    56    make
>>> arnold    22    make
>>> arnold    45    miss
>>> Time taken: 0.04 seconds, Fetched: 8 row(s)
>>>
>>> This makes sense:
>>> hive> select name,avg(range) OVER (PARTITION by name ORDER by range)
>>> FROM field_goal  ;
>>> arnold    22.0
>>> arnold    33.5
>>> arnold    41.0
>>> pete    20.0
>>> pete    20.5
>>> tynes    33.0
>>> tynes    36.5
>>> tynes    39.0
>>> Time taken: 4.14 seconds, Fetched: 8 row(s)
>>>
>>> but what is this?
>>> hive> select name,range OVER (PARTITION by name ORDER by range) FROM
>>> field_goal  ;
>>> tynes    44
>>> tynes    40
>>> tynes    33
>>> pete    20
>>> pete    21
>>> arnold    56
>>> arnold    22
>>> arnold    45
>>> Time taken: 3.709 seconds, Fetched: 8 row(s)
>>>
>>> It would be great if the
>>> https://cwiki.apache.org/Hive/languagemanual-windowingandanalytics.html#LanguageManualWindowingAndAnalytics-PARTITIONBYwithpartitioning%252CORDERBY%252Candwindowspecification
>>>
>>>
>>> Most of the links here:
>>> https://cwiki.apache.org/Hive/languagemanual.html
>>>
>>> are broken...
>>> What gives?
>>> The language manual used to be fairly useful, now it is in major
>>> dis-array.
>>>
>>>
>>>
>>>
>>>
>>>
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity
>>> to which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender immediately
>>> and delete it from your system. Thank You.