Skip to main content

Explore Delta Lake

Explore Delta Lake:

Delta Lake is an open-source data storage layer that runs on top of existing data lake systems, such as Apache Hadoop or Amazon S3. It was developed by Databricks, a company that provides a unified analytics platform for data engineering, data science, and machine learning.

Delta Lake provides ACID transactions, schema enforcement, and other data management features on top of data lakes, which are typically used for storing large volumes of unstructured and semi-structured data. By adding these features, Delta Lake makes data lakes more suitable for use cases where data quality, consistency, and reliability are important, such as data science, machine learning, and analytics.

Some of the key features of Delta Lake include:

ACID Transactions: Delta Lake provides transactional guarantees for both batch and streaming data. This means that data operations, such as inserts, updates, and deletes, are executed in an atomic, consistent, isolated, and durable (ACID) manner. ACID transactions ensure data integrity and consistency, even in the face of concurrent updates or failures.

Schema Enforcement: Delta Lake provides schema enforcement, which ensures that data adheres to a predefined schema. This feature allows for easier data validation, data quality checks, and data governance. Additionally, Delta Lake allows for schema evolution, meaning that the schema can be changed over time without disrupting existing data.



Ref.: https://delta.io/static/delta-hp-hero-bottom-46084c40468376aaecdedc066291e2d8.png

Time Travel: Delta Lake provides time travel, which allows for versioning and historical querying of data. This feature enables data analysts and data scientists to query data at different points in time, enabling them to track changes and understand trends over time.

Unified Batch and Streaming: Delta Lake supports both batch and streaming workloads, allowing for real-time data processing and analytics. This feature makes it easier to build end-to-end data pipelines that can handle both batch and streaming data, without requiring separate data storage or processing systems.

Open Source: Delta Lake is an open-source project, meaning that it is freely available to use and contribute to. This allows organizations to customize and extend Delta Lake to meet their specific needs and use cases.

Overall, Delta Lake provides a more reliable and consistent data storage layer on top of data lakes, making it easier for organizations to manage and analyze their data effectively. It has become a popular choice for data science and analytics workloads, particularly for organizations that use the Apache Spark processing engine.

Comments

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...