Hello Srikanth,

Nope you should not have to mess with the classpath for that to work.
Created a JIRA for it [1].

Can you provide a bit about your config on GetSolr?

Regarding the extension and class loader model the developer guide
does a pretty good job of describing it [2].  You can get to those
docs from from the site [3] or a running instance of NiFi.

Thanks
Joe

[1] https://issues.apache.org/jira/browse/NIFI-910
[2] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#nars
[3] https://nifi.apache.org/docs.html

On Sun, Aug 30, 2015 at 7:50 PM, Srikanth <[email protected]> wrote:
> Hello,
>
> I'm trying out my first dataflow using NiFi. The flow involves GetSolr ->
> LogAttributes. I ran into NoClassDefFoundError while trying this.
>
> Here is an extract from nifi-app.log
>
> 18:36:26 EDTERROR7a7692b6-a9dd-4a95-a68a-932d54774144
>> GetSolr[id=7a7692b6-a9dd-4a95-a68a-932d54774144]
>> GetSolr[id=7a7692b6-a9dd-4a95-a68a-932d54774144] failed to process due to
>> java.lang.NoClassDefFoundError: org/apache/http/message/TokenParser;
>> rolling back session: java.lang.NoClassDefFoundError:
>> org/apache/http/message/TokenParser
>> 2015-08-30 18:34:55,908 WARN [Timer-Driven Process Thread-7]
>> o.a.n.c.t.ContinuallyRunProcessorTask
>> java.lang.NoClassDefFoundError: org/apache/http/message/TokenParser
>>         at
>> org.apache.http.client.utils.URLEncodedUtils.parse(URLEncodedUtils.java:280)
>> ~[httpclient-4.4.1.jar:4.4.1]
>>         at
>> org.apache.http.client.utils.URLEncodedUtils.parse(URLEncodedUtils.java:237)
>> ~[httpclient-4.4.1.jar:4.4.1]
>
>
> Should I be manually adding certain jars to class path?
>
> A more general question, how are jars built, distributed and loaded in
> NiFi.
> Asking this mainly because of the extendable design of this project.
>
> I have to say it was super easy to get started with NiFi. Doc was well
> organized.
> I had my first visit to NiFi page y'day morning and I'm writing my first
> dataflow today evening...hit my first exception too!!
>
> Regards,
> Srikanth

Reply via email to