[
https://issues.apache.org/jira/browse/FLUME-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Shreedharan updated FLUME-975:
-----------------------------------
Description: Move classes generated by Avro to a separate module(and thus a
separate jar): AvroFlumeEvent, AvroSourceProtocol and Status out of
flume-ng-core(and maybe create a Flume client exception class), so that clients
which use these are not dependent and do not require flume-ng-core itself.
This will ensure that the AvroCLIClient, and the Log4jAppender, and any new
clients are not dependent on Flume NG itself. (was: Logging appender for log4j
framework, which uses AvroSource under the hood.)
Priority: Major (was: Minor)
> Move AvroFlumeEvent and related classes, generated by Avro out of
> Flume-ng-core to a new sub module, which is not dependant on flume-ng itself
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLUME-975
> URL: https://issues.apache.org/jira/browse/FLUME-975
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.0.0
> Reporter: Hari Shreedharan
> Fix For: v1.1.0
>
>
> Move classes generated by Avro to a separate module(and thus a separate jar):
> AvroFlumeEvent, AvroSourceProtocol and Status out of flume-ng-core(and maybe
> create a Flume client exception class), so that clients which use these are
> not dependent and do not require flume-ng-core itself. This will ensure that
> the AvroCLIClient, and the Log4jAppender, and any new clients are not
> dependent on Flume NG itself.
--
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
