Return-Path: X-Original-To: apmail-flume-user-archive@www.apache.org Delivered-To: apmail-flume-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5073210A70 for ; Thu, 13 Mar 2014 22:32:33 +0000 (UTC) Received: (qmail 50140 invoked by uid 500); 13 Mar 2014 22:32:32 -0000 Delivered-To: apmail-flume-user-archive@flume.apache.org Received: (qmail 50072 invoked by uid 500); 13 Mar 2014 22:32:32 -0000 Mailing-List: contact user-help@flume.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flume.apache.org Delivered-To: mailing list user@flume.apache.org Received: (qmail 50064 invoked by uid 99); 13 Mar 2014 22:32:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Mar 2014 22:32:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kanirip@gmail.com designates 209.85.216.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Mar 2014 22:32:27 +0000 Received: by mail-qc0-f182.google.com with SMTP id e16so1982098qcx.41 for ; Thu, 13 Mar 2014 15:32:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GjIKN7Dmpz/8Aw/QK02TZbfCZQ97/mTczMx5kPc58ZA=; b=lrcsl1Rifp1W0pNqZsgCkCYhL+IAVQYKJVAomWkw/okLulHFwqxLZhtqk7E8YQnc+K 1NpOUhKYtubuOkHN5nRRXwnLHdzbw1HDdyRqf95gd/oqgzZmk891xTn9t2Y43cQKTSPm RPW8wVnTCs0WpBfWT9wX+2AV30n5touRHrqW0OHSLKCAomdMEMQiuQDkmnEJ78TSYX6m 1gkgDiP94tpzyXpx7czVX8EerC09bzgB2W45HQyI+sjDivNxviV43Jddn4R9fmrIlnV6 bsbm+vFUsDKSgdFfp/qE68BLZ+PtXaQuP3WeFlSqGkv+Z4BdoA8PZHnKwHPKVo+a10bk HkKw== MIME-Version: 1.0 X-Received: by 10.229.28.2 with SMTP id k2mr3359013qcc.16.1394749927276; Thu, 13 Mar 2014 15:32:07 -0700 (PDT) Received: by 10.140.90.80 with HTTP; Thu, 13 Mar 2014 15:32:07 -0700 (PDT) In-Reply-To: References: Date: Thu, 13 Mar 2014 23:32:07 +0100 Message-ID: Subject: Re: JMS Source on 1.3.0? From: Kris Ogirri To: user@flume.apache.org Content-Type: multipart/alternative; boundary=001a1133bbd0f74ae304f4848568 X-Virus-Checked: Checked by ClamAV on apache.org --001a1133bbd0f74ae304f4848568 Content-Type: text/plain; charset=ISO-8859-1 I am not certain how performing the update to Flume violate any Service contract one could have with IBM but I am certain that Flume 1.3 has a significant amount of issues with Hbase connectivity. You might have to discuss the legal implications with your IBM Sales Rep or Business Partner.( Disclaimer: I work for IBM) On 13 March 2014 23:19, Christopher Shannon wrote: > Kris, > > How does running Flume 1.4 affect your service contract with IBM? > On Mar 13, 2014 5:02 PM, "Kris Ogirri" 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 wrote: >> >>> IBM Big Insights. >>> On Mar 13, 2014 4:47 PM, "Brock Noland" 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 < >>>> cshannon108@gmail.com> 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? >>>>> >>>> >>>> >> --001a1133bbd0f74ae304f4848568 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I am not certain how performing the update to Flume violat= e any Service contract one could have with IBM but I am certain that Flume = 1.3 has a significant amount of issues with Hbase connectivity. You might h= ave to discuss the legal implications with your IBM Sales Rep or Business P= artner.( Disclaimer: I work for IBM)


On 13 M= arch 2014 23:19, Christopher Shannon <cshannon108@gmail.com> wrote:

Kris,

How does running Flume 1.4 affect your service contract with= IBM?

On Mar 13, 2014 5:02 PM, "Kris Ogirri"= <kanirip@gmail.c= om> wrote:
Hello Christoper,
I believe the latest versions of BigInsights=A0 does come with Flume 1.3 = but I have been able to successfully upgrade Flume within BigInsights to th= e 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 s= ite.
2) Perform a backup of the 'bin' , 'lib', = 9;docs','conf' directory in $BIGINSIGHTS_HOME/flume/ ( I basica= lly 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&= #39; , 'lib', 'docs','conf' and 'tools' dir= ectory from your Flume 1.4 directory into your $BIGINSIGHTS_HOME/flume/=A0 = ( or /opt/ibm/biginsights/flume)
5) Test flume functionality by executing the following command in the= 'bin' directory ' ./flume-ng version'

If ever= ything 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 <cshannon108@gmail.com> wrote:

IBM Big Insights.

On Mar 13, 2014 4:47 PM, "Brock Noland"= ; <brock@clouder= a.com> 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 <= cshannon108@gmai= l.com> wrote:

I know that the JMS source is new in version 1.4, but has an= yone tried running this particular component on Flume 1.3.x? I can"t u= pgrade to 1.4 because of vendor lock-in. And I am condidering rolling my ow= n JMS source for 1.3 if the source for 1.4 won't work.

Any thoughts or recommendations?




--001a1133bbd0f74ae304f4848568--