In this previous blog post we provided a high-level overview of Cloudera Replication Plugin, explaining how it brings cross-platform replication with little configuration. In this post, we will cover how this plugin can be applied in CDP clusters and explain how the plugin enables strong authentication between systems which do not share mutual authentication trust.

If you’ve followed Cloudera for a while, you know we’ve long been singing the praises—or harping on the importance, depending on perspective—of a solid, standalone enterprise data strategy. While certainly not a new concept, Government missions are wholly dependent on real time access/analysis of data (wherever it may be (legacy data centers or public cloud) to render insight to support operational decisions.

For all of the buzz surrounding both artificial intelligence and data-driven management, many companies have seen mixed results in their quest to harness the value of enterprise data. To avoid those pitfalls, we mixed best-of-breed and proprietary solutions to develop our enterprise data platform (EDP), focusing much of our attention on a combination of smart changes in technology, culture and process for data lakes.

Like most organizations, Yellowfin has a CRM tool. The data in your CRM should be able to help you understand how you’re selling and how you win. But everyone I speak to is frustrated by the analytics they get from their CRM. We realized very quickly that the reporting in our CRM tool wasn't meeting our needs, so we built our own solution.

For data analysts, business intelligence professionals, and CTOs to optimize and scale business operations, they must first understand the business data that is available to them. One of the best platforms to turn complicated data points from multiple platforms into a singular, coherent data set is Microsoft Power BI. However, you must first prepare the data sets to eliminate fragmentations and create structural consistency. This article explores how to prepare data for Microsoft Power BI.

Hortonworks DataFlow (HDF) 3.5.2 was released at the end of 2020. The new releases will not continue under HDF as Cloudera brings the best and latest of Apache NiFi in the new Cloudera Flow Management (CFM) product. Getting the latest improvements and new features of NiFi is one of many reasons for you to move your legacy deployments of NiFi on this new platform. To that end, we released a few blog posts to help you migrate from HDF to CFM.

In my previous blog posts, I’ve talked about how you can aggregate data depending on the data type, as well as how you can re-express your data to get more value from it. For this post, let’s look at some of the different ways of measuring your data.

Ask any analyst how they spend the majority of their work day and they’ll tell you: Performing remedial tasks that provide no analytics value. 92% of data workers report that their time is being siphoned away performing operational tasks outside of their roles. Data teams waste an inordinate amount of time maintaining the delicate data-to-dashboards pipelines they’ve created, leaving only 50% of their time to actually analyze data.

Data paves the way for every strategic move made by banks and insurance companies. Whether looking to create a new service, complying with regulations, or overhauling and re-engineering legacy operations, a massive data project is always central to the effort. For financial services businesses, the pace at which they can reshape and repurpose data has become a key determinant of their ability to predict market trends and meet client expectations.

Last week in our BigQuery Reference Guide series, we spoke about the BigQuery resource hierarchy - specifically digging into project and dataset structures. This week, we’re going one level deeper and talking through some of the resources within datasets. In this post, we’ll talk through the different types of tables available inside of BigQuery, and how to leverage routines for data transformation.