[jira] [Updated] (BIGTOP-1582) Define BigTop 1x

["jay vyas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BIGTOP-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jay vyas updated BIGTOP-1582:
-----------------------------
    Attachment: Screen Shot 2014-12-24 at 9.10.53 AM.png

atttached image of what seems to be the consensus from http://mail-archives.apache.org/mod_mbox/bigtop-user/201412.mbox/%3C66D1B31B-90BA-467B-B31F-1CFACC7E1D13@gmail.com%3E 

> Define BigTop 1x
> ----------------
>
>                 Key: BIGTOP-1582
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1582
>             Project: Bigtop
>          Issue Type: Task
>          Components: general
>    Affects Versions: 1.0.0
>            Reporter: jay vyas
>             Fix For: 1.0.0
>
>         Attachments: Screen Shot 2014-12-24 at 9.10.53 AM.png
>
>
> This is very much early stages and brainstorming, but i think its good to now formalize it into a JIRA that we can vote on.
> - We've had a mailing list thread going on around bigtop 1x, and what it will look like.  
> - theme => Keep it *lean*, make some tough *decisions*, and support something less generic.
> - Attaching an image of what seems to be the *consensus* from the email.  
> Anyone want to comment on it ? 
> The idea seems to be that spark would drive parts of the analytics, and persistance would be around Hbase and/or SOLR, with an in memory caching tier (tachyon/gridgain (soon to be ignite)).  
> This is a way to formalize what we discussed in http://mail-archives.apache.org/mod_mbox/bigtop-user/201412.mbox/%3C66D1B31B-90BA-467B-B31F-1CFACC7E1D13@gmail.com%3E and so on.
> I think the coolest thing we could do  here is to focus on *interop* - something that right now we don't have *time* to do, b/c we are juggling so many components. 



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