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

ASF GitHub Bot commented on IGNITE-529:
---------------------------------------

GitHub user shroman opened a pull request:

    https://github.com/apache/ignite/pull/265

    IGNITE-529: Fixed README

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shroman/ignite ignite-529-readme

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/265.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #265
    
----
commit 739ba495cd2913ac8dc581a428c6ca3a07d744e4
Author: shtykh_roman <rsht...@yahoo.com>
Date:   2015-11-26T02:40:48Z

    IGNITE-529: Fixed README

----


> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --------------------------------------------------------------
>
>                 Key: IGNITE-529
>                 URL: https://issues.apache.org/jira/browse/IGNITE-529
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: streaming
>            Reporter: Dmitriy Setrakyan
>            Assignee: Roman Shtykh
>         Attachments: IgniteSinkSetup.txt
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from 
> Apache Flume and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to