You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Will McQueen (Created) (JIRA)" <ji...@apache.org> on 2012/03/02 12:22:57 UTC

[jira] [Created] (FLUME-1014) Agent Config docs are out of date

Agent Config docs are out of date
---------------------------------

                 Key: FLUME-1014
                 URL: https://issues.apache.org/jira/browse/FLUME-1014
             Project: Flume
          Issue Type: Bug
          Components: Docs
    Affects Versions: v1.1.0
         Environment: RHEL 6.2 64-bit
            Reporter: Will McQueen
             Fix For: v1.1.0


The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host'->'agent' change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (FLUME-1014) Agent Config docs are out of date

Posted by "Will McQueen (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will McQueen updated FLUME-1014:
--------------------------------

    Description: The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host'\->'agent' change.  (was: The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host' to 'agent' change.)
    
> Agent Config docs are out of date
> ---------------------------------
>
>                 Key: FLUME-1014
>                 URL: https://issues.apache.org/jira/browse/FLUME-1014
>             Project: Flume
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: v1.1.0
>         Environment: RHEL 6.2 64-bit
>            Reporter: Will McQueen
>             Fix For: v1.1.0
>
>
> The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host'\->'agent' change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (FLUME-1014) Agent Config docs are out of date

Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arvind Prabhakar updated FLUME-1014:
------------------------------------

    Status: Open  (was: Patch Available)

Canceling patch since it needs to be rebased and refactored.

Discussion on https://reviews.apache.org/r/4154/
                
> Agent Config docs are out of date
> ---------------------------------
>
>                 Key: FLUME-1014
>                 URL: https://issues.apache.org/jira/browse/FLUME-1014
>             Project: Flume
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: v1.1.0
>         Environment: RHEL 6.2 64-bit
>            Reporter: Will McQueen
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1014.patch
>
>
> The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host' to 'agent' change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (FLUME-1014) Agent Config docs are out of date

Posted by "Will McQueen (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will McQueen updated FLUME-1014:
--------------------------------

    Attachment: FLUME-1014.patch
    
> Agent Config docs are out of date
> ---------------------------------
>
>                 Key: FLUME-1014
>                 URL: https://issues.apache.org/jira/browse/FLUME-1014
>             Project: Flume
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: v1.1.0
>         Environment: RHEL 6.2 64-bit
>            Reporter: Will McQueen
>             Fix For: v1.1.0
>
>         Attachments: FLUME-1014.patch
>
>
> The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host' to 'agent' change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (FLUME-1014) Agent Config docs are out of date

Posted by "Will McQueen (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will McQueen updated FLUME-1014:
--------------------------------

    Status: Patch Available  (was: Open)

https://reviews.apache.org/r/4154/
                
> Agent Config docs are out of date
> ---------------------------------
>
>                 Key: FLUME-1014
>                 URL: https://issues.apache.org/jira/browse/FLUME-1014
>             Project: Flume
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: v1.1.0
>         Environment: RHEL 6.2 64-bit
>            Reporter: Will McQueen
>             Fix For: v1.1.0
>
>         Attachments: FLUME-1014.patch
>
>
> The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host' to 'agent' change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (FLUME-1014) Agent Config docs are out of date

Posted by "Will McQueen (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will McQueen updated FLUME-1014:
--------------------------------

    Description: The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host' to 'agent' change.  (was: The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host'->'agent' change.)
    
> Agent Config docs are out of date
> ---------------------------------
>
>                 Key: FLUME-1014
>                 URL: https://issues.apache.org/jira/browse/FLUME-1014
>             Project: Flume
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: v1.1.0
>         Environment: RHEL 6.2 64-bit
>            Reporter: Will McQueen
>             Fix For: v1.1.0
>
>
> The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host' to 'agent' change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (FLUME-1014) Agent Config docs are out of date

Posted by "Will McQueen (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will McQueen updated FLUME-1014:
--------------------------------

    Description: The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host' to 'agent' change.  (was: The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host'\->'agent' change.)
    
> Agent Config docs are out of date
> ---------------------------------
>
>                 Key: FLUME-1014
>                 URL: https://issues.apache.org/jira/browse/FLUME-1014
>             Project: Flume
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: v1.1.0
>         Environment: RHEL 6.2 64-bit
>            Reporter: Will McQueen
>             Fix For: v1.1.0
>
>
> The javadocs and sample config files are out of date with respect to valid agent configurations. The docs and sample file also mention "host" instead of "agent", which can get confused with the hostname of a machine. The agent name specified in the config file should by convention be named "agent" to make it clearer. An agent name specified in the config file (props file) is what needs to get passed to the '\-n' option when running the flume-ng script. The affected code should also be updated to reflect this 'host' to 'agent' change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira