falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-37) Falcon - Dashboard Feature
Date Fri, 11 Oct 2013 10:38:41 GMT

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

Srikanth Sundarrajan commented on FALCON-37:

There is likely to be plenty of information about feed status and process completion status,
much of which is well structured with clear schema. DB is probably the cheapest way to do
this. Besides backup, security, replication, HA etc are well understood in this space with
no additional operability overheads. I do agree that there may be frequent cases where JMS
messages might be modified, but majority of them would for supporting the orchestration requirement
for FALCON and may not be for dashboard consumption. Only relevant information from JMS messages
that have an analytics/monitoring application need to be promoted to DB. MQ persistence layer
will treat message as a blob and we can't meaningfully light up the dashboard with that. One
other option that we can probably explore is to store this information through elastic search
like system which supports faceted queries. 

> Falcon - Dashboard Feature
> --------------------------
>                 Key: FALCON-37
>                 URL: https://issues.apache.org/jira/browse/FALCON-37
>             Project: Falcon
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: 0.4
>            Reporter: Srikanth Sundarrajan
>            Assignee: Srikanth Vittal
>         Attachments: Falcon – Dashboard.pdf

This message was sent by Atlassian JIRA

View raw message