dawidwys commented on a change in pull request #361:
URL: https://github.com/apache/flink-web/pull/361#discussion_r458583041
##########
File path: _posts/2020-07-21-catalogs.md
##########
@@ -0,0 +1,188 @@
+---
+layout: post
+title: "Sharing is caring - Catalogs in Flink SQL"
+date: 2020-07-21T08:00:00.000Z
+authors:
+- dawid:
+ name: "Dawid Wysakowicz"
+ twitter: "dwysakowicz"
+---
+
+It's not a surprise that, in an era of digitalization, data is the most
valuable asset in many companies: it's always the base for — and product of —
any analysis or business logic. With an ever-growing number of people working
with data, it's a common practice for companies to build self-service platforms
with the goal of democratizing their access across different teams and —
especially — to enable users from any background to be independent in their
data needs. In such environments, metadata management becomes a crucial aspect.
Without it, users often work blindly, spending too much time searching for
datasets and their location, figuring out data formats and similar cumbersome
tasks.
Review comment:
I though about it again this morning. I removed the first sentence with
the "marketing" wording.
I did not further change the introduction. I understand your point of "using
Flink as a universal query engine..." My idea for this blog was slightly
different though, with more stress on the relevance of catalogs as such. That's
the core idea I build around. Therefore the introduction is not Flink specific
and less technical. Only once I explain the relevance of catalogs I go into the
Flink catalogs support. This is to showcase that Flink does well on that
important topic of catalogs that I explain in the beginning.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
