remove kvstore, mapper, tables and queue

docs/api/python.rst

@@ -7,7 +7,7 @@ Resources
 ------------------------------------
 Resources are the Runhouse abstraction for objects that can be saved, shared, and reused.
 This includes both compute abstractions (clusters, functions, packages, environments) and
-data abstractions (blobs, folders, tables).
+data abstractions (files, blobs, folders).
 
 .. toctree::
    :maxdepth: 1
@@ -48,15 +48,10 @@ and rich debugging and accessibility interfaces built-in.
 
     python/module
 
-.. toctree::
-    :maxdepth: 1
-
-    python/mapper
-
 
 Data Abstractions
 ------------------------------------
-The Folder, Table, Blob, and File APIs provide a simple interface for storing, recalling, and moving data between
+The Folder, Blob, and File APIs provide a simple interface for storing, recalling, and moving data between
 the user's laptop, remote compute, cloud storage, and specialized storage (e.g. data warehouses).
 They provide least-common-denominator APIs across providers, allowing users to easily specify the actions
 they want to take on the data without needed to dig into provider-specific APIs. We'd like to extend this
@@ -67,12 +62,6 @@ to other data concepts in the future, like kv-stores, time-series, vector and gr
 
    python/folder
 
-
-.. toctree::
-   :maxdepth: 1
-
-   python/table
-
 .. toctree::
    :maxdepth: 1
 

docs/api/python/run.rst

@@ -64,7 +64,7 @@ A Run may contain some (or all) of these core components:
 - **Downstream dependencies**: Runhouse artifacts saved by the Run.
 
 .. note::
-    Artifacts represent any Runhouse primitive (e.g. :ref:`Blob`, :ref:`Function`, :ref:`Table`, etc.) that is
+    Artifacts represent any Runhouse primitive (e.g. :ref:`Blob`, :ref:`Function`, etc.) that is
     loaded or saved by the Run.
 
 

docs/architecture.rst

@@ -8,7 +8,7 @@ Runhouse Resources
 
 Resources are the Runhouse primitive for objects that can be saved, shared, and reused. This can be split
 into compute resources (clusters, functions, modules, environments, and runs) and data resources
-(folder, table, blob, etc).
+(folder, blob, etc).
 
 Compute
 -------
@@ -41,8 +41,6 @@ dig into provider-specific APIs.
 * **Folder**: Represents a specified location (could be local, remote, or file storage), for managing where various
   Runhouse resources live.
 
-* **Table**: Provides convenient APIs for writing, partitioning, fetch, and stream various data types.
-
 * **Blob**: Represents a data object stored in a particular system.
 
 * **File**: Represents a file object stored in a particular system.

runhouse/__init__.py

@@ -2,7 +2,6 @@
 from runhouse.resources.blobs import blob, Blob, file, File
 from runhouse.resources.envs import conda_env, CondaEnv, env, Env
 from runhouse.resources.folders import Folder, folder, GCSFolder, S3Folder
-from runhouse.resources.functionals.mapper import Mapper, mapper
 from runhouse.resources.functions.aws_lambda import LambdaFunction
 from runhouse.resources.functions.aws_lambda_factory import aws_lambda_fn
 from runhouse.resources.functions.function import Function
@@ -19,14 +18,11 @@
 
 # WARNING: Any built-in module that is imported here must be capitalized followed by all lowercase, or we will
 # will not find the module class when attempting to reconstruct it from a config.
-from runhouse.resources.kvstores.kvstore import Kvstore
 from runhouse.resources.module import Module, module
 from runhouse.resources.packages import git_package, GitPackage, package, Package
 from runhouse.resources.provenance import capture_stdout, Run, run, RunStatus, RunType
-from runhouse.resources.queues import Queue
 from runhouse.resources.resource import Resource
 from runhouse.resources.secrets import provider_secret, ProviderSecret, Secret, secret
-from runhouse.resources.tables import Table, table
 
 from runhouse.rns.top_level_rns_fns import (
     as_caller,