datashard 0.1.1__tar.gz

datashard-0.1.1/.readthedocs.yaml

@@ -0,0 +1,13 @@
+name: python-docs
+base: /Users/farshid/develop/iceberg/datashard
+
+python:
+  version: 3.8
+  install:
+    - requirements: requirements-docs.txt
+
+build:
+  image: latest
+
+sphinx:
+  configuration: docs/conf.py

datashard-0.1.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [2025] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

datashard-0.1.1/PKG-INFO

@@ -0,0 +1,172 @@
+Metadata-Version: 2.4
+Name: datashard
+Version: 0.1.1
+Summary: Safe concurrent data operations for ML/AI workloads, Python implementation of Apache Iceberg concepts
+Author-email: Farshid Ashouri <farsheed.ashouri@gmail.com>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/rodmena-limited/datashard
+Project-URL: Repository, https://github.com/rodmena-limited/datashard
+Project-URL: Documentation, https://datashard.readthedocs.io/
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.7
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Database
+Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.7
+Description-Content-Type: text/plain
+License-File: LICENSE
+Requires-Dist: pyarrow>=10.0.0
+Requires-Dist: typing-extensions>=3.10.0; python_version < "3.10"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Requires-Dist: pytest-cov>=4.0; extra == "dev"
+Requires-Dist: pytest-xdist>=3.0; extra == "dev"
+Requires-Dist: black>=22.0; extra == "dev"
+Requires-Dist: ruff>=0.0.247; extra == "dev"
+Requires-Dist: isort>=5.0; extra == "dev"
+Requires-Dist: mypy>=1.0; extra == "dev"
+Requires-Dist: types-setuptools>=65.0; extra == "dev"
+Provides-Extra: docs
+Requires-Dist: sphinx>=4.0; extra == "docs"
+Requires-Dist: sphinx-rtd-theme>=1.0; extra == "docs"
+Requires-Dist: sphinx-autodoc-typehints>=1.0; extra == "docs"
+Dynamic: license-file
+
+				  //
+                 //
+                //
+               //
+              //
+             //
+            //
+           //
+          //
+         //
+        //
+       //
+      //___________________
+     //                   /
+    //___________________/
+
+       D A T A S H A R D
+
+
+
+
+datashard
+========
+Iceberg-inspired safe concurrent data operations for ML/AI workloads in Python.
+
+
+What is datashard?
+==================
+
+datashard is a Python package that provides safe concurrent data operations for machine learning and AI workloads. It implements the core concepts of Apache Iceberg to give you:
+
+Copyright (c) RODMENA LIMITED. Licensed under Apache 2.0.
+
+- ACID transactions: Operations either fully complete or fully fail
+- Time travel: Ability to look at your data as it existed at any point in time  
+- Safe concurrent access: Multiple processes can read and write safely without corrupting data
+- Data integrity: No matter how many processes access your data simultaneously, it stays intact
+
+
+Demo: 12 Processes Lost 111,434 Operations Due to Data Corruption
+===================================================================
+
+In our test, 12 processes each tried to increment a counter 10,000 times:
+- Expected result: 120,000 (12 × 10,000)
+- Normal files result: Only 8,566 operations completed (111,434 LOST!)
+- datashard result: 120,000 (all operations completed safely)
+
+This is the difference between using regular files and using datashard.
+
+Why Do You Need This for ML/AI?
+===============================
+
+Machine learning and AI projects often involve multiple processes:
+- Different models training on the same data
+- Data pipelines running concurrently  
+- Multiple experiments accessing shared datasets
+- Real-time inference and batch processing happening together
+
+Without proper data management, these operations can corrupt your data. datashard ensures that even when 10 or 100 processes access your data simultaneously, everything works safely.
+
+Real-World Analogy
+==================
+
+Think of regular file access like a shared notebook where 10 people write simultaneously. You get smudged, overlapping text. 
+
+datashard is like a smart filing system with multiple copies of the notebook. When someone updates it, everyone sees a consistent version at the time they looked, and no one's work gets overwritten.
+
+How It Compares to Apache Iceberg
+=================================
+
+Apache Iceberg is a Java-based system built for big data platforms like Spark, Flink, and Hive. It's complex and requires significant infrastructure.
+
+datashard is a pure Python implementation designed for:
+- Individual data scientists and ML engineers
+- Smaller datasets and personal projects
+- Direct Python integration without Java dependencies
+- Quick setup without complex infrastructure
+
+Apache Iceberg offers more features and better performance for huge datasets, but datashard provides the same safety guarantees in a simple Python package.
+
+Installation
+============
+
+pip install datashard
+
+Quick Start
+===========
+
+from datashard import create_table
+
+# Create a table to store your data safely
+table = create_table("/path/to/your/data")
+
+# Multiple processes can safely add data
+table.append_records([
+    {"id": 1, "name": "data_point", "value": 42}
+])
+
+# Access data from any point in time
+historical_snapshot = table.time_travel(snapshot_id=12345)
+
+Safety Guarantee
+================
+
+No matter how many Python processes access your data simultaneously, datashard ensures:
+- No data loss or corruption
+- All operations complete successfully  
+- Consistent views for readers
+- Atomic commits (never partial updates)
+- Recovery from failures without data damage
+
+
+Why I Built datashard
+=======================
+Datashard was born as part of my effort to build a strictly Atomic workflow system. 
+I needed to record huge amounts of metadata from multiple concurrent processes without risking data corruption.
+In the meantime, I do not have good memories of almost all java-based solutions I tried. Iceberg conceptually fit my needs perfectly,
+but I wanted a pure Python solution. There were complexities in the implementation that I couldn't purely do it myslef, by we're in 2025 now and
+Gemiini has made it possible for me to build complex OCC parts in pure Python. 
+This makes it safe for production ML/AI systems where data corruption could be expensive or dangerous.
+
+Enjoy using datashard!
+Farshid.
+
+
+

datashard-0.1.1/README.txt

@@ -0,0 +1,126 @@
+				  //
+                 //
+                //
+               //
+              //
+             //
+            //
+           //
+          //
+         //
+        //
+       //
+      //___________________
+     //                   /
+    //___________________/
+
+       D A T A S H A R D
+
+
+
+
+datashard
+========
+Iceberg-inspired safe concurrent data operations for ML/AI workloads in Python.
+
+
+What is datashard?
+==================
+
+datashard is a Python package that provides safe concurrent data operations for machine learning and AI workloads. It implements the core concepts of Apache Iceberg to give you:
+
+Copyright (c) RODMENA LIMITED. Licensed under Apache 2.0.
+
+- ACID transactions: Operations either fully complete or fully fail
+- Time travel: Ability to look at your data as it existed at any point in time  
+- Safe concurrent access: Multiple processes can read and write safely without corrupting data
+- Data integrity: No matter how many processes access your data simultaneously, it stays intact
+
+
+Demo: 12 Processes Lost 111,434 Operations Due to Data Corruption
+===================================================================
+
+In our test, 12 processes each tried to increment a counter 10,000 times:
+- Expected result: 120,000 (12 × 10,000)
+- Normal files result: Only 8,566 operations completed (111,434 LOST!)
+- datashard result: 120,000 (all operations completed safely)
+
+This is the difference between using regular files and using datashard.
+
+Why Do You Need This for ML/AI?
+===============================
+
+Machine learning and AI projects often involve multiple processes:
+- Different models training on the same data
+- Data pipelines running concurrently  
+- Multiple experiments accessing shared datasets
+- Real-time inference and batch processing happening together
+
+Without proper data management, these operations can corrupt your data. datashard ensures that even when 10 or 100 processes access your data simultaneously, everything works safely.
+
+Real-World Analogy
+==================
+
+Think of regular file access like a shared notebook where 10 people write simultaneously. You get smudged, overlapping text. 
+
+datashard is like a smart filing system with multiple copies of the notebook. When someone updates it, everyone sees a consistent version at the time they looked, and no one's work gets overwritten.
+
+How It Compares to Apache Iceberg
+=================================
+
+Apache Iceberg is a Java-based system built for big data platforms like Spark, Flink, and Hive. It's complex and requires significant infrastructure.
+
+datashard is a pure Python implementation designed for:
+- Individual data scientists and ML engineers
+- Smaller datasets and personal projects
+- Direct Python integration without Java dependencies
+- Quick setup without complex infrastructure
+
+Apache Iceberg offers more features and better performance for huge datasets, but datashard provides the same safety guarantees in a simple Python package.
+
+Installation
+============
+
+pip install datashard
+
+Quick Start
+===========
+
+from datashard import create_table
+
+# Create a table to store your data safely
+table = create_table("/path/to/your/data")
+
+# Multiple processes can safely add data
+table.append_records([
+    {"id": 1, "name": "data_point", "value": 42}
+])
+
+# Access data from any point in time
+historical_snapshot = table.time_travel(snapshot_id=12345)
+
+Safety Guarantee
+================
+
+No matter how many Python processes access your data simultaneously, datashard ensures:
+- No data loss or corruption
+- All operations complete successfully  
+- Consistent views for readers
+- Atomic commits (never partial updates)
+- Recovery from failures without data damage
+
+
+Why I Built datashard
+=======================
+Datashard was born as part of my effort to build a strictly Atomic workflow system. 
+I needed to record huge amounts of metadata from multiple concurrent processes without risking data corruption.
+In the meantime, I do not have good memories of almost all java-based solutions I tried. Iceberg conceptually fit my needs perfectly,
+but I wanted a pure Python solution. There were complexities in the implementation that I couldn't purely do it myslef, by we're in 2025 now and
+Gemiini has made it possible for me to build complex OCC parts in pure Python. 
+This makes it safe for production ML/AI systems where data corruption could be expensive or dangerous.
+
+Enjoy using datashard!
+Farshid.
+
+
+

datashard-0.1.1/datashard/__init__.py

@@ -0,0 +1,24 @@
+"""
+datashard - Safe concurrent data operations for ML/AI workloads
+
+A Python implementation of Apache Iceberg providing ACID transactions,
+time travel, and safe concurrent access.
+"""
+__version__ = "0.1.1"
+__author__ = "RODMENA LIMITED"
+
+# Import the main classes to make them available at package level
+from .iceberg import create_table, load_table, DataFile
+from .data_structures import FileFormat
+from .transaction import Table
+
+
+__all__ = [
+    'create_table',
+    'load_table',
+    'DataFile', 
+    'FileFormat',
+    'Table',
+    '__version__',
+    '__author__'
+]

datashard-0.1.1/docs/README.md

@@ -0,0 +1,149 @@
+# Python Iceberg Implementation
+
+This is a simplified but powerful Python implementation of Apache Iceberg that provides core functionality including ACID transactions, time travel, metadata management, and proper file system operations.
+
+## Features
+
+- **ACID Transactions**: Supports atomic, consistent, isolated, and durable transactions
+- **Time Travel**: Ability to query table state at any point in time
+- **Metadata Management**: Comprehensive metadata tracking and persistence
+- **Snapshotting**: Point-in-time snapshots of table state
+- **File Management**: Proper file system operations, validation, and manifest management
+- **Data Operations**: Reading and writing actual data files (Parquet) with schema management
+
+## Architecture
+
+The implementation consists of several key components:
+
+### Core Data Structures
+- `TableMetadata`: Contains table schema, partition spec, sort order, properties, and snapshot information
+- `Snapshot`: Represents a point-in-time view of the table
+- `DataFile`: Represents individual data files in the table
+- `ManifestFile`: Lists data files and their metadata
+- `Schema`: Defines the table schema
+- `PartitionSpec`: Defines how the table is partitioned
+
+### Core Components
+- `MetadataManager`: Handles metadata persistence and updates
+- `SnapshotManager`: Manages snapshots and time travel functionality
+- `Transaction`: Provides ACID transaction support
+- `Table`: Main table interface that ties everything together
+
+## Usage
+
+### Creating a Table
+
+```python
+from rewrite.iceberg import create_table, DataFile, FileFormat
+
+# Create a new table
+table = create_table("/path/to/your/table")
+
+# Add data files to the table using a transaction
+from rewrite.data_structures import DataFile, FileFormat
+
+data_files = [
+    DataFile(
+        file_path="/data/file1.parquet",
+        file_format=FileFormat.PARQUET,
+        partition_values={"year": 2023, "month": 1},
+        record_count=1000,
+        file_size_in_bytes=102400
+    )
+]
+
+# Use a transaction to add files
+with table.new_transaction() as tx:
+    tx.append_files(data_files)
+    tx.commit()
+```
+
+### Time Travel
+
+```python
+# Get the current snapshot
+current = table.current_snapshot()
+
+# Get a snapshot by ID
+snapshot = table.snapshot_by_id(123456789)
+
+# Get all snapshots
+snapshots = table.snapshots()
+
+# Time travel to a specific snapshot
+traveled_snapshot = table.time_travel(snapshot_id=123456789)
+
+# Time travel to a snapshot as of a specific time
+from datetime import datetime
+timestamp_ms = int(datetime.now().timestamp() * 1000)
+traveled_snapshot = table.time_travel(timestamp=timestamp_ms)
+```
+
+### Transactions
+
+```python
+# Create a transaction
+with table.new_transaction() as tx:
+    # Add files
+    tx.append_files([data_file1, data_file2])
+    
+    # Perform other operations
+    tx.expire_snapshots(older_than_ms=1609459200000)  # Jan 1, 2021
+    
+    # Transaction commits automatically when exiting the 'with' block
+    # or explicitly call tx.commit()
+```
+
+## Data Operations
+
+The implementation includes full data file operations:
+
+- **Parquet Support**: Reading and writing Parquet files using PyArrow
+- **Schema Conversion**: Automatic conversion between Iceberg and PyArrow schemas
+- **Data Validation**: Verification of data compatibility with schema
+- **File Readers/Writers**: Efficient reading and writing of data files
+- **Transaction Integration**: Data operations integrated with ACID transactions
+
+## Storage Format
+
+The implementation stores metadata in JSON format following Iceberg's metadata evolution principles:
+
+- `metadata/`: Contains versioned metadata files (v0.json, v1.json, etc.)
+- `metadata.version-hint.text`: Points to the current metadata version
+- `snapshots/`: Contains snapshot-specific information
+- `manifests/`: Contains manifest list files for each snapshot
+
+## ACID Properties
+
+1. **Atomicity**: All transactions are atomic - they either complete entirely or are rolled back completely
+2. **Consistency**: Metadata is validated on each update to maintain consistency
+3. **Isolation**: Achieved through Optimistic Concurrency Control with base state comparison and retry logic
+4. **Durability**: All metadata changes are immediately persisted to disk
+
+## Limitations
+
+This is a simplified implementation focusing on the core Iceberg concepts. Some advanced features of Apache Iceberg are not implemented:
+
+- Advanced partition transforms beyond basic ones
+- Row-level deletes beyond file-level deletes
+- Advanced optimization operations like file compaction
+- Encryption support
+
+## Optimistic Concurrency Control (OCC)
+
+This implementation properly follows Apache Iceberg's atomic commit pattern:
+
+- Uses base metadata comparison to detect concurrent modifications
+- Implements automatic retry logic with backoff for conflicts
+- Provides proper exception handling when operations cannot be resolved
+- Maintains consistency in concurrent environments without distributed locks
+- Follows the same atomic commit patterns as the Apache Iceberg Java implementation
+
+## Testing
+
+Run the comprehensive test suite:
+
+```bash
+cd rewrite
+python test_iceberg.py
+```