sop4py 2.0.0__tar.gz → 2.0.1__tar.gz

{sop4py-2.0.0/sop4py.egg-info → sop4py-2.0.1}/PKG-INFO

@@ -1,27 +1,29 @@
 Metadata-Version: 2.4
 Name: sop4py
-Version: 2.0.0
-Summary: Scalable Objects Persistence for Python.
+Version: 2.0.1
+Summary: Scalable Objects Persistence for Python. Beta 3 Release
 Author-email: Gerardo Recinto <gerardorecinto@yahoo.com>
 Classifier: Programming Language :: Python :: 3
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
 Requires-Python: >=3.7
 Description-Content-Type: text/markdown
-Requires-Dist: libjsondb_amd64darwin.dylib
-Requires-Dist: libjsondb_amd64darwin.h
-Requires-Dist: libjsondb_arm64darwin.dylib
-Requires-Dist: libjsondb_arm64darwin.h
-Requires-Dist: libjsondb_amd64linux.so
-Requires-Dist: libjsondb_amd64linux.h
-Requires-Dist: libjsondb_arm64linux.so
-Requires-Dist: libjsondb_arm64linux.h
-Requires-Dist: libjsondb_amd64windows.dll
-Requires-Dist: libjsondb_amd64windows.h
 
 # What is SOP?
 
-Scalable Objects Persistence (SOP) is a raw storage engine that bakes together a set of storage related features & algorithms in order to provide the most efficient & reliable (ACID attributes of transactions) technique (known) of storage management and rich search, as it brings to the application, the raw muscle of "raw storage", direct IO communications w/ disk drives. In a code library form factor.
+Scalable Objects Persistence (SOP) is a raw storage engine that bakes together a set of storage related features & algorithms in order to provide the most efficient & reliable (ACID attributes of transactions) technique (known) of storage management and rich search, as it brings to the application, the raw muscle of "raw storage", direct IO operations w/ disk drives. In a code library form factor.
+
+Other "key advances" in database technology available in this SOP release:
+* Serverless (or all servers!) operations mode in the cluster, i.e. - your applications that use SOP library are server-less
+* Uses a new storage & L1/L2 caching strategy that is ground breaking in performance & efficiency
+* New superfast realtime Orchestration engine fit for database transactions
+* Support for small, medium to large/very large (multi-GBs/TB) data management
+* Sports advanced/efficient/high tolerance software based (via Erasure Coding) replication
+* Horizontal & Vertical scaling in storage and cluster processes
+* New database storage strategy that uses segment files which avoids having to manage a huge file, resulting in higher IO efficiency & file system/disk drive friendly (medium sized) data files
+* Built-in data caching, your application data can be cached automatically via config setting. No need to write special code to cache certain data set in Redis, for example. SOP can provide that if configured
+* Host your applications across platforms, e.g. - microservice cluster running in Linux, another cluster or instance running in Windows, and all SOPs inter-operating with one another seamlessly and data stored in same set of disk drives. Freedom to use popular hardware architecture & OS of your choice(s)!
+* Unlimited B-trees, limited only by your hardware resources. Each B-tree store, as the name implies, is a B-tree serving super-fast, sorted by Key (Key & Value pair) data sets
 
 # SOP supported Hardware/OS
 SOP supports popular architectures & Operating Systems such as Linux, Darwin & Microsoft Windows, in both ARM64 & AMD64 architectures. For Windows, only AMD64 is supported since it is the only architecture Windows is available in.
@@ -42,6 +44,7 @@ Following steps outlines how to use the Scalable Objects Persistence code librar
 * Follow standard Python package import and start coding to use the SOP for Python code library for data management. Import the sop package in your python code file.
 * Specify Home base folders where Store info & Registry data files will be stored.
 * Specify Erasure Coding (EC) configuration details which will be used by SOP's EC based replication.
+* Open the global Redis connection
 * Create a transaction
 * Begin a transaction
 * Create a new B-tree, or Open an existing B-tree
@@ -51,9 +54,10 @@ Following steps outlines how to use the Scalable Objects Persistence code librar
 Below is an example code black for illustrating the above steps. For other SOP B-tree examples, you can checkout the code in the unit tests test_btree.py & test_btree_idx.py files that comes w/ the SOP package you downloaded from pypi.
 
 ```
-import sop.transaction
-import sop.btree
-import sop.context
+from sop import transaction
+from sop import btree
+from sop import context
+from sop import redis
 
 stores_folders = ("/disk1", "/disk2")
 ec = {
@@ -76,8 +80,8 @@ ec = {
 # Transaction Options (to).
 to = transaction.TransationOptions(
     transaction.TransactionMode.ForWriting.value,
-    # commit timeout of 5mins
-    5,
+    # commit timeout of 15mins
+    15,
     # Min Registry hash mod value is 250, you can specify higher value like 1000. A 250 hashmod
     # will use 1MB sized file segments. Good for demo, but for Prod, perhaps a bigger value is better.
     transaction.MIN_HASH_MOD_VALUE,
@@ -90,9 +94,10 @@ to = transaction.TransationOptions(
 # Context object.
 ctx = context.Context()
 
-# initialize/open SOP global Redis connection
-ro = RedisOptions()
-Redis.open_connection(ro)
+# initialize/open SOP global Redis connection. You can specify your Redis cluster host address(es) & port, etc
+# but defaults to localhost and default Redis port # if none is specified.
+ro = redis.RedisOptions()
+redis.Redis.open_connection(ro)
 
 t = transaction.Transaction(ctx, to)
 t.begin()
@@ -103,7 +108,9 @@ cache = btree.CacheConfig()
 bo = btree.BtreeOptions("barstoreec", True, cache_config=cache)
 bo.set_value_data_size(btree.ValueDataSize.Small)
 
-# create the new "barstoreec" b-tree store.
+# create the new "barstoreec" b-tree store. Once created, you can just use the "open" method. Perhaps
+# you can have a code set for creating B-trees like "admin only" script. Then all other app code uses
+# the "open" method.
 b3 = btree.Btree.new(ctx, bo, t)
 
 # Since we've specified Native data type = True in BtreeOptions, we can use "integer" values as Key.
@@ -111,11 +118,12 @@ l = [
     btree.Item(1, "foo"),
 ]
 
-# Add Item to the B-tree,
+# Add Item to the B-tree.
 b3.add(ctx, l)
 
 # Commit the transaction to finalize the new B-tree (store) change.
 t.commit(ctx)
+print("ended.")
 ```
 
 # SOP in Github

{sop4py-2.0.0 → sop4py-2.0.1}/README.md

@@ -1,6 +1,18 @@
 # What is SOP?
 
-Scalable Objects Persistence (SOP) is a raw storage engine that bakes together a set of storage related features & algorithms in order to provide the most efficient & reliable (ACID attributes of transactions) technique (known) of storage management and rich search, as it brings to the application, the raw muscle of "raw storage", direct IO communications w/ disk drives. In a code library form factor.
+Scalable Objects Persistence (SOP) is a raw storage engine that bakes together a set of storage related features & algorithms in order to provide the most efficient & reliable (ACID attributes of transactions) technique (known) of storage management and rich search, as it brings to the application, the raw muscle of "raw storage", direct IO operations w/ disk drives. In a code library form factor.
+
+Other "key advances" in database technology available in this SOP release:
+* Serverless (or all servers!) operations mode in the cluster, i.e. - your applications that use SOP library are server-less
+* Uses a new storage & L1/L2 caching strategy that is ground breaking in performance & efficiency
+* New superfast realtime Orchestration engine fit for database transactions
+* Support for small, medium to large/very large (multi-GBs/TB) data management
+* Sports advanced/efficient/high tolerance software based (via Erasure Coding) replication
+* Horizontal & Vertical scaling in storage and cluster processes
+* New database storage strategy that uses segment files which avoids having to manage a huge file, resulting in higher IO efficiency & file system/disk drive friendly (medium sized) data files
+* Built-in data caching, your application data can be cached automatically via config setting. No need to write special code to cache certain data set in Redis, for example. SOP can provide that if configured
+* Host your applications across platforms, e.g. - microservice cluster running in Linux, another cluster or instance running in Windows, and all SOPs inter-operating with one another seamlessly and data stored in same set of disk drives. Freedom to use popular hardware architecture & OS of your choice(s)!
+* Unlimited B-trees, limited only by your hardware resources. Each B-tree store, as the name implies, is a B-tree serving super-fast, sorted by Key (Key & Value pair) data sets
 
 # SOP supported Hardware/OS
 SOP supports popular architectures & Operating Systems such as Linux, Darwin & Microsoft Windows, in both ARM64 & AMD64 architectures. For Windows, only AMD64 is supported since it is the only architecture Windows is available in.
@@ -21,6 +33,7 @@ Following steps outlines how to use the Scalable Objects Persistence code librar
 * Follow standard Python package import and start coding to use the SOP for Python code library for data management. Import the sop package in your python code file.
 * Specify Home base folders where Store info & Registry data files will be stored.
 * Specify Erasure Coding (EC) configuration details which will be used by SOP's EC based replication.
+* Open the global Redis connection
 * Create a transaction
 * Begin a transaction
 * Create a new B-tree, or Open an existing B-tree
@@ -30,9 +43,10 @@ Following steps outlines how to use the Scalable Objects Persistence code librar
 Below is an example code black for illustrating the above steps. For other SOP B-tree examples, you can checkout the code in the unit tests test_btree.py & test_btree_idx.py files that comes w/ the SOP package you downloaded from pypi.
 
 ```
-import sop.transaction
-import sop.btree
-import sop.context
+from sop import transaction
+from sop import btree
+from sop import context
+from sop import redis
 
 stores_folders = ("/disk1", "/disk2")
 ec = {
@@ -55,8 +69,8 @@ ec = {
 # Transaction Options (to).
 to = transaction.TransationOptions(
     transaction.TransactionMode.ForWriting.value,
-    # commit timeout of 5mins
-    5,
+    # commit timeout of 15mins
+    15,
     # Min Registry hash mod value is 250, you can specify higher value like 1000. A 250 hashmod
     # will use 1MB sized file segments. Good for demo, but for Prod, perhaps a bigger value is better.
     transaction.MIN_HASH_MOD_VALUE,
@@ -69,9 +83,10 @@ to = transaction.TransationOptions(
 # Context object.
 ctx = context.Context()
 
-# initialize/open SOP global Redis connection
-ro = RedisOptions()
-Redis.open_connection(ro)
+# initialize/open SOP global Redis connection. You can specify your Redis cluster host address(es) & port, etc
+# but defaults to localhost and default Redis port # if none is specified.
+ro = redis.RedisOptions()
+redis.Redis.open_connection(ro)
 
 t = transaction.Transaction(ctx, to)
 t.begin()
@@ -82,7 +97,9 @@ cache = btree.CacheConfig()
 bo = btree.BtreeOptions("barstoreec", True, cache_config=cache)
 bo.set_value_data_size(btree.ValueDataSize.Small)
 
-# create the new "barstoreec" b-tree store.
+# create the new "barstoreec" b-tree store. Once created, you can just use the "open" method. Perhaps
+# you can have a code set for creating B-trees like "admin only" script. Then all other app code uses
+# the "open" method.
 b3 = btree.Btree.new(ctx, bo, t)
 
 # Since we've specified Native data type = True in BtreeOptions, we can use "integer" values as Key.
@@ -90,11 +107,12 @@ l = [
     btree.Item(1, "foo"),
 ]
 
-# Add Item to the B-tree,
+# Add Item to the B-tree.
 b3.add(ctx, l)
 
 # Commit the transaction to finalize the new B-tree (store) change.
 t.commit(ctx)
+print("ended.")
 ```
 
 # SOP in Github

{sop4py-2.0.0 → sop4py-2.0.1}/pyproject.toml

@@ -7,11 +7,11 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "sop4py"
-version = "2.0.0"
+version = "2.0.1"
 authors = [
     { name="Gerardo Recinto", email="gerardorecinto@yahoo.com" },
 ]
-description = "Scalable Objects Persistence for Python."
+description = "Scalable Objects Persistence for Python. Beta 3 Release"
 readme = "README.md"
 requires-python = ">=3.7"
 classifiers = [
@@ -19,18 +19,7 @@ classifiers = [
     "License :: OSI Approved :: MIT License",
     "Operating System :: OS Independent",
 ]
-dependencies = [
-    "libjsondb_amd64darwin.dylib",
-    "libjsondb_amd64darwin.h",
-    "libjsondb_arm64darwin.dylib",
-    "libjsondb_arm64darwin.h",
-    "libjsondb_amd64linux.so",
-    "libjsondb_amd64linux.h",
-    "libjsondb_arm64linux.so",
-    "libjsondb_arm64linux.h",
-    "libjsondb_amd64windows.dll",
-    "libjsondb_amd64windows.h",
-]
+dependencies = []
 
 # build: python3 -m build
 # upload to pypi using twine: python3 -m twine upload dist/*

{sop4py-2.0.0 → sop4py-2.0.1}/sop/btree.py

@@ -1,15 +1,15 @@
 import json
 import uuid
 import logging
-import call_go
-import context
+from . import call_go
+from . import context
 
 logger = logging.getLogger(__name__)
 
 from typing import TypeVar, Generic, Type
 from dataclasses import dataclass, asdict
 
-from transaction import Transaction, TransactionError
+from . import transaction
 
 # Define TypeVars 'TK' & 'TV' to represent Key & Value generic types.
 TK = TypeVar("TK")
@@ -19,13 +19,11 @@ from datetime import timedelta
 
 from enum import Enum, auto
 
-
 class ValueDataSize(Enum):
     Small = 0
     Medium = 1
     Big = 2
 
-
 class PagingDirection(Enum):
     Forward = 0
     Backward = 1
@@ -126,8 +124,8 @@ class Item(Generic[TK, TV]):
     id: str = str(uuid.UUID(int=0))
 
 
-class BtreeError(TransactionError):
-    """Exception for Btree-related errors, 'is derived from TransactionError."""
+class BtreeError(transaction.TransactionError):
+    """Exception for Btree-related errors, 'is derived from transaction.TransactionError."""
 
     pass
 
@@ -186,7 +184,7 @@ class Btree(Generic[TK, TV]):
         cls: Type["Btree[TK,TV]"],
         ctx: context.Context,
         options: BtreeOptions,
-        trans: Transaction,
+        trans: transaction.Transaction,
         index_spec: IndexSpecification = None,
     ) -> "Btree[TK,TV]":
         """Create a new B-tree store in the backend storage with the options specified then returns an instance
@@ -196,7 +194,7 @@ class Btree(Generic[TK, TV]):
             cls (Type["Btree[TK,TV]"]): Supports generics for Key (TK) & Value (TV) pair.
             ctx (context.Context): context.Context object, useful for telling SOP in the backend the ID of the context for use in calls.
             options (BtreeOptions): _description_
-            trans (Transaction): instance of a Transaction that the B-tree store to be opened belongs.
+            trans (transaction.Transaction): instance of a transaction.Transaction that the B-tree store to be opened belongs.
             index_spec (IndexSpecification, optional): Defaults to None.
 
         Raises:
@@ -226,14 +224,14 @@ class Btree(Generic[TK, TV]):
 
     @classmethod
     def open(
-        cls: Type["Btree[TK,TV]"], ctx: context.Context, name: str, trans: Transaction
+        cls: Type["Btree[TK,TV]"], ctx: context.Context, name: str, trans: transaction.Transaction
     ) -> "Btree[TK,TV]":
         """Open an existing B-tree store on the backend and returns a B-tree manager that can allow code to do operations on it.
         Args:
             cls (Type["Btree[TK,TV]"]): Supports generics for Key (TK) & Value (TV) pair.
             ctx (context.Context): context.Context object, useful for telling SOP in the backend the ID of the context for use in calls.
             name (str): Name of the B-tree store to open.
-            trans (Transaction): instance of a Transaction that the B-tree store to be opened belongs.
+            trans (transaction.Transaction): instance of a transaction.Transaction that the B-tree store to be opened belongs.
 
         Raises:
             BtreeError: error message generated when calling different methods of the B-tree.

{sop4py-2.0.0 → sop4py-2.0.1}/sop/call_go.py

@@ -20,7 +20,9 @@ else:
 
 # Load the shared library
 try:
-    lib = ctypes.CDLL(f"./libjsondb_{ext}")
+    script_dir = os.path.dirname(__file__) # Get directory of the current script
+    library_path = os.path.join(script_dir, f"libjsondb_{ext}") # Adjust filename
+    lib = ctypes.CDLL(library_path)
 except OSError as e:
     print(f"Error loading library: {e}")
     print("Ensure 'libjsondb_<arch><os>.so' (or .dll/.dylib) is in the same directory.")

{sop4py-2.0.0 → sop4py-2.0.1}/sop/context.py

@@ -1,4 +1,4 @@
-import call_go
+from . import call_go
 
 
 class Context:

{sop4py-2.0.0 → sop4py-2.0.1}/sop/redis.py

@@ -1,5 +1,4 @@
-import ctypes
-import call_go
+from . import call_go
 
 
 class RedisOptions:

{sop4py-2.0.0 → sop4py-2.0.1}/sop/transaction.py

@@ -1,7 +1,7 @@
 import json
-import call_go
+from . import call_go
 import uuid
-import context
+from . import context
 
 from enum import Enum
 from dataclasses import dataclass, asdict

{sop4py-2.0.0 → sop4py-2.0.1/sop4py.egg-info}/PKG-INFO

@@ -1,27 +1,29 @@
 Metadata-Version: 2.4
 Name: sop4py
-Version: 2.0.0
-Summary: Scalable Objects Persistence for Python.
+Version: 2.0.1
+Summary: Scalable Objects Persistence for Python. Beta 3 Release
 Author-email: Gerardo Recinto <gerardorecinto@yahoo.com>
 Classifier: Programming Language :: Python :: 3
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
 Requires-Python: >=3.7
 Description-Content-Type: text/markdown
-Requires-Dist: libjsondb_amd64darwin.dylib
-Requires-Dist: libjsondb_amd64darwin.h
-Requires-Dist: libjsondb_arm64darwin.dylib
-Requires-Dist: libjsondb_arm64darwin.h
-Requires-Dist: libjsondb_amd64linux.so
-Requires-Dist: libjsondb_amd64linux.h
-Requires-Dist: libjsondb_arm64linux.so
-Requires-Dist: libjsondb_arm64linux.h
-Requires-Dist: libjsondb_amd64windows.dll
-Requires-Dist: libjsondb_amd64windows.h
 
 # What is SOP?
 
-Scalable Objects Persistence (SOP) is a raw storage engine that bakes together a set of storage related features & algorithms in order to provide the most efficient & reliable (ACID attributes of transactions) technique (known) of storage management and rich search, as it brings to the application, the raw muscle of "raw storage", direct IO communications w/ disk drives. In a code library form factor.
+Scalable Objects Persistence (SOP) is a raw storage engine that bakes together a set of storage related features & algorithms in order to provide the most efficient & reliable (ACID attributes of transactions) technique (known) of storage management and rich search, as it brings to the application, the raw muscle of "raw storage", direct IO operations w/ disk drives. In a code library form factor.
+
+Other "key advances" in database technology available in this SOP release:
+* Serverless (or all servers!) operations mode in the cluster, i.e. - your applications that use SOP library are server-less
+* Uses a new storage & L1/L2 caching strategy that is ground breaking in performance & efficiency
+* New superfast realtime Orchestration engine fit for database transactions
+* Support for small, medium to large/very large (multi-GBs/TB) data management
+* Sports advanced/efficient/high tolerance software based (via Erasure Coding) replication
+* Horizontal & Vertical scaling in storage and cluster processes
+* New database storage strategy that uses segment files which avoids having to manage a huge file, resulting in higher IO efficiency & file system/disk drive friendly (medium sized) data files
+* Built-in data caching, your application data can be cached automatically via config setting. No need to write special code to cache certain data set in Redis, for example. SOP can provide that if configured
+* Host your applications across platforms, e.g. - microservice cluster running in Linux, another cluster or instance running in Windows, and all SOPs inter-operating with one another seamlessly and data stored in same set of disk drives. Freedom to use popular hardware architecture & OS of your choice(s)!
+* Unlimited B-trees, limited only by your hardware resources. Each B-tree store, as the name implies, is a B-tree serving super-fast, sorted by Key (Key & Value pair) data sets
 
 # SOP supported Hardware/OS
 SOP supports popular architectures & Operating Systems such as Linux, Darwin & Microsoft Windows, in both ARM64 & AMD64 architectures. For Windows, only AMD64 is supported since it is the only architecture Windows is available in.
@@ -42,6 +44,7 @@ Following steps outlines how to use the Scalable Objects Persistence code librar
 * Follow standard Python package import and start coding to use the SOP for Python code library for data management. Import the sop package in your python code file.
 * Specify Home base folders where Store info & Registry data files will be stored.
 * Specify Erasure Coding (EC) configuration details which will be used by SOP's EC based replication.
+* Open the global Redis connection
 * Create a transaction
 * Begin a transaction
 * Create a new B-tree, or Open an existing B-tree
@@ -51,9 +54,10 @@ Following steps outlines how to use the Scalable Objects Persistence code librar
 Below is an example code black for illustrating the above steps. For other SOP B-tree examples, you can checkout the code in the unit tests test_btree.py & test_btree_idx.py files that comes w/ the SOP package you downloaded from pypi.
 
 ```
-import sop.transaction
-import sop.btree
-import sop.context
+from sop import transaction
+from sop import btree
+from sop import context
+from sop import redis
 
 stores_folders = ("/disk1", "/disk2")
 ec = {
@@ -76,8 +80,8 @@ ec = {
 # Transaction Options (to).
 to = transaction.TransationOptions(
     transaction.TransactionMode.ForWriting.value,
-    # commit timeout of 5mins
-    5,
+    # commit timeout of 15mins
+    15,
     # Min Registry hash mod value is 250, you can specify higher value like 1000. A 250 hashmod
     # will use 1MB sized file segments. Good for demo, but for Prod, perhaps a bigger value is better.
     transaction.MIN_HASH_MOD_VALUE,
@@ -90,9 +94,10 @@ to = transaction.TransationOptions(
 # Context object.
 ctx = context.Context()
 
-# initialize/open SOP global Redis connection
-ro = RedisOptions()
-Redis.open_connection(ro)
+# initialize/open SOP global Redis connection. You can specify your Redis cluster host address(es) & port, etc
+# but defaults to localhost and default Redis port # if none is specified.
+ro = redis.RedisOptions()
+redis.Redis.open_connection(ro)
 
 t = transaction.Transaction(ctx, to)
 t.begin()
@@ -103,7 +108,9 @@ cache = btree.CacheConfig()
 bo = btree.BtreeOptions("barstoreec", True, cache_config=cache)
 bo.set_value_data_size(btree.ValueDataSize.Small)
 
-# create the new "barstoreec" b-tree store.
+# create the new "barstoreec" b-tree store. Once created, you can just use the "open" method. Perhaps
+# you can have a code set for creating B-trees like "admin only" script. Then all other app code uses
+# the "open" method.
 b3 = btree.Btree.new(ctx, bo, t)
 
 # Since we've specified Native data type = True in BtreeOptions, we can use "integer" values as Key.
@@ -111,11 +118,12 @@ l = [
     btree.Item(1, "foo"),
 ]
 
-# Add Item to the B-tree,
+# Add Item to the B-tree.
 b3.add(ctx, l)
 
 # Commit the transaction to finalize the new B-tree (store) change.
 t.commit(ctx)
+print("ended.")
 ```
 
 # SOP in Github

{sop4py-2.0.0 → sop4py-2.0.1}/sop4py.egg-info/SOURCES.txt

@@ -22,5 +22,4 @@ sop/transaction.py
 sop4py.egg-info/PKG-INFO
 sop4py.egg-info/SOURCES.txt
 sop4py.egg-info/dependency_links.txt
-sop4py.egg-info/requires.txt
 sop4py.egg-info/top_level.txt

sop4py-2.0.0/sop4py.egg-info/requires.txt

@@ -1,10 +0,0 @@
-libjsondb_amd64darwin.dylib
-libjsondb_amd64darwin.h
-libjsondb_arm64darwin.dylib
-libjsondb_arm64darwin.h
-libjsondb_amd64linux.so
-libjsondb_amd64linux.h
-libjsondb_arm64linux.so
-libjsondb_arm64linux.h
-libjsondb_amd64windows.dll
-libjsondb_amd64windows.h