falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-288) Persist lineage information into a persistent store
Date Sun, 02 Mar 2014 06:29:19 GMT

    [ https://issues.apache.org/jira/browse/FALCON-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917301#comment-13917301

Venkatesh Seetharam commented on FALCON-288:

Also, on second thoughts, the name property can be unique for a vertex. We need to think how
we will handle replication where in if we have an edge from feed-instance to the bcp cluster
as a replicated edge, we should be good.

What do you think?

> Persist lineage information into a persistent store
> ---------------------------------------------------
>                 Key: FALCON-288
>                 URL: https://issues.apache.org/jira/browse/FALCON-288
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.5
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>              Labels: lineage
>         Attachments: Dependency Graph.png, FALCON-288-Hive-Review.patch, FALCON-288-review-v1.patch,
FALCON-288-review.patch, FALCON-288-v1.patch, Lineage Over Dependency.png
> Need to evaluate the store - rdbms vs graph db. Leaning towards latter since the data
is hierarchical.

This message was sent by Atlassian JIRA

View raw message