-
Notifications
You must be signed in to change notification settings - Fork 3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Describe support of CHAR/VARCHAR predicate pushdown
- Loading branch information
Showing
8 changed files
with
55 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
18 changes: 18 additions & 0 deletions
18
docs/src/main/sphinx/connector/no-inequality-pushdown-text-type.fragment
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
Predicate pushdown support | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
The connector does not support pushdown of inequality predicates, such as | ||
``!=``, ``>``, or ``BETWEEN``, on columns with | ||
:ref:`character string types <string-data-types>` like ``CHAR`` or ``VARCHAR``. | ||
Equality predicates, such as ``IN`` or ``=``, on columns with textual types are | ||
pushed down. This ensures correctness of results since the remote data source | ||
may sort strings differently than Trino. | ||
|
||
In the following example, the predicate of the first query is not pushed down | ||
since ``name`` is a column of type ``VARCHAR`` and ``>`` is an inequality | ||
predicate. The second query is pushed down. | ||
|
||
.. code-block:: sql | ||
|
||
SELECT * FROM nation WHERE name > 'CANADA'; | ||
SELECT * FROM nation WHERE name = 'CANADA'; |
15 changes: 15 additions & 0 deletions
15
docs/src/main/sphinx/connector/no-pushdown-text-type.fragment
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
Predicate pushdown support | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
The connector does not support pushdown of any predicates on columns with | ||
:ref:`textual types <string-data-types>` like ``CHAR`` or ``VARCHAR``. | ||
This ensures correctness of results since the data source may compare strings | ||
case-insensitively. | ||
|
||
In the following example, the predicate is not pushed down for either query | ||
since ``name`` is a column of type ``VARCHAR``: | ||
|
||
.. code-block:: sql | ||
|
||
SELECT * FROM nation WHERE name > 'CANADA'; | ||
SELECT * FROM nation WHERE name = 'CANADA'; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters