I'd like to thank Ran for giving a great talk on NoSQL & Cassa
/**
* @file
* Main view template.
*
* Variables available:
* - $classes_array: An array of classes determined in
* template_preprocess_views_view(). Default classes are:
* .view
* .view-[css_name]
* .view-id-[view_name]
* .view-display-id-[display_name]
* .view-dom-id-[dom_id]
* - $classes: A string version of $classes_array for use in the class attribute
* - $css_name: A css-safe version of the view name.
* - $css_class: The user-specified classes names, if any
* - $header: The view header
* - $footer: The view footer
* - $rows: The results of the view query, if any
* - $empty: The empty text to display if the view is empty
* - $pager: The pager next/prev links to display, if any
* - $exposed: Exposed widget form/info to display
* - $feed_icon: Feed icon to display, if any
* - $more: A link to view more, if any
*
* @ingroup views_templates
*/
?>
by udid
tags:
border:
Large scale analysis solution must be able to provide very fast response time (<1sec) to some complex queries which are typically structured from a large fact table which is joined to many dimension tables and grouped-by them.
Using standard SQL databases such as MySQL InnoDB (as well as leading commercial vendors) will result in poor performance even when correct indexes are set up since in many case the database will be forced to perform unnecessary full table scans which will kill the performance if dimension tables are large.
by Anonymous
tags:
border:
A very thorough list of databases and connection strings. I used several of them - all were accurate.