[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferenc Szabo updated FLUME-2706: Fix Version/s: (was: 1.8.0) 1.9.0 > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Fix For: 1.9.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Labels: (was: docs-missing) > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Fix For: v1.7.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: flume-2706.patch A new patch with the documentation updated > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Labels: docs-missing > Fix For: v1.7.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: (was: flume-2706.patch) > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Labels: docs-missing > Fix For: v1.7.0 > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bessenyei Balázs Donát updated FLUME-2706: -- Labels: docs-missing (was: docs-missing reviewboard-missing) > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Labels: docs-missing > Fix For: v1.7.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: flume-2706.patch > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Labels: docs-missing, reviewboard-missing > Fix For: v1.7.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: (was: flume-2076.patch) > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Labels: docs-missing, reviewboard-missing > Fix For: v1.7.0 > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: (was: flume-2706.patch) > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Labels: docs-missing, reviewboard-missing > Fix For: v1.7.0 > > Attachments: flume-2076.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: flume-2076.patch This is a new patch as a diff with the latest status of the trunk > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Labels: docs-missing, reviewboard-missing > Fix For: v1.7.0 > > Attachments: flume-2076.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bessenyei Balázs Donát updated FLUME-2706: -- Labels: docs-missing reviewboard-missing (was: ) > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Labels: docs-missing, reviewboard-missing > Fix For: v1.7.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: (was: flume-2706.patch) > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Fix For: v1.7.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: flume-2706.patch Corrected the patch. > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Fix For: v1.7.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: flume-2706.patch > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Fix For: v1.7.0 > > Attachments: flume-2706.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: (was: FLUME-2706-0.patch) > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Fix For: v1.7.0 > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2706) Camel source
[ https://issues.apache.org/jira/browse/FLUME-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Greco updated FLUME-2706: --- Attachment: FLUME-2706-0.patch > Camel source > > > Key: FLUME-2706 > URL: https://issues.apache.org/jira/browse/FLUME-2706 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: David Greco >Priority: Minor > Fix For: v1.7.0 > > Attachments: FLUME-2706-0.patch > > > This component can start Camel routes, in this way provides a very powerful > mechanism for ingesting data from virtually any source supported by Camel > http://camel.apache.org. > This source can be configured either with a Camel URI or with an XML file > containing route specifications. > The configuration is very simple, let's show a couple of examples: > 1. Configuration by an URI: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.sourceURI = > twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken= > any URI supported by Camel components is valid. For Twitter, see > [here](http://camel.apache.org/twitter.html). > 2. Configuration by an xml file: > tier1.sources = source1 > tier1.channels = channel1 > tier1.sinks = sink1 > tier1.sources.source1.type = org.apache.flume.source.camel.CamelSource > tier1.sources.source1.routesFile = conf/routes.xml > where the routes.xml can contain something like: > http://camel.apache.org/schema/spring";> > > uri="twitter://streaming/sample?type=event&consumerKey=&consumerSecret=&accessToken="/> > > > > any route that wants to send data to flume must have as a target endpoint an > URI with the following format: direct-vm://, so in > our case the CamelSource's name is source1 and consequently the endpoint URI > is: direct-vm://source1 as shown in the XML snippet above. > The sourceURI property takes always precedence on the routesFile property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
