[
https://issues.apache.org/jira/browse/FLUME-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651196#comment-13651196
]
Saikat Kanjilal commented on FLUME-2035:
----------------------------------------
My inclination is to keep flume constructs completely separated from the graph
constructs, from the perspective of flume it should understand
sinks/sources/channels, where knowledge of the graph becomes important is the
actual graphsink which would know particulars about the graphstore constraints.
Another idea I had was to drain a channel and write directly to the backing
indexing store for neo4j which is lucene.
I'd like to quickly bring together a list of initial features quickly and roll
something out that we can iterate on.
> GraphSink for flume
> -------------------
>
> Key: FLUME-2035
> URL: https://issues.apache.org/jira/browse/FLUME-2035
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Reporter: Saikat Kanjilal
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The goal of this feature is to implement a graph sink for flume , the sink
> will connect to both Titan and neo4j and others through an abstraction layer.
--
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
