Kris, How does running Flume 1.4 affect your service contract with IBM? On Mar 13, 2014 5:02 PM, "Kris Ogirri" <[email protected]> wrote:
> Hello Christoper, > > I believe the latest versions of BigInsights does come with Flume 1.3 but > I have been able to successfully upgrade Flume within BigInsights to the > most recent version I know of ( 1.4). The steps are straight-forward. > > 1) Download the flume v1.4 binary tarball from the Apache Flume site. > 2) Perform a backup of the 'bin' , 'lib', 'docs','conf' directory in > $BIGINSIGHTS_HOME/flume/ ( I basically renamed these directories appending > a 13 to their names) > 3) Explode the Apache Flume Tarball into any other directory in your > environment ( $HOME/flume140 probably) > 4) Copy over the 'bin' , 'lib', 'docs','conf' and 'tools' directory from > your Flume 1.4 directory into your $BIGINSIGHTS_HOME/flume/ ( or > /opt/ibm/biginsights/flume) > 5) Test flume functionality by executing the following command in the > 'bin' directory ' ./flume-ng version' > > If everything goes right you should see that flume is updated to version > 1.4. > > Try it out and let us know how it goes, > > > > On 13 March 2014 22:48, Christopher Shannon <[email protected]> wrote: > >> IBM Big Insights. >> On Mar 13, 2014 4:47 PM, "Brock Noland" <[email protected]> wrote: >> >>> I think it should work to run the 1.4 JMS source in 1.3. >>> >>> Out of curiosity, which vendor isn't shipping 1.4? >>> >>> Brock >>> >>> >>> On Thu, Mar 13, 2014 at 4:43 PM, Christopher Shannon < >>> [email protected]> wrote: >>> >>>> I know that the JMS source is new in version 1.4, but has anyone tried >>>> running this particular component on Flume 1.3.x? I can"t upgrade to 1.4 >>>> because of vendor lock-in. And I am condidering rolling my own JMS source >>>> for 1.3 if the source for 1.4 won't work. >>>> >>>> Any thoughts or recommendations? >>>> >>> >>> >
