Progress on Apache Drill « Big Data Craft By Camuel Gilyadov, on September 4th, 2012 We are continuing our efforts in contributing our OpenDremel code to Apache Drill project and look forward to be active with it right after that. Right now the efforts are being put into our ANTLR-based parser, we want to make it work with the new grammar of BigQuery language. Next on, we plan to refactor and contribute the Semantic Analyzer, which processes the output of the parser into an intermediate form, resolving references and rewriting (flattening) the query into single full table scan operation. The final phase of OpenDremel – Drill merge, will be the contribution of the code generator based on the Apache Velocity templates. Everyone who wishes to help is welcome. We probably will use repo as a staging area or the Apache git repo directly, it all depends on what will be proposed by Ted Dunning – the Apache Drill Champion. We look ahead to Apache Drill with pluggable frontends and pluggable backends.
mikeaddison93/hoya Implementing the SaaS Maturity Model - SaaS Addict When it comes to SaaS maturity model, maturity is not an all-or-nothing proposition, as a SaaS application can possess one or two important attributes and still manage to fit the typical definition and meet the essential business requirements. So in that case the app architects may choose not to meet or fulfill other attributes, especially if in so doing the action would be rendered cost ineffective. Broadly speaking, SaaS maturity can be demonstrated using a delivery model with 4 distinct levels, with each level distinguished from all other previous ones by simply adding one, two or more attributes. The four levels are briefly described below. Level I: Custom/ Ad Hoc This level of SaaS maturity resembles the conventional ASP (application service provider) software delivery model with its origin in the 1990s. Level II: Configurable This is the 2nd level SaaS maturity is where your SaaS vendor hosts a totally different instance of the SaaS application for each tenant or customer.
cpitman/spark-drools-example: A simple example of how to integrate drools into an Apache Spark job NGDATA - Lily - Smart Data, at Scale, made Easy Lily is Smart Data, at Scale, made Easy. Lily is a data management platform combining planet-sized data storage, indexing and search with on-line, real-time usage tracking, audience analytics and content recommendations. It's a one-stop-platform for any organization confronted with Big Data challenges that seeks rapid implementation, rock-solid performance at scale, and efficiency at management. Lily unifies Apache HBase, Hadoop and Solr into a comprehensively integrated, interactive data platform with easy-to-use access APIs, a high-level data model and schema language, flexible, real-time indexing and the expressive search power of Apache Solr. Best of all, Lily is open source - allowing anyone to explore and learn what Lily can do. Features Lily adds the missing bits any Big Data engineer will encounter when trying to combine Apache HBase and Solr into an interactive data management environment:
mikeaddison93/hadoop-20 antlr4/README.md at master · antlr/antlr4 42 Big Data Startups – Vote for the Top 10 Update: The roundup of the 10 finalists is now available on CIO.com. The Big Data space is heating up, and unlike some over-hyped trends (cloud, I’m looking at you), it’s pretty easy to pinpoint the ROI with these tools. When I put out calls for nominees through my Story Source Newsletter, HARO, Twitter, etc., for my upcoming CIO.com story, “10 Big Data Startups to Watch,” I received more than 100 recommendations. Usually, when I get that many recommendations, a good chunk of them can be dismissed out of hand. Not so this time. I’m after those Goldilocks startups. Now comes the hard work. There is one big wrinkle to the voting this time around: this list of 42 isn’t locked. If I do set up a challenge, the startup will have a chance to fight its way onto the list of nominees, and, perhaps, knock someone else off it in the process. I’m going to leave the voting open for a week or so. Voting closes Monday, June 3 at 5 PM PT. 1. Why they might not make the cut: They’re a strong entrant. 2.
Giraph - Welcome To Apache Giraph!