James,

reviewed, squashed the commits, and merged the PR.  Thanks.  What I
failed to however was to close the PR.  Can you please go ahead and
close it?

Thanks
Joe

On Thu, Dec 31, 2015 at 10:40 AM, Joe Witt <[email protected]> wrote:
> James,
>
> Looks like you did great.  Will take a look and provide feedback or merge 
> soon.
>
> Thanks again
> Joe
>
> On Thu, Dec 31, 2015 at 10:09 AM, James Harrison <[email protected]> wrote:
>> Hopefully I got the process correct -  here's the links to the ticket and
>> pull request:
>>
>> https://issues.apache.org/jira/browse/NIFI-1338
>>
>> https://github.com/apache/nifi/pull/153
>>
>> Thanks,
>> James
>>
>> On Thu, Dec 31, 2015 at 2:11 PM, Joe Witt <[email protected]> wrote:
>>
>>> James
>>>
>>> Would def take a contrib  on improving the docs for invokehttp.  If you
>>> would like to submit a PR or just put text here let us know.
>>>
>>> Thanks
>>> Joe
>>> On Dec 31, 2015 9:09 AM, "James Harrison" <[email protected]> wrote:
>>>
>>> > Looks like InvokeHTTP can do this - the docs imply that it only deals
>>> with
>>> > attributes/headers and doesn't explicitly indicate it can transfer the
>>> > contents of the flowfile.
>>> >
>>> > Thanks!
>>> >
>>> > On Thu, Dec 31, 2015 at 1:57 PM, Joe Gresock <[email protected]> wrote:
>>> >
>>> > > I think InvokeHTTP will do the trick.
>>> > >
>>> > > On Thu, Dec 31, 2015 at 8:55 AM, James Harrison <[email protected]>
>>> > > wrote:
>>> > >
>>> > > > Hi,
>>> > > >
>>> > > > We need to send data to an HTTP Endpoint which requires PUT
>>> operations
>>> > > > rather than POST operations. We currently use a forked version of
>>> > > PostHTTP
>>> > > > which allows selection of the HTTP operation. I'd like to contribute
>>> > the
>>> > > > functionality to Nifi which leads to a couple of questions:
>>> > > >
>>> > > > 1. Have I overlooked a really obvious processor which can already do
>>> > > this?
>>> > > >
>>> > > > 2. Is anyone else looking at this? - I can't find any tickets which
>>> > > relate.
>>> > > >
>>> > > > 3. Should this be supported by:
>>> > > >     a.  a separate "PutHTTP" processor? (probably abstracting most of
>>> > > > PostHTTP to a common superclass)
>>> > > >     b. An additional property for "PostHTTP"? (which leads to
>>> slightly
>>> > > > confusing naming)
>>> > > >     c. A completely different way?
>>> > > >
>>> > > > Thanks,
>>> > > > James
>>> > > >
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > I know what it is to be in need, and I know what it is to have
>>> plenty.  I
>>> > > have learned the secret of being content in any and every situation,
>>> > > whether well fed or hungry, whether living in plenty or in want.  I can
>>> > do
>>> > > all this through him who gives me strength.    *-Philippians 4:12-13*
>>> > >
>>> >
>>>

Reply via email to