TableDataset¶
TableDataset is used to load and save data to tables using the Ibis framework.
kedro_datasets.ibis.TableDataset ¶
TableDataset(*, table_name, database=None, connection=None, load_args=None, save_args=None, metadata=None)
Bases: ConnectionMixin, AbstractDataset[Table, Table]
TableDataset loads/saves data from/to Ibis table expressions.
Examples:
Using the YAML API:
cars:
type: ibis.TableDataset
table_name: cars
connection:
backend: duckdb
database: company.db
save_args:
materialized: table
motorbikes:
type: ibis.TableDataset
table_name: motorbikes
connection:
backend: duckdb
database: company.db
Using the Python API:
>>> import ibis
>>> from kedro_datasets.ibis import TableDataset
>>>
>>> data = ibis.memtable({"col1": [1, 2], "col2": [4, 5], "col3": [5, 6]})
>>>
>>> dataset = TableDataset(
... table_name="test",
... connection={"backend": "duckdb", "database": tmp_path / "file.db"},
... save_args={"materialized": "table"},
... )
>>> dataset.save(data)
>>> reloaded = dataset.load()
>>> assert data.execute().equals(reloaded.execute())
TableDataset connects to the Ibis backend object constructed
from the connection configuration. The backend key provided in
the config can be any of the supported backends <https://ibis- project.org/install>. The remaining dictionary entries will be
passed as arguments to the underlying connect() method (e.g.
ibis.duckdb.connect() <https://ibis-project.org/backends/duckdb #ibis.duckdb.connect>).
The dataset establishes a connection to the relevant table for the execution
backend. Therefore, Ibis doesn't fetch data on load; all compute
is deferred until materialization, when the expression is saved.
In practice, this happens when another TableDataset instance
is saved, after running code defined across one more more nodes.
Parameters:
-
table_name(str) –The name of the table or view to read or create.
-
database(str | None, default:None) –The name of the database to read the table or view from or create the table or view in. If not passed, then the current database is used. Provide a tuple of strings (e.g.
("catalog", "database")) or a dotted string path (e.g."catalog.database") to reference a table or view in a multi-level table hierarchy. -
connection(dict[str, Any] | None, default:None) –Configuration for connecting to an Ibis backend. If not provided, connect to DuckDB in in-memory mode.
-
load_args(dict[str, Any] | None, default:None) –Additional arguments passed to the Ibis backend's
read_{file_format}method. -
save_args(dict[str, Any] | None, default:None) –Additional arguments passed to the Ibis backend's
create_{materialized}method. By default,ir.Tableobjects are materialized as views. To save a table using a different materialization strategy, supply a value formaterializedinsave_args. -
metadata(dict[str, Any] | None, default:None) –Any arbitrary metadata. This is ignored by Kedro, but may be consumed by users or external plugins.
Source code in kedro-datasets/kedro_datasets/ibis/table_dataset.py
70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 | |
DEFAULT_CONNECTION_CONFIG
class-attribute
¶
DEFAULT_CONNECTION_CONFIG = {'backend': 'duckdb', 'database': ':memory:'}
_connection_config
instance-attribute
¶
_connection_config = connection or DEFAULT_CONNECTION_CONFIG
_connect ¶
_connect()
Source code in kedro-datasets/kedro_datasets/ibis/table_dataset.py
137 138 139 140 141 142 | |
_describe ¶
_describe()
Source code in kedro-datasets/kedro_datasets/ibis/table_dataset.py
156 157 158 159 160 161 162 163 164 165 166 167 168 | |
_exists ¶
_exists()
Source code in kedro-datasets/kedro_datasets/ibis/table_dataset.py
170 171 172 173 | |
load ¶
load()
Source code in kedro-datasets/kedro_datasets/ibis/table_dataset.py
149 150 | |
save ¶
save(data)
Source code in kedro-datasets/kedro_datasets/ibis/table_dataset.py
152 153 154 | |