You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: presto-docs/src/main/sphinx/develop/connectors.rst
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,8 @@ you adapt your data source to the API expected by Presto, you can write
8
8
queries against this data.
9
9
10
10
ConnectorSplit
11
-
----------------
11
+
--------------
12
+
12
13
Instances of your connector splits.
13
14
14
15
The ``getNodeSelectionStrategy`` method indicates the node affinity
@@ -81,3 +82,14 @@ Given a split and a list of columns, the record set provider is
81
82
responsible for delivering data to the Presto execution engine.
82
83
It creates a ``RecordSet``, which in turn creates a ``RecordCursor``
83
84
that is used by Presto to read the column values for each row.
85
+
86
+
Node Selection Strategy
87
+
-----------------------
88
+
89
+
The node selection strategy is specified by a connector on each split. The possible values are:
90
+
91
+
* HARD_AFFINITY - The Presto runtime must schedule this split on the nodes specified on ``ConnectorSplit#getPreferredNodes``.
92
+
* SOFT_AFFINITY - The Presto runtime should prefer ``ConnectorSplit#getPreferredNodes`` nodes, but doesn't have to. Use this value primarily for caching.
93
+
* NO_PREFERENCE - No preference.
94
+
95
+
Use the ``node_selection_strategy`` session property in Hive and Iceberg to override this.
0 commit comments