This is an automated email from the ASF dual-hosted git repository.
alamb pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion.git
The following commit(s) were added to refs/heads/main by this push:
new e34dd7651f fix ExecutionContext to SessionContext (#7903)
e34dd7651f is described below
commit e34dd7651fc3e2cc80f87e8bfaf0d98ec1312195
Author: ZENOTME <[email protected]>
AuthorDate: Mon Oct 23 21:17:02 2023 +0800
fix ExecutionContext to SessionContext (#7903)
Co-authored-by: ZENOTME <[email protected]>
---
docs/source/library-user-guide/custom-table-providers.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/source/library-user-guide/custom-table-providers.md
b/docs/source/library-user-guide/custom-table-providers.md
index 2de4b1ba05..ca0e9de779 100644
--- a/docs/source/library-user-guide/custom-table-providers.md
+++ b/docs/source/library-user-guide/custom-table-providers.md
@@ -139,10 +139,10 @@ For filters that can be pushed down, they'll be passed to
the `scan` method as t
## Using the Custom Table Provider
-In order to use the custom table provider, we need to register it with
DataFusion. This is done by creating a `TableProvider` and registering it with
the `ExecutionContext`.
+In order to use the custom table provider, we need to register it with
DataFusion. This is done by creating a `TableProvider` and registering it with
the `SessionContext`.
```rust
-let mut ctx = ExecutionContext::new();
+let mut ctx = SessionContext::new();
let custom_table_provider = CustomDataSource::new();
ctx.register_table("custom_table", Arc::new(custom_table_provider));
@@ -160,7 +160,7 @@ To recap, in order to implement a custom table provider,
you need to:
1. Implement the `TableProvider` trait
2. Implement the `ExecutionPlan` trait
-3. Register the `TableProvider` with the `ExecutionContext`
+3. Register the `TableProvider` with the `SessionContext`
## Next Steps
