update

_posts/2024-11-04-Deletion-Vectors.md

@@ -257,8 +257,7 @@ Deletion vectors are an excellent _default_ configuration for Delta tables **pro
 That said, there's a couple scenarios where you will not want to enable deletion vectors:
 - **Infrequent Writes, Frequent Reads**: If a table has infrequent writes but frequent reads, deletion vectors may introduce unnecessary read overhead. For example, if you only modify data monthly but run ad-hoc queries daily, it may make more sense to use _copy-on-write_ to avoid merging data on read for every query.
 
-    ![alt text](/assets/img/posts/Deletion-Vectors/deletion-vector-guidance2.excalidraw.svg){: .excalidraw-image }
-    ![Description of Image](/assets/img/posts/Deletion-Vectors/deletion-vector-guidance3.excalidraw.png){: .excalidraw-img }
+    ![Deletion vector guidance](/assets/img/posts/Deletion-Vectors/deletion-vector-guidance3.excalidraw.png){: .excalidraw-img }
 
 - **External Delta Compatibility Requirements**: Deletion vectors require Delta Lake version 2.3 or newer, with reader version 3 and writer version 7. This means older readers or tools not yet supporting deletion vectors will encounter compatibility issues.
 - **Fabric Pipeline COPY Activity**: Currently, the COPY activity in Fabric does not support deletion vectors. It will return all active Parquet files without filtering out records included in deletion vectors, meaning deleted or updated data will reappear unless an `OPTIMIZE` operation is run before each COPY activity. Full support for deletion vectors in COPY activities is expected in the next 3-4 months.

_sass/type-on-strap.scss

@@ -52,5 +52,4 @@ Put it right after this comment for your changes to be applied over the default
 Then create your _custom.scss right next to type-on-strap.scss and add in it all
 of the unique scss that your blog needs.
 
-*/
-@import 'custom';
+*/