Data Engineers
前往频道在 Telegram
Free Data Engineering Ebooks & Courses
显示更多📈 Telegram 频道 Data Engineers 的分析概览
频道 Data Engineers (@sql_engineer) 英语 语言赛道中的 是活跃参与者。目前社区聚集了 10 901 名订阅者,在 教育 类别中位列第 17 965,并在 印度 地区排名第 35 421 位。
📊 受众指标与增长动态
自 невідомо 创建以来,项目保持高速增长,吸引了 10 901 名订阅者。
根据 29 八月, 2026 的最新数据,频道保持稳定运转。过去 30 天订阅人数变化为 293,过去 24 小时变化为 10,整体触达仍然可观。
- 认证状态: 未认证
- 互动率 (ER): 平均受众互动率为 12.66%。内容发布后 24 小时内通常能获得 3.15% 的反应,占订阅者总量。
- 帖子覆盖: 每篇帖子平均可获得 1 380 次浏览,首日通常累积 343 次浏览。
- 互动与反馈: 受众积极参与,单帖平均反应数为 7。
- 主题关注点: 内容集中在 sql, learning, analytic, engineer, link:- 等核心主题上。
📝 描述与内容策略
作者将该频道定位为表达主观观点的平台:
“Free Data Engineering Ebooks & Courses”
凭借高频更新(最新数据采集于 30 八月, 2026),频道始终保持新鲜度与高覆盖。分析显示受众积极互动,使其成为 教育 类别中的关键影响点。
10 901
订阅者
+1024 小时
+297 天
+29330 天
帖子存档
10 901
Pre-Interview Checklist for Big Data Engineer Roles.
➤ SQL Essentials:
- SELECT statements including WHERE, ORDER BY, GROUP BY, HAVING
- Basic JOINS: INNER, LEFT, RIGHT, FULL
- Aggregate functions: COUNT, SUM, AVG, MAX, MIN
- Subqueries, Common Table Expressions (WITH clause)
- CASE statements, advanced JOIN techniques, and Window functions (OVER, PARTITION BY, ROW_NUMBER, RANK)
➤ Python Programming:
- Basic syntax, control structures, data structures (lists, dictionaries)
- Pandas & NumPy for data manipulation: DataFrames, Series, groupby
➤ Hadoop Ecosystem Proficiency:
- Understanding HDFS architecture, replication, and block management.
- Mastery of MapReduce for distributed data processing.
- Familiarity with YARN for resource management and job scheduling.
➤ Hive Skills:
- Writing efficient HiveQL queries for data retrieval and manipulation.
- Optimizing table performance with partitioning and bucketing.
- Working with ORC, Parquet, and Avro file formats.
➤ Apache Spark:
- Spark architecture
- RDD, Dataframe, Datasets, Spark SQL
- Spark optimization techniques
- Spark Streaming
➤ Apache HBase:
- Designing effective row keys and understanding HBase’s data model.
- Performing CRUD operations and integrating HBase with other big data tools.
➤ Apache Kafka:
- Deep understanding of Kafka architecture, including producers, consumers, and brokers.
- Implementing reliable message queuing systems and managing data streams.
- Integrating Kafka with ETL pipelines.
➤ Apache Airflow:
- Designing and managing DAGs for workflow scheduling.
- Handling task dependencies and monitoring workflow execution.
➤ Data Warehousing and Data Modeling:
- Concepts of OLAP vs. OLTP
- Star and Snowflake schema designs
- ETL processes: Extract, Transform, Load
- Data lake vs. data warehouse
- Balancing normalization and denormalization in data models.
➤ Cloud Computing for Data Engineering:
- Benefits of cloud services (AWS, Azure, Google Cloud)
- Data storage solutions: S3, Azure Blob Storage, Google Cloud Storage
- Cloud-based data analytics tools: BigQuery, Redshift, Snowflake
- Cost management and optimization strategies
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
- PySpark + DataFrame API = Data Manipulation
- PySpark + RDD = Distributed Datasets
- PySpark + filter() = Data Filtering
- PySpark + join() = Data Integration
- PySpark + groupBy() = Data Aggregation
- PySpark + orderBy() = Data Sorting
- PySpark + union() = Combining Datasets
- PySpark + withColumn() = Data Transformation
- PySpark + select() = Column Selection
- PySpark + SQL Queries = SQL Integration
- PySpark + createOrReplaceTempView() = Virtual Tables
- PySpark + map() = Data Mapping
- PySpark + reduceByKey() = Data Reduction
- PySpark + partitionBy() = Data Partitioning
- PySpark + broadcast() = Data Broadcasting
- PySpark + accumulators = Shared Variables
- PySpark + Spark SQL = Structured Data
- PySpark + DataFrame Caching = Performance Optimization
- PySpark + Window Functions = Advanced Analytics
- PySpark + UDFs = Custom Functions
- PySpark + Machine Learning = Scalable Models
- PySpark + GraphX = Graph Processing
- PySpark + Streaming = Real-Time Processing
- PySpark + DataFrame Joins = Efficient Merging
- PySpark + MLlib = Machine Learning
- PySpark + Structured Streaming = Continuous Processing
- PySpark + Pipeline API = Workflow Automation
- PySpark + Delta Lake = Reliable Lakes
- PySpark + Databricks = Cloud Platform
- PySpark + ETL Pipelines = Data Extraction
- PySpark + Performance Tuning = Query Efficiency
- PySpark + Cluster Management = Distributed Computing
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
Pyspark interview questions for Data Engineer 2024.
1. How do you deploy PySpark applications in a production environment?
2. What are some best practices for monitoring and logging PySpark jobs?
3. How do you manage resources and scheduling in a PySpark application?
4. Write a PySpark job to perform a specific data processing task (e.g., filtering data, aggregating results).
5. You have a dataset containing user activity logs with missing values and inconsistent data types. Describe how you would clean and standardize this dataset using PySpark.
6. Given a dataset with nested JSON structures, how would you flatten it into a tabular format using PySpark?
8. Your PySpark job is running slower than expected due to data skew. Explain how you would identify and address this issue.
9. You need to join two large datasets, but the join operation is causing out-of-memory errors. What strategies would you use to optimize this join?
10. Describe how you would set up a real-time data pipeline using PySpark and Kafka to process streaming data.
11. You are tasked with processing real-time sensor data to detect anomalies. Explain the steps you would take to implement this using PySpark.
12. Describe how you would design and implement an ETL pipeline in PySpark to extract data from an RDBMS, transform it, and load it into a data warehouse.
13. Given a requirement to process and transform data from multiple sources (e.g., CSV, JSON, and Parquet files), how would you handle this in a PySpark job?
14. You need to integrate data from an external API into your PySpark pipeline. Explain how you would achieve this.
15. Describe how you would use PySpark to join data from a Hive table and a Kafka stream.
16. You need to integrate data from an external API into your PySpark pipeline. Explain how you would achieve this.
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
Part 1: Basic Concepts and Architecture
1. What is a stream in Snowflake, and what are the columns present in a stream?
2. What is the architecture of Snowflake?
3. What is a Snowpipe in the context of Snowflake?
4. Can you explain the concept of a warehouse in Snowflake?
5. What is the data flow, and how many layers are in our projects?
6. How do you convert JSON to the Snowflake VARIANT data type?
7. How are task dependencies managed in Snowflake?
8. Is there a specific table for maintaining notification history in Snowflake?
9. What are alternative methods for loading data into Snowflake without using JSON functions?
10. How can you set up error notifications in Snowflake?
Part 2: Data Management and ETL Processes
1. Could you explain the process of data sharing in Snowflake?
2. Explain the relationship between AWS and SF.
3. How do you move 100 GB of data into SF? Describe the steps you would follow.
4. Differentiate between a View and a Materialized View.
5. Explain the concept of a Merge statement in the context of a relational database.
6. What is the purpose of the pattern function in Snowflake?
7. Have you worked with Snowpipe? If so, describe your experience in creating and using Snowpipe.
8. How can you create a table in Oracle with a time/travel retention period to go back before 12 days?
9. What is the maximum size of a file that can be loaded into an S3 bucket?
10. What are the types of Slowly Changing Dimensions (SCD)?
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
SQL is composed of five key components:
𝐃𝐃𝐋 (𝐃𝐚𝐭𝐚 𝐃𝐞𝐟𝐢𝐧𝐢𝐭𝐢𝐨𝐧 𝐋𝐚𝐧𝐠𝐮𝐚𝐠𝐞): Commands like CREATE, ALTER, DROP for defining and modifying database structures.
𝐃𝐐𝐋 (𝐃𝐚𝐭𝐚 𝐐𝐮𝐞𝐫𝐲 𝐋𝐚𝐧𝐠𝐮𝐚𝐠𝐞): Commands like SELECT for querying and retrieving data.
𝐃𝐌𝐋 (𝐃𝐚𝐭𝐚 𝐌𝐚𝐧𝐢𝐩𝐮𝐥𝐚𝐭𝐢𝐨𝐧 𝐋𝐚𝐧𝐠𝐮𝐚𝐠𝐞): Commands like INSERT, UPDATE, DELETE for modifying data.
𝐃𝐂𝐋 (𝐃𝐚𝐭𝐚 𝐂𝐨𝐧𝐭𝐫𝐨𝐥 𝐋𝐚𝐧𝐠𝐮𝐚𝐠𝐞): Commands like GRANT, REVOKE for managing access permissions.
𝐓𝐂𝐋 (𝐓𝐫𝐚𝐧𝐬𝐚𝐜𝐭𝐢𝐨𝐧 𝐂𝐨𝐧𝐭𝐫𝐨𝐥 𝐋𝐚𝐧𝐠𝐮𝐚𝐠𝐞): Commands like COMMIT, ROLLBACK for managing transactions.
If you're an engineer, you'll likely need a solid understanding of all these components. If you're a data analyst, focusing on DQL will be more relevant. Tailor your learning to the topics that best fit your role.
10 901
Pyspark interview questions for Data Engineer 2024.
1. Describe the shuffle operation in Apache Spark and its impact on performance.
2. What are the different types of joins available in Apache Spark SQL?
3. Provide examples of when to use each. Discuss the optimizations performed by Apache Spark’s Catalyst optimizer.
4. Explain how broadcast variables work in Apache Spark and when they should be used.
5. How does Apache Spark handle memory management and garbage collection in its execution model?
6. Describe the architecture of Apache Spark and its components in a distributed environment. What are the different deployment modes available for running Apache Spark applications? When would you choose each mode?
7. Explain the role of the SparkContext in an Apache Spark application and how it differs from the SparkSession.
8. Discuss the performance tuning techniques you would employ to optimize Apache Spark jobs.
9. How does Apache Spark handle skewed data when performing aggregations or group-bys? Explain the concept of window functions in Apache Spark SQL and provide examples of their usage.
10. Discuss the role of lineage, checkpoints, and RDD persistence in ensuring fault tolerance in Apache Spark.
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
- SQL + SELECT = Querying Data
- SQL + JOIN = Data Integration
- SQL + WHERE = Data Filtering
- SQL + GROUP BY = Data Aggregation
- SQL + ORDER BY = Data Sorting
- SQL + UNION = Combining Queries
- SQL + INSERT = Data Insertion
- SQL + UPDATE = Data Modification
- SQL + DELETE = Data Removal
- SQL + CREATE TABLE = Database Design
- SQL + ALTER TABLE = Schema Modification
- SQL + DROP TABLE = Table Removal
- SQL + INDEX = Query Optimization
- SQL + VIEW = Virtual Tables
- SQL + Subqueries = Nested Queries
- SQL + Stored Procedures = Task Automation
- SQL + Triggers = Automated Responses
- SQL + CTE = Recursive Queries
- SQL + Window Functions = Advanced Analytics
- SQL + Transactions = Data Integrity
- SQL + ACID Compliance = Reliable Operations
- SQL + Data Warehousing = Large Data Management
- SQL + ETL = Data Transformation
- SQL + Partitioning = Big Data Management
- SQL + Replication = High Availability
- SQL + Sharding = Database Scaling
- SQL + JSON = Semi-Structured Data
- SQL + XML = Structured Data
- SQL + Data Security = Data Protection
- SQL + Performance Tuning = Query Efficiency
- SQL + Data Governance = Data Quality
10 901
Data engineering interviews will be 10x easier if you learn these tools in sequence👇
➤ 𝗣𝗿𝗲-𝗿𝗲𝗾𝘂𝗶𝘀𝗶𝘁𝗲𝘀
- SQL is very important
- Learn Python Funddamentals
- Pandas and Numpy Library in Python.
➤ 𝗢𝗻-𝗣𝗿𝗲𝗺 𝘁𝗼𝗼𝗹𝘀
- Learn Pyspark - In Depth (Processing tool)
- Hadoop (Distrubuted Storage)
- Hive (Datawarehouse)
- Hbase (NoSQL Database)
- Airflow (Orchestration)
- Kafka (Streaming platform)
- CICD for production readiness
➤ 𝗖𝗹𝗼𝘂𝗱 (𝗔𝗻𝘆 𝗼𝗻𝗲)
- AWS
- Azure
- GCP
➤ Do a couple of projects to get a good feel of it.
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
HR: "What's your salary expectation?"
Candidate: $8,000 to 10,000 a month.
HR: You are the best-fit for the role but we can only offer $7000.
Candidate: Okay. $7,000 would be fine.
HR: How soon can you start?
Meanwhile the budget for that particular role is $15,000. HR feels like they did a great job in salary negotiation and management will be happy they cut cost for the organisation.
The new employee starts and notices the pay disparity. Guess what happens? Dissatisfaction. Disengagement. Disloyalty.
Two months later, the employee leaves the organization for a better job. The recruitment process starts all over again. Leading to further costs and performance gaps within the team and organisation.
In order to attract and retain top talent, please pay people what they are worth.
10 901
Roadmap for becoming an Azure Data Engineer in 2024:
- SQL
- Basic python
- Cloud Fundamental
- ADF
- Databricks/Spark/Pyspark
- Azure Synapse
- Azure Functions, Logic Apps,
- Azure Storage, Key Vault
- Dimensional Modelling
- Azure Fabric
- End-to-End Project
- Resume Preparation
- Interview Prep
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
Unlock your full potential as a Data Engineer with this detailed career path
Step 1: Fundamentals
Step 2: Data Structures & Algorithms
Step 3: Databases (SQL / NoSQL) & Data Modeling
Step 4: Data Ingestion & Data Storage Techniques
Step 5: Data warehousing tools & Data analytics techniques
Step 6: Major cloud providers and their services related to Data Engineering
Step 7: Tools required for real-time data and batch data pipelines
Step 8: Data Engineering Deployments & ops
10 901
Git commands for Data Engineers
𝟭. 𝗴𝗶𝘁 𝗱𝗶𝗳𝗳: Show file differences not yet staged.
𝟮. 𝗴𝗶𝘁 𝗰𝗼𝗺𝗺𝗶𝘁 -𝗮 -𝗺 "𝗰𝗼𝗺𝗺𝗶𝘁 𝗺𝗲𝘀𝘀𝗮𝗴𝗲": Commit all tracked changes with a message.
𝟯. 𝗴𝗶𝘁 𝘀𝘁𝗮𝘁𝘂𝘀: Show the state of your working directory.
𝟰. 𝗴𝗶𝘁 𝗮𝗱𝗱 𝗳𝗶𝗹𝗲_𝗽𝗮𝘁𝗵:Add file(s) to the staging area.
𝟱. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 -𝗯 𝗯𝗿𝗮𝗻𝗰𝗵_𝗻𝗮𝗺𝗲: Create and switch to a new branch.
𝟲. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 𝗯𝗿𝗮𝗻𝗰𝗵_𝗻𝗮𝗺𝗲: Switch to an existing branch.
𝟳. 𝗴𝗶𝘁 𝗰𝗼𝗺𝗺𝗶𝘁 --𝗮𝗺𝗲𝗻𝗱:Modify the last commit.
𝟴. 𝗴𝗶𝘁 𝗽𝘂𝘀𝗵 𝗼𝗿𝗶𝗴𝗶𝗻 𝗯𝗿𝗮𝗻𝗰𝗵_𝗻𝗮𝗺𝗲: Push a branch to a remote.
𝟵. 𝗴𝗶𝘁 𝗽𝘂𝗹𝗹: Fetch and merge remote changes.
𝟭𝟬. 𝗴𝗶𝘁 𝗿𝗲𝗯𝗮𝘀𝗲 -𝗶: Rebase interactively, rewrite commit history.
𝟭𝟭. 𝗴𝗶𝘁 𝗰𝗹𝗼𝗻𝗲: Create a local copy of a remote repo.
𝟭𝟮. 𝗴𝗶𝘁 𝗺𝗲𝗿𝗴𝗲: Merge branches together.
𝟭𝟯. 𝗴𝗶𝘁 𝗹𝗼𝗴 --𝘀𝘁𝗮𝘁: Show commit logs with stats.
𝟭𝟰. 𝗴𝗶𝘁 𝘀𝘁𝗮𝘀𝗵: Stash changes for later.
𝟭𝟱. 𝗴𝗶𝘁 𝘀𝘁𝗮𝘀𝗵 𝗽𝗼𝗽: Apply and remove stashed changes.
𝟭𝟲. 𝗴𝗶𝘁 𝘀𝗵𝗼𝘄 𝗰𝗼𝗺𝗺𝗶𝘁_𝗶𝗱: Show details about a commit.
𝟭𝟳. 𝗴𝗶𝘁 𝗿𝗲𝘀𝗲𝘁 𝗛𝗘𝗔𝗗~𝟭: Undo the last commit, preserving changes locally.
𝟭𝟴. 𝗴𝗶𝘁 𝗳𝗼𝗿𝗺𝗮𝘁-𝗽𝗮𝘁𝗰𝗵 -𝟭 𝗰𝗼𝗺𝗺𝗶𝘁_𝗶𝗱: Create a patch file for a specific commit.
𝟭𝟵. 𝗴𝗶𝘁 𝗮𝗽𝗽𝗹𝘆 𝗽𝗮𝘁𝗰𝗵_𝗳𝗶𝗹𝗲_𝗻𝗮𝗺𝗲: Apply changes from a patch file.
𝟮𝟬. 𝗴𝗶𝘁 𝗯𝗿𝗮𝗻𝗰𝗵 -𝗗 𝗯𝗿𝗮𝗻𝗰𝗵_𝗻𝗮𝗺𝗲: Delete a branch forcefully.
𝟮𝟭. 𝗴𝗶𝘁 𝗿𝗲𝘀𝗲𝘁: Undo commits by moving branch reference.
𝟮𝟮. 𝗴𝗶𝘁 𝗿𝗲𝘃𝗲𝗿𝘁: Undo commits by creating a new commit.
𝟮𝟯. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗿𝗿𝘆-𝗽𝗶𝗰𝗸 𝗰𝗼𝗺𝗺𝗶𝘁_𝗶𝗱: Apply changes from a specific commit.
𝟮𝟰. 𝗴𝗶𝘁 𝗯𝗿𝗮𝗻𝗰𝗵: Lists branches.
𝟮𝟱. 𝗴𝗶𝘁 𝗿𝗲𝘀𝗲𝘁 --𝗵𝗮𝗿𝗱: Resets everything to a previous commit, erasing all uncommitted changes.
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
Free 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀 𝘁𝗼 𝗹𝗲𝗮𝗿𝗻 Apache 𝘀𝗽𝗮𝗿𝗸 𝗳𝗼𝗿 𝗳𝗿𝗲𝗲
𝟭. 𝗙𝗶𝗿𝘀𝘁 𝗶𝗻𝘀𝘁𝗮𝗹𝗹 𝘀𝗽𝗮𝗿𝗸 𝗳𝗿𝗼𝗺 𝗵𝗲𝗿𝗲 -
https://lnkd.in/gx_Dc8ph
https://lnkd.in/gg6-8xDz
𝟮. 𝗟𝗲𝗮𝗿𝗻 𝗕𝗮𝘀𝗶𝗰 𝘀𝗽𝗮𝗿𝗸 𝗳𝗿𝗼𝗺 𝗵𝗲𝗿𝗲 - https://lnkd.in/ddThYxAS
𝟯. 𝗟𝗲𝗮𝗿𝗻 𝗔𝗱𝘃𝗮𝗻𝗰𝗲 𝘀𝗽𝗮𝗿𝗸 𝗳𝗿𝗼𝗺 𝗵𝗲𝗿𝗲 - https://lnkd.in/dvZUiJZT
𝟰. 𝗔𝗽𝗮𝗰𝗵𝗲 𝗦𝗽𝗮𝗿𝗸 𝗺𝘂𝘀𝘁 𝗿𝗲𝗮𝗱 𝗯𝗼𝗼𝗸 - https://lnkd.in/d5-KiHHd
𝟱. 𝗦𝗽𝗮𝗿𝗸 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝘆𝗼𝘂 𝗺𝘂𝘀𝘁 𝗱𝗼 -
https://lnkd.in/gE8hsyZx
https://lnkd.in/gwWytS-Q
https://lnkd.in/gR7DR6_5
𝟲. 𝗙𝗶𝗻𝗮𝗹𝗹𝘆 𝘀𝗽𝗮𝗿𝗸 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 -
https://lnkd.in/dFP5yiHT
https://lnkd.in/dweZX3RA
Here, you can find Data Engineering Resources 👇
https://topmate.io/analyst/910180
All the best 👍👍
10 901
🔺 Data engineering Free Courses
1️⃣ Data Engineering Course : Learn the basics of data engineering.
2️⃣ Data Engineer Learning Path course : a comprehensive road map to become a data engineer.
3️⃣ The Data Eng Zoomcamp course : a practical course to learn data engineering
10 901
Interviewer: You have 2 minutes. Explain the difference between Caching and Persisting in Spark.
➤ 𝗖𝗮𝗰𝗵𝗶𝗻𝗴:
Caching in Apache Spark involves storing RDDs in memory temporarily. When an RDD is cached, its partitions are kept in memory across multiple operations, allowing for faster access and reuse of intermediate results.
➤ 𝗣𝗲𝗿𝘀𝗶𝘀𝘁𝗶𝗻𝗴:
Persisting in Apache Spark is similar to caching but offers more flexibility in terms of storage options. When you persist an RDD, you can specify different storage levels such as MEMORY_ONLY, MEMORY_AND_DISK, or DISK_ONLY, depending on your requirements
➤ 𝗞𝗲𝘆 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲𝘀 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗰𝗮𝗰𝗵𝗶𝗻𝗴 𝗮𝗻𝗱 𝗽𝗲𝗿𝘀𝗶𝘀𝘁𝗶𝗻𝗴:
- While caching stores RDDs in memory by default, persisting allows you to choose different storage levels, including disk storage. Caching is suitable for scenarios where RDDs need to be reused in subsequent operations within the same Spark job.
- whereas persisting is more versatile and can be used to store RDDs across multiple jobs or even persist them to disk for fault tolerance.
➤ 𝗘𝘅𝗮𝗺𝗽𝗹𝗲 𝗼𝗳 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝘄𝗼𝘂𝗹𝗱 𝘂𝘀𝗲 𝗰𝗮𝗰𝗵𝗶𝗻𝗴 𝘃𝗲𝗿𝘀𝘂𝘀 𝗽𝗲𝗿𝘀𝗶𝘀𝘁𝗶𝗻𝗴
- Let's say we have an iterative algorithm where the same RDD is accessed multiple times within a loop. In this case, caching the RDD would be beneficial as it would avoid recomputation of the RDD's partitions in each iteration, resulting in significant performance gains.
- On the other hand, if we need to persist RDDs across multiple Spark jobs or need fault tolerance, persisting would be more appropriate.
➤ 𝗛𝗼𝘄 𝗱𝗼𝗲𝘀 𝗦𝗽𝗮𝗿𝗸 𝗵𝗮𝗻𝗱𝗹𝗲 𝗰𝗮𝗰𝗵𝗶𝗻𝗴 𝗮𝗻𝗱 𝗽𝗲𝗿𝘀𝗶𝘀𝘁𝗶𝗻𝗴 𝘂𝗻𝗱𝗲𝗿 𝘁𝗵𝗲 𝗵𝗼𝗼𝗱
Spark employs a lazy evaluation strategy, so RDDs are not actually cached or persisted until an action is triggered. When an action is called on a cached or persisted RDD, Spark checks if the data is already in memory or on disk. If not, it calculates the RDD's partitions and stores them accordingly based on the specified storage level.
That’s the difference between Caching and Persisting in Spark.
10 901
Frequently asked SQL interview for Data Analyst/Data Engineer
1 What is SQL and what are its main features?
2 Order of writing SQL query?
3Order of execution of SQL query?
4 What are some of the most common SQL commands?
5 What’s a primary key & foreign key?
6 All types of joins and questions on their outputs?
7 Explain all window functions and difference between them?
8 What is stored procedure?
9 Difference between stored procedure & Functions in SQL?
10 What is trigger in SQL?
