[SDP] DatasetManager and (table and persistent view) materialization

Author: jaceklaskowski

docs/declarative-pipelines/DatasetManager.md

@@ -1,6 +1,11 @@
 # DatasetManager
 
-!!! note "Scala object"
+`DatasetManager` is a global manager to [materialize datasets](#materializeDatasets) (tables and persistent views).
+
+!!! note ""
+    **Materialization** is a process of publishing tables and persistent views to session [TableCatalog](../connector/catalog/TableCatalog.md) and [SessionCatalog](../SessionCatalog.md), for tables and persistent views, respectively.
+
+??? note "Scala object"
     `DatasetManager` is an `object` in Scala which means it is a class that has exactly one instance (itself).
     A Scala `object` is created lazily when it is referenced for the first time.
 
@@ -22,6 +27,8 @@ materializeDatasets(
 
 For every table to be materialized, `materializeDatasets` [materializeTable](#materializeTable).
 
+In the end, `materializeDatasets` [materializeViews](#materializeViews).
+
 ---
 
 `materializeDatasets` is used when:
@@ -52,12 +59,49 @@ Materializing metadata for table [identifier].
 
 For an existing table, `materializeTable` wipes data out (`TRUNCATE TABLE`) if it is`isFullRefresh` or the table is not [streaming](Table.md#isStreamingTable).
 
-For an existing table, `materializeTable` requests the `TableCatalog` to [alterTable](../connector/catalog/TableCatalog.md#alterTable) if there are any changes in the schema or table properties.
+For an existing table, `materializeTable` requests the `TableCatalog` to [alter the table](../connector/catalog/TableCatalog.md#alterTable) if there are any changes in the schema or table properties.
 
 Unless created already, `materializeTable` requests the `TableCatalog` to [create the table](../connector/catalog/TableCatalog.md#createTable).
 
 In the end, `materializeTable` requests the `TableCatalog` to [load the materialized table](../connector/catalog/TableCatalog.md#loadTable) and returns the given [Table](Table.md) back (with the [normalized table storage path](Table.md#normalizedPath) updated to the `location` property of the materialized table).
 
+### Materialize Views { #materializeViews }
+
+```scala
+materializeViews(
+  virtualizedConnectedGraphWithTables: DataflowGraph,
+  context: PipelineUpdateContext): Unit
+```
+
+`materializeViews` requests the given [DataflowGraph](DataflowGraph.md) for the [persisted views](DataflowGraph.md#persistedViews) to materialize (_publish or refresh_).
+
+!!! note "Publish (Materialize) Views"
+    To publish a view, it is required that all the input sources must exist in the metastore.
+    If a Persisted View target reads another Persisted View source, the source must be published first.
+
+`materializeViews`...FIXME
+
+For each view to be persisted (with no pending inputs), `materializeViews` [materialize the view](#materializeView).
+
+#### Materialize View { #materializeView }
+
+```scala
+materializeView(
+  view: View,
+  flow: ResolvedFlow,
+  spark: SparkSession): Unit
+```
+
+`materializeView` [executes a CreateViewCommand logical command](../logical-operators/CreateViewCommand.md).
+
+---
+
+`materializeView` creates a [CreateViewCommand](../logical-operators/CreateViewCommand.md) logical command (as a `PersistedView` with `allowExisting` and `replace` flags enabled).
+
+`materializeView` requests the given [ResolvedFlow](ResolvedFlow.md) for the [QueryContext](ResolutionCompletedFlow.md#queryContext) to set the current catalog and current database, if defined, in the session [CatalogManager](../connector/catalog/CatalogManager.md).
+
+In the end, `materializeView` [executes the CreateViewCommand](../logical-operators/CreateViewCommand.md#run).
+
 ## constructFullRefreshSet { #constructFullRefreshSet }
 
 ```scala