Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <22559673.3961273693603587.JavaMail.jira@thor>
Date: Wed, 12 May 2010 15:46:43 -0400 (EDT)
From: "Namit Jain (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Updated: (HIVE-801) row-wise IN would be useful
In-Reply-To: <1756716722.1251320159316.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Namit Jain updated HIVE-801:
----------------------------

           Status: Resolved  (was: Patch Available)
     Hadoop Flags: [Reviewed]
    Fix Version/s: 0.6.0
       Resolution: Fixed

Committed. Thanks Paul

> row-wise IN would be useful
> ---------------------------
>
>                 Key: HIVE-801
>                 URL: https://issues.apache.org/jira/browse/HIVE-801
>             Project: Hadoop Hive
>          Issue Type: New Feature
>            Reporter: Adam Kramer
>            Assignee: Paul Yang
>             Fix For: 0.6.0
>
>         Attachments: HIVE-801.1.patch, HIVE-801.2.patch, HIVE-801.3.patch
>
>
> SELECT * FROM tablename t
> WHERE IN(12345,key1,key2,key3);
> ...IN would operate on a given row, and return True when the first argument equaled at least one of the other arguments. So here IN would return true if 12345=key1 OR 12345=key2 OR 12345=key3 (but wouldn't test the latter two if the first matched).
> This would also help with https://issues.apache.org/jira/browse/HIVE-783, if IN were implemented in a manner that allows it to be used in an ON clause.

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