Re: The difference between PostHTTP and GetHTTP wrt headers

[Otto Fowler]

Along with user defined….


On March 15, 2018 at 22:40:33, Otto Fowler (ottobackwa...@gmail.com) wrote:

So looking at it, the standard way would be dynamic properties.  Thank you
Andy.


On March 15, 2018 at 22:30:33, Otto Fowler (ottobackwa...@gmail.com) wrote:

I’m actually looking at doing a web service processor , that would support
setting custom headers, and I want it to be “standard”.
I’ll look at the InvokeHTTP.


On March 15, 2018 at 15:57:33, Andy LoPresto (alopre...@apache.org) wrote:

Both of these are legacy processors introduced early on in NiFi’s
development and intended for moving data between NiFi instances. I would
recommend you use InvokeHTTP, which is a more modern and full-featured
processor and can perform both GET and POST requests.


Andy LoPresto
alopre...@apache.org
*alopresto.apa...@gmail.com *
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Mar 15, 2018, at 12:47 PM, Otto Fowler  wrote:

Can someone explain or confirm why GetHTTP uses Dynamic Properties for
setting custom headers in http requests but PostHTTP uses a Property with a
Regex to pull flow file attributes?

Is it due to the forbidden input?

Thanks

ottO

Re: The difference between PostHTTP and GetHTTP wrt headers

[Otto Fowler]

So looking at it, the standard way would be dynamic properties.  Thank you
Andy.


On March 15, 2018 at 22:30:33, Otto Fowler (ottobackwa...@gmail.com) wrote:

I’m actually looking at doing a web service processor , that would support
setting custom headers, and I want it to be “standard”.
I’ll look at the InvokeHTTP.


On March 15, 2018 at 15:57:33, Andy LoPresto (alopre...@apache.org) wrote:

Both of these are legacy processors introduced early on in NiFi’s
development and intended for moving data between NiFi instances. I would
recommend you use InvokeHTTP, which is a more modern and full-featured
processor and can perform both GET and POST requests.


Andy LoPresto
alopre...@apache.org
*alopresto.apa...@gmail.com *
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Mar 15, 2018, at 12:47 PM, Otto Fowler  wrote:

Can someone explain or confirm why GetHTTP uses Dynamic Properties for
setting custom headers in http requests but PostHTTP uses a Property with a
Regex to pull flow file attributes?

Is it due to the forbidden input?

Thanks

ottO

Re: The difference between PostHTTP and GetHTTP wrt headers

[Otto Fowler]

I’m actually looking at doing a web service processor , that would support
setting custom headers, and I want it to be “standard”.
I’ll look at the InvokeHTTP.


On March 15, 2018 at 15:57:33, Andy LoPresto (alopre...@apache.org) wrote:

Both of these are legacy processors introduced early on in NiFi’s
development and intended for moving data between NiFi instances. I would
recommend you use InvokeHTTP, which is a more modern and full-featured
processor and can perform both GET and POST requests.


Andy LoPresto
alopre...@apache.org
*alopresto.apa...@gmail.com *
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Mar 15, 2018, at 12:47 PM, Otto Fowler  wrote:

Can someone explain or confirm why GetHTTP uses Dynamic Properties for
setting custom headers in http requests but PostHTTP uses a Property with a
Regex to pull flow file attributes?

Is it due to the forbidden input?

Thanks

ottO

Re: trouble installing minifi

[Aldrin Piri]

Hi Maribeth,

I am assuming you are building from the source tarball that was published
for 0.4.0.  During the release process, we noticed some additional,
generated sources had made it into the tarball but did not want to waste
the time that already went into the release verification process.

Could you please try removing Scanner.cpp, Parser.hpp, Parser.cpp, *.hh
from the extensions/expression-language folder and rebuilding?

Please let us know if that clears things up or if there are lingering
issues.

Sorry for the hurdle!

--aldrin

On Thu, Mar 15, 2018 at 6:09 PM, Marc  wrote:

> Hi,
>   What is your os? Did you use the cmake instructions or bootstrap?
>
> On Mar 15, 2018 6:06 PM, "mjrudd...@gmail.com" 
> wrote:
>
> > I've been following the instructions for installing minifi, and
> everything
> > worked up until i ran the 'make' command from the build folder. Partway
> > through the make process, I get the following errors (see below). Has
> > anyone seen this before, and what can I do to fix it?
> >
> > Thanks in advance for your help..
> >
> > /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> > extensions/expression-language/Scanner.cpp: In member function ‘int
> > org::apache::nifi::minifi::expression::Driver::lex(org::
> > apache::nifi::minifi::expression::Parser::semantic_type*,
> > org::apache::nifi::minifi::expression::Parser::location_type*)’:
> > /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> > extensions/expression-language/Scanner.cpp:582:9: error: no match for
> > ‘operator=’ (operand types are ‘std::istream {aka
> > std::basic_istream}’ and ‘std::istream* {aka
> > std::basic_istream*}’)
> > In file included from /usr/include/c++/5/iostream:40:0,
> >  from /Users/apiri/Development/code/
> > apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> > /usr/include/c++/5/istream:625:7: note: candidate:
> > std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
> > _Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT
> =
> > char; _Traits = std::char_traits]
> >operator=(basic_istream&& __rhs)
> >^
> > /usr/include/c++/5/istream:625:7: note:   no known conversion for
> > argument 1 from ‘std::istream* {aka std::basic_istream*}’ to
> > ‘std::basic_istream&&’
> > /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> > extensions/expression-language/Scanner.cpp:585:10: error: no match for
> > ‘operator=’ (operand types are ‘std::ostream {aka
> > std::basic_ostream}’ and ‘std::ostream* {aka
> > std::basic_ostream*}’)
> > In file included from /usr/include/c++/5/iostream:39:0,
> >  from /Users/apiri/Development/code/
> > apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> > /usr/include/c++/5/ostream:402:7: note: candidate:
> > std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT,
> > _Traits>::operator=(std::basic_ostream<_CharT, _Traits>&&) [with _CharT
> =
> > char; _Traits = std::char_traits]
> >operator=(basic_ostream&& __rhs)
> >^
> > /usr/include/c++/5/ostream:402:7: note:   no known conversion for
> > argument 1 from ‘std::ostream* {aka std::basic_ostream*}’ to
> > ‘std::basic_ostream&&’
> > /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> > extensions/expression-language/Scanner.cpp:802:44: error: cannot convert
> > ‘std::istream {aka std::basic_istream}’ to ‘std::istream* {aka
> > std::basic_istream*}’ in assignment
> > In file included from /usr/include/c++/5/iostream:40:0,
> >  from /Users/apiri/Development/code/
> > apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> > /usr/include/c++/5/istream: In constructor ‘yyFlexLexer::yyFlexLexer(std:
> :istream*,
> > std::ostream*)’:
> > /usr/include/c++/5/istream:606:7: error: ‘std::basic_istream<_CharT,
> > _Traits>::basic_istream() [with _CharT = char; _Traits =
> > std::char_traits]’ is protected
> >basic_istream()
> >^
> > /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> > extensions/expression-language/Scanner.cpp:913:75: error: within this
> > context
> > In file included from /usr/include/c++/5/iostream:39:0,
> >  from /Users/apiri/Development/code/
> > apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> > /usr/include/c++/5/ostream:384:7: error: ‘std::basic_ostream<_CharT,
> > _Traits>::basic_ostream() [with _CharT = char; _Traits =
> > std::char_traits]’ is protected
> >basic_ostream()
> >^
> > /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> > extensions/expression-language/Scanner.cpp:913:75: error: within this
> > context
> > /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> > extensions/expression-language/Scanner.cpp:915:7: error: no match for
> > ‘operator=’ (operand types are ‘std::istream {aka
> > std::basic_istream}’ and ‘std::istream* {aka
> > std::basic_istream*}’)
> > In file included from 

Re: trouble installing minifi

[Marc]

Hi,
  I was reminded that on the download page there is a comment
regarding the source release tarball:

  "Note: If you experience any issues with building, please try
removing Scanner.cpp, Parser.hpp, Parser.cpp, *.hh from the
extensions/expression-language folder and rebuild"

  This only applies to the current source tarball:
nifi-minifi-cpp-0.4.0-source.tar.gz

  Sorry for the inconvenience and let us know if you have additional problems.




On Thu, Mar 15, 2018 at 6:09 PM, Marc  wrote:
> Hi,
>   What is your os? Did you use the cmake instructions or bootstrap?
>
> On Mar 15, 2018 6:06 PM, "mjrudd...@gmail.com"  wrote:
>>
>> I've been following the instructions for installing minifi, and everything
>> worked up until i ran the 'make' command from the build folder. Partway
>> through the make process, I get the following errors (see below). Has anyone
>> seen this before, and what can I do to fix it?
>>
>> Thanks in advance for your help..
>>
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:
>> In member function ‘int
>> org::apache::nifi::minifi::expression::Driver::lex(org::apache::nifi::minifi::expression::Parser::semantic_type*,
>> org::apache::nifi::minifi::expression::Parser::location_type*)’:
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:582:9:
>> error: no match for ‘operator=’ (operand types are ‘std::istream {aka
>> std::basic_istream}’ and ‘std::istream* {aka
>> std::basic_istream*}’)
>> In file included from /usr/include/c++/5/iostream:40:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/istream:625:7: note: candidate:
>> std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
>> _Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT =
>> char; _Traits = std::char_traits]
>>operator=(basic_istream&& __rhs)
>>^
>> /usr/include/c++/5/istream:625:7: note:   no known conversion for argument
>> 1 from ‘std::istream* {aka std::basic_istream*}’ to
>> ‘std::basic_istream&&’
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:585:10:
>> error: no match for ‘operator=’ (operand types are ‘std::ostream {aka
>> std::basic_ostream}’ and ‘std::ostream* {aka
>> std::basic_ostream*}’)
>> In file included from /usr/include/c++/5/iostream:39:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/ostream:402:7: note: candidate:
>> std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT,
>> _Traits>::operator=(std::basic_ostream<_CharT, _Traits>&&) [with _CharT =
>> char; _Traits = std::char_traits]
>>operator=(basic_ostream&& __rhs)
>>^
>> /usr/include/c++/5/ostream:402:7: note:   no known conversion for argument
>> 1 from ‘std::ostream* {aka std::basic_ostream*}’ to
>> ‘std::basic_ostream&&’
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:802:44:
>> error: cannot convert ‘std::istream {aka std::basic_istream}’ to
>> ‘std::istream* {aka std::basic_istream*}’ in assignment
>> In file included from /usr/include/c++/5/iostream:40:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/istream: In constructor
>> ‘yyFlexLexer::yyFlexLexer(std::istream*, std::ostream*)’:
>> /usr/include/c++/5/istream:606:7: error: ‘std::basic_istream<_CharT,
>> _Traits>::basic_istream() [with _CharT = char; _Traits =
>> std::char_traits]’ is protected
>>basic_istream()
>>^
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:913:75:
>> error: within this context
>> In file included from /usr/include/c++/5/iostream:39:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/ostream:384:7: error: ‘std::basic_ostream<_CharT,
>> _Traits>::basic_ostream() [with _CharT = char; _Traits =
>> std::char_traits]’ is protected
>>basic_ostream()
>>^
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:913:75:
>> error: within this context
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:915:7:
>> error: no match for ‘operator=’ (operand types are ‘std::istream {aka
>> std::basic_istream}’ and ‘std::istream* {aka
>> std::basic_istream*}’)
>> In file included from /usr/include/c++/5/iostream:40:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/istream:625:7: note: 

Re: trouble installing minifi

[Marc]

Hi,
  What is your os? Did you use the cmake instructions or bootstrap?

On Mar 15, 2018 6:06 PM, "mjrudd...@gmail.com"  wrote:

> I've been following the instructions for installing minifi, and everything
> worked up until i ran the 'make' command from the build folder. Partway
> through the make process, I get the following errors (see below). Has
> anyone seen this before, and what can I do to fix it?
>
> Thanks in advance for your help..
>
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp: In member function ‘int
> org::apache::nifi::minifi::expression::Driver::lex(org::
> apache::nifi::minifi::expression::Parser::semantic_type*,
> org::apache::nifi::minifi::expression::Parser::location_type*)’:
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:582:9: error: no match for
> ‘operator=’ (operand types are ‘std::istream {aka
> std::basic_istream}’ and ‘std::istream* {aka
> std::basic_istream*}’)
> In file included from /usr/include/c++/5/iostream:40:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/istream:625:7: note: candidate:
> std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
> _Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT =
> char; _Traits = std::char_traits]
>operator=(basic_istream&& __rhs)
>^
> /usr/include/c++/5/istream:625:7: note:   no known conversion for
> argument 1 from ‘std::istream* {aka std::basic_istream*}’ to
> ‘std::basic_istream&&’
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:585:10: error: no match for
> ‘operator=’ (operand types are ‘std::ostream {aka
> std::basic_ostream}’ and ‘std::ostream* {aka
> std::basic_ostream*}’)
> In file included from /usr/include/c++/5/iostream:39:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/ostream:402:7: note: candidate:
> std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT,
> _Traits>::operator=(std::basic_ostream<_CharT, _Traits>&&) [with _CharT =
> char; _Traits = std::char_traits]
>operator=(basic_ostream&& __rhs)
>^
> /usr/include/c++/5/ostream:402:7: note:   no known conversion for
> argument 1 from ‘std::ostream* {aka std::basic_ostream*}’ to
> ‘std::basic_ostream&&’
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:802:44: error: cannot convert
> ‘std::istream {aka std::basic_istream}’ to ‘std::istream* {aka
> std::basic_istream*}’ in assignment
> In file included from /usr/include/c++/5/iostream:40:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/istream: In constructor 
> ‘yyFlexLexer::yyFlexLexer(std::istream*,
> std::ostream*)’:
> /usr/include/c++/5/istream:606:7: error: ‘std::basic_istream<_CharT,
> _Traits>::basic_istream() [with _CharT = char; _Traits =
> std::char_traits]’ is protected
>basic_istream()
>^
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:913:75: error: within this
> context
> In file included from /usr/include/c++/5/iostream:39:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/ostream:384:7: error: ‘std::basic_ostream<_CharT,
> _Traits>::basic_ostream() [with _CharT = char; _Traits =
> std::char_traits]’ is protected
>basic_ostream()
>^
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:913:75: error: within this
> context
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:915:7: error: no match for
> ‘operator=’ (operand types are ‘std::istream {aka
> std::basic_istream}’ and ‘std::istream* {aka
> std::basic_istream*}’)
> In file included from /usr/include/c++/5/iostream:40:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/istream:625:7: note: candidate:
> std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
> _Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT =
> char; _Traits = std::char_traits]
>operator=(basic_istream&& __rhs)
>^
> /usr/include/c++/5/istream:625:7: note:   no known conversion for
> argument 1 from ‘std::istream* {aka std::basic_istream*}’ to
> ‘std::basic_istream&&’
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:916:8: error: no match for
> ‘operator=’ (operand types are ‘std::ostream {aka
> 

trouble installing minifi

[mjruddell]

I've been following the instructions for installing minifi, and everything 
worked up until i ran the 'make' command from the build folder. Partway through 
the make process, I get the following errors (see below). Has anyone seen this 
before, and what can I do to fix it?

Thanks in advance for your help..

/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:
 In member function ‘int 
org::apache::nifi::minifi::expression::Driver::lex(org::apache::nifi::minifi::expression::Parser::semantic_type*,
 org::apache::nifi::minifi::expression::Parser::location_type*)’:
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:582:9:
 error: no match for ‘operator=’ (operand types are ‘std::istream {aka 
std::basic_istream}’ and ‘std::istream* {aka 
std::basic_istream*}’)
In file included from /usr/include/c++/5/iostream:40:0,
 from 
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
/usr/include/c++/5/istream:625:7: note: candidate: std::basic_istream<_CharT, 
_Traits>& std::basic_istream<_CharT, 
_Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT = char; 
_Traits = std::char_traits]
   operator=(basic_istream&& __rhs)
   ^
/usr/include/c++/5/istream:625:7: note:   no known conversion for argument 1 
from ‘std::istream* {aka std::basic_istream*}’ to 
‘std::basic_istream&&’
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:585:10:
 error: no match for ‘operator=’ (operand types are ‘std::ostream {aka 
std::basic_ostream}’ and ‘std::ostream* {aka 
std::basic_ostream*}’)
In file included from /usr/include/c++/5/iostream:39:0,
 from 
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
/usr/include/c++/5/ostream:402:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>& std::basic_ostream<_CharT, 
_Traits>::operator=(std::basic_ostream<_CharT, _Traits>&&) [with _CharT = char; 
_Traits = std::char_traits]
   operator=(basic_ostream&& __rhs)
   ^
/usr/include/c++/5/ostream:402:7: note:   no known conversion for argument 1 
from ‘std::ostream* {aka std::basic_ostream*}’ to 
‘std::basic_ostream&&’
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:802:44:
 error: cannot convert ‘std::istream {aka std::basic_istream}’ to 
‘std::istream* {aka std::basic_istream*}’ in assignment
In file included from /usr/include/c++/5/iostream:40:0,
 from 
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
/usr/include/c++/5/istream: In constructor 
‘yyFlexLexer::yyFlexLexer(std::istream*, std::ostream*)’:
/usr/include/c++/5/istream:606:7: error: ‘std::basic_istream<_CharT, 
_Traits>::basic_istream() [with _CharT = char; _Traits = 
std::char_traits]’ is protected
   basic_istream()
   ^
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:913:75:
 error: within this context
In file included from /usr/include/c++/5/iostream:39:0,
 from 
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
/usr/include/c++/5/ostream:384:7: error: ‘std::basic_ostream<_CharT, 
_Traits>::basic_ostream() [with _CharT = char; _Traits = 
std::char_traits]’ is protected
   basic_ostream()
   ^
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:913:75:
 error: within this context
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:915:7:
 error: no match for ‘operator=’ (operand types are ‘std::istream {aka 
std::basic_istream}’ and ‘std::istream* {aka 
std::basic_istream*}’)
In file included from /usr/include/c++/5/iostream:40:0,
 from 
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
/usr/include/c++/5/istream:625:7: note: candidate: std::basic_istream<_CharT, 
_Traits>& std::basic_istream<_CharT, 
_Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT = char; 
_Traits = std::char_traits]
   operator=(basic_istream&& __rhs)
   ^
/usr/include/c++/5/istream:625:7: note:   no known conversion for argument 1 
from ‘std::istream* {aka std::basic_istream*}’ to 
‘std::basic_istream&&’
/Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:916:8:
 error: no match for ‘operator=’ (operand types are ‘std::ostream {aka 
std::basic_ostream}’ and ‘std::ostream* {aka 
std::basic_ostream*}’)
In file included from /usr/include/c++/5/iostream:39:0,
 from 

Re: GetKinesis processor

[Andy LoPresto]

I am not aware of ongoing efforts for this processor [1]. The release candidate 
for 1.6.0 will be started early next week, so if you’re looking for it to make 
that release, it might be a busy weekend.

[1] https://issues.apache.org/jira/browse/NIFI-2892 


Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Mar 15, 2018, at 12:58 PM, Martini, Adam  wrote:
> 
> Hello all,
> 
> Is anyone actively working on a GetKinesis Processor? This is something that 
> we could really use, but do not want to duplicate effort.
> 
> If not, is there a timeline for this work and/or is there any chance of 
> getting this in the 1.6.0 release?
> 
> Thanks!
> 
> Adam Martini
> Senior Dev, Nike Digital



signature.asc
Description: Message signed with OpenPGP using GPGMail

GetKinesis processor

[Martini, Adam]

Hello all,

Is anyone actively working on a GetKinesis Processor? This is something that we 
could really use, but do not want to duplicate effort.

If not, is there a timeline for this work and/or is there any chance of getting 
this in the 1.6.0 release?

Thanks!

Adam Martini
Senior Dev, Nike Digital

Re: The difference between PostHTTP and GetHTTP wrt headers

[Andy LoPresto]

Both of these are legacy processors introduced early on in NiFi’s development 
and intended for moving data between NiFi instances. I would recommend you use 
InvokeHTTP, which is a more modern and full-featured processor and can perform 
both GET and POST requests.


Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Mar 15, 2018, at 12:47 PM, Otto Fowler  wrote:
> 
> Can someone explain or confirm why GetHTTP uses Dynamic Properties for
> setting custom headers in http requests but PostHTTP uses a Property with a
> Regex to pull flow file attributes?
> 
> Is it due to the forbidden input?
> 
> Thanks
> 
> ottO



signature.asc
Description: Message signed with OpenPGP using GPGMail

The difference between PostHTTP and GetHTTP wrt headers

[Otto Fowler]

Can someone explain or confirm why GetHTTP uses Dynamic Properties for
setting custom headers in http requests but PostHTTP uses a Property with a
Regex to pull flow file attributes?

Is it due to the forbidden input?

Thanks

ottO