You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by ns...@apache.org on 2022/01/11 14:08:37 UTC

[ignite] branch master updated: IGNITE-16262 Remove the hash join index section from docs (#9725)

This is an automated email from the ASF dual-hosted git repository.

nsafonov pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ignite.git


The following commit(s) were added to refs/heads/master by this push:
     new 87baaa5  IGNITE-16262 Remove the hash join index section from docs (#9725)
87baaa5 is described below

commit 87baaa5c238a309786d2ee4b28d9c4eaa26be613
Author: Nikita Safonov <73...@users.noreply.github.com>
AuthorDate: Tue Jan 11 17:08:16 2022 +0300

    IGNITE-16262 Remove the hash join index section from docs (#9725)
---
 docs/_docs/SQL/distributed-joins.adoc | 61 +----------------------------------
 1 file changed, 1 insertion(+), 60 deletions(-)

diff --git a/docs/_docs/SQL/distributed-joins.adoc b/docs/_docs/SQL/distributed-joins.adoc
index 5394c3a..34d4037 100644
--- a/docs/_docs/SQL/distributed-joins.adoc
+++ b/docs/_docs/SQL/distributed-joins.adoc
@@ -48,63 +48,4 @@ If the join is done on the primary or affinity key, the nodes send unicast reque
 Enable the non-colocated mode of query execution by setting a JDBC/ODBC parameter or, if you use SQL API, by calling `SqlFieldsQuery.setDistributedJoins(true)`.
 
 WARNING: If you use a non-collocated join on a column from a link:data-modeling/data-partitioning#replicated[replicated table], the column must have an index.
-Otherwise, you will get an exception.
-
-
-
-== Hash Joins
-
-//tag::hash-join[]
-To boost performance of join queries, Ignite supports the https://en.wikipedia.org/wiki/Hash_join[hash join
-algorithm].
-Hash joins can be more efficient than nested loop joins for many scenarios, except when the probe side of the join is very small.
-However, hash joins can only be used with equi-joins, i.e. a type of join with equality comparison in the join-predicate.
-
-//end::hash-join[]
-
-To enforce the use of hash joins:
-
-. Use the `enforceJoinOrder` option:
-+
-[tabs]
---
-tab:Java API[]
-[source,java]
-----
-include::{javaCodeDir}/SqlAPI.java[tags=enforceJoinOrder,indent=0]
-----
-
-tab:JDBC[]
-[source,java]
-----
-Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
-
-// Open the JDBC connection.
-Connection conn = DriverManager.getConnection("jdbc:ignite:thin://127.0.0.1?enforceJoinOrder=true");
-----
-tab:C#/.NET[]
-[source,csharp]
-----
-include::code-snippets/dotnet/SqlJoinOrder.cs[tag=sqlJoinOrder,indent=0]
-----
-
-tab:C++[]
-[source,c++]
-----
-include::code-snippets/cpp/src/sql_join_order.cpp[tag=sql-join-order,indent=0]
-----
---
-
-. Specify `USE INDEX(HASH_JOIN_IDX)` on the table for which you want to create the hash-join index:
-+
---
-
-[source, sql]
-----
-SELECT * FROM TABLE_A, TABLE_B USE INDEX(HASH_JOIN_IDX) WHERE TABLE_A.column1 = TABLE_B.column2
-----
---
-
-
-
-
+Otherwise, you will get an exception.
\ No newline at end of file