Mailing-List: contact chukwa-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of billgraham@gmail.com designates
 74.125.83.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:date:message-id:subject:from:to:content-type;
        b=HVzyxpQa5HrSxQqSEFR1SYPeNNaPFgSywcOPuubWm5KWTIlhOpi1uiWItKtyJ0hBjB
         QB6kPtC4dGzIauMlih2L1QpdtC0GZtwgfnuLK2M85dOOI8FVKiooHEtlpGk75WpfQz+l
         RbImnU/3ytO2WW8Kqsp6GcNsAt0MBS0L6xI9s=
MIME-Version: 1.0
Reply-To: billgraham@gmail.com
Date: Wed, 21 Apr 2010 15:31:41 -0700
Message-ID: <i2o449b48761004211531i5a698cb2y510442f75a0748b6@mail.gmail.com>
Subject: HttpTriggerAction - configuring N objects
From: Bill Graham <billgraham@gmail.com>
To: chukwa-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=00504502cc731923ad0484c6c27a

--00504502cc731923ad0484c6c27a
Content-Type: text/plain; charset=ISO-8859-1

Hi,

As a follow up to CHUKWA-477, I'm writing a class called HttpTriggerAction
that can hit one or more URLs upon successful completion of a demux job. I'd
like to contribute it back unless anyone objects. Anyway, I'm looking for
feedback though on how to configure this object.

The issue is that since the class can hit N urls, it needs N sets of
key-value configurations. The hadoop configurations model is just name-value
pairs though, so I'm kicking around ideas around the best way to handle
this.

Specifically, I need to configure values for url, an optional HTTP method
(default is GET), an optional collection of HTTP headers and an optional
post body. I was thinking of just making a convention where key values could
be incremented like below, but wanted to see if there were better
suggestions out there.

chukwa.trigger.action.[eventName].http.1.url=http://site.com/firstTrigger
chukwa.trigger.action.[eventName].http.1.headers=User-Agent:chukwa

chukwa.trigger.action.[eventName].http.2.url=http://site.com/secondTrigger
chukwa.trigger.action.[eventName].http.2.method=POST
chukwa.trigger.action.[eventName].http.2.headers=User-Agent:chukwa,Accepts:text/plain
chukwa.trigger.action.[eventName].http.2.body=Some post body to submit
....
chukwa.trigger.action.[eventName].http.N.url=
chukwa.trigger.action.[eventName].http.N.method=
chukwa.trigger.action.[eventName].http.N.headers=
chukwa.trigger.action.[eventName].http.N.body=

Since the action could potentially be used by other types of events, the
event name should be included. This implies that we should add an eventName
field to the TriggerAction.execute method in CHUKWA-477.

Thoughts?

thanks,
Bill

--00504502cc731923ad0484c6c27a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>As a follow up to CHUKWA-477, I&#39;m writing a class called Htt=
pTriggerAction that can hit one or more URLs upon successful completion of =
a demux job. I&#39;d like to contribute it back unless anyone objects. Anyw=
ay, I&#39;m looking for feedback though on how to configure this object.<br=
>
<br>The issue is that since the class can hit N urls, it needs N sets of ke=
y-value configurations. The hadoop configurations model is just name-value =
pairs though, so I&#39;m kicking around ideas around the best way to handle=
 this.<br>
<br>Specifically, I need to configure values for url, an optional HTTP meth=
od (default is GET), an optional collection of HTTP headers and an optional=
 post body. I was thinking of just making a convention where key values cou=
ld be incremented like below, but wanted to see if there were better sugges=
tions out there. <br>
<br>chukwa.trigger.action.[eventName].http.1.url=3D<a href=3D"http://site.c=
om/firstTrigger">http://site.com/firstTrigger</a><br>
chukwa.trigger.action.[eventName].http.1.headers=3DUser-Agent:chukwa<br><br=
>
chukwa.trigger.action.[eventName].http.2.url=3D<a href=3D"http://site.com/s=
econdTrigger">http://site.com/secondTrigger</a><br>chukwa.trigger.action.[e=
ventName].http.2.method=3DPOST<br>chukwa.trigger.action.[eventName].http.2.=
headers=3DUser-Agent:chukwa,Accepts:text/plain<br>


chukwa.trigger.action.[eventName].http.2.body=3DSome post body to submit<br=
>....<br>chukwa.trigger.action.[eventName].http.N.url=3D<br>
chukwa.trigger.action.[eventName].http.N.method=3D<br>
chukwa.trigger.action.[eventName].http.N.headers=3D<br>


chukwa.trigger.action.[eventName].http.N.body=3D<br>
<br>Since the action could potentially be used by other types of events, th=
e event name should be included. This implies that we should add an eventNa=
me field to the TriggerAction.execute method in CHUKWA-477.<br><br>Thoughts=
?<br>
<br>thanks,<br>Bill<br>

<br>
<br>

--00504502cc731923ad0484c6c27a--