You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Roshan Naik (JIRA)" <ji...@apache.org> on 2013/05/10 00:29:15 UTC

[jira] [Comment Edited] (FLUME-1976) JMS Source document should provide instruction on JMS implementation jars

    [ https://issues.apache.org/jira/browse/FLUME-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653289#comment-13653289 ] 

Roshan Naik edited comment on FLUME-1976 at 5/9/13 10:27 PM:
-------------------------------------------------------------

> I think "to flume event converter." should be "flume event converter." I believe that was my mistake

It seems ok to me. The phrase ", message to flume event converter"  seems more correct than ", message flume event converter" ... isnt it ?

WRT plugin.d dir : i dont see any references to this directory anywhere else in the docs nor in the startup script 
                
      was (Author: roshan_naik):
    > I think "to flume event converter." should be "flume event converter." I believe that was my mistake

It seems ok to me. The phrase ", message to flume event converter"  seems more correct than ", message flume event converter" ... isnt it ?

WRT plugin.d dir : i dont see any references to this directory anywhere else nor in the startup script 
                  
> JMS Source document should provide instruction on JMS implementation jars
> -------------------------------------------------------------------------
>
>                 Key: FLUME-1976
>                 URL: https://issues.apache.org/jira/browse/FLUME-1976
>             Project: Flume
>          Issue Type: Improvement
>            Reporter: Brock Noland
>            Assignee: Roshan Naik
>            Priority: Minor
>         Attachments: FLUME-1976.patch
>
>
> The JMS Source should instruct/remind users that they will have to place their vendor supplied JMS jars in the flume classpath to utilize the JMS source.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira