Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Tue, 21 Jan 2014 19:35:19 +0000 (UTC)
From: "Nezih Yigitbasi (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12690095.1390332841524.41446.1390332919938@arcas>
In-Reply-To: <JIRA.12690095.1390332841524@arcas>
References: <JIRA.12690095.1390332841524@arcas>
Subject: [jira] [Created] (PIG-3680) A new type of EvalFunc,
 TransactionalEvalFunc, would be useful
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Nezih Yigitbasi created PIG-3680:
------------------------------------

             Summary: A new type of EvalFunc, TransactionalEvalFunc, would be useful
                 Key: PIG-3680
                 URL: https://issues.apache.org/jira/browse/PIG-3680
             Project: Pig
          Issue Type: New Feature
            Reporter: Nezih Yigitbasi
            Assignee: Nezih Yigitbasi
            Priority: Minor


I think a new type of EvalFunc that has some notion of a transactional context would be very useful. This new TransactionalEvalFunc abstract class should have methods like initialize, onSuccess, and onFailure to mark the transaction boundaries. Such EvalFuncs would be useful for interacting with external resources. For example, to delete rows from an existing hbase table such a transactional UDF would be useful. Of course we can imitate this with a StoreFunc, but conceptually StoreFunc's are restricted to writes. If the community thinks this will be useful, I am ready to spend time on this..


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)