Skip to content

Commit 216edd1

Browse files
committed
Fix spellings
1 parent 744f9cd commit 216edd1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/blog/hive-to-unity-catalog-data-migration-databricks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ to catalog and assess tables within the Hive Metastore. This enabled us to filte
5151
essential data.
5252

5353
We collaborated with multiple stakeholders, from schema owners to data engineers, for input on which tables were
54-
critical and required for daily operations. This info-gathering stage identified schemas for migration and non-essential
54+
critical and required for daily operations. This information-gathering stage identified schemas for migration and non-essential
5555
ones for removal, enhancing the organization’s data efficiency.
5656

5757
## **Execution Phase**
@@ -128,7 +128,7 @@ As with any large-scale project, there were a few unexpected challenges along th
128128
was the importance of removing migrated tables from Hive immediately after the migration. Initially, we delayed this
129129
step, which led to users continuing to write to the old tables in Hive, causing data divergence.
130130

131-
The takeaway? **Don’t wait to delete migrated tables from Hive**—doing so ensures data consistency and smooths the
131+
The takeaway? **Don’t wait to delete migrated tables from Hive**—doing so ensures data consistency and smoothes the
132132
transition to Unity Catalog. This small adjustment made a huge difference in the overall process.
133133

134134
## **Conclusion: Strategic Impact and Future Roadmap**

0 commit comments

Comments
 (0)