update redirected links

colleenmcginnis · colleenmcginnis · commit 17811e65df0f · 2025-03-19T20:09:02.000-05:00
diff --git a/docs/reference/apache-spark-support.md b/docs/reference/apache-spark-support.md
@@ -1374,7 +1374,7 @@ The connector translates the query into:
 }
 ```
 
-Further more, the pushdown filters can work on `analyzed` terms (the default) or can be configured to be *strict* and provide `exact` matches (work only on `not-analyzed` fields). Unless one manually specifies the mapping, it is highly recommended to leave the defaults as they are.  This and other topics are discussed at length in the {{es}} [Reference Documentation](elasticsearch://reference/query-languages/query-dsl-term-query.md).
+Further more, the pushdown filters can work on `analyzed` terms (the default) or can be configured to be *strict* and provide `exact` matches (work only on `not-analyzed` fields). Unless one manually specifies the mapping, it is highly recommended to leave the defaults as they are.  This and other topics are discussed at length in the {{es}} [Reference Documentation](elasticsearch://reference/query-languages/query-dsl/query-dsl-term-query.md).
 
 Note that `double.filtering`, available since elasticsearch-hadoop 2.2 for Spark 1.6 or higher, allows filters that are already pushed down to {{es}} to be processed/evaluated by Spark as well (default) or not. Turning this feature off, especially when dealing with large data sizes speed things up. However one should pay attention to the semantics as turning this off, might return different results (depending on how the data is indexed, `analyzed` vs `not_analyzed`). In general, when turning *strict* on, one can disable `double.filtering` as well.
 

Original file line number	Diff line number	Diff line change
`@@ -1374,7 +1374,7 @@ The connector translates the query into:`
`1374`	`1374`	`}`
`1375`	`1375`	```
`1376`	`1376`
`1377`		-Further more, the pushdown filters can work on `analyzed` terms (the default) or can be configured to be strict and provide `exact` matches (work only on `not-analyzed` fields). Unless one manually specifies the mapping, it is highly recommended to leave the defaults as they are. This and other topics are discussed at length in the {{es}} [Reference Documentation](elasticsearch://reference/query-languages/query-dsl-term-query.md).
	`1377`	+Further more, the pushdown filters can work on `analyzed` terms (the default) or can be configured to be strict and provide `exact` matches (work only on `not-analyzed` fields). Unless one manually specifies the mapping, it is highly recommended to leave the defaults as they are. This and other topics are discussed at length in the {{es}} [Reference Documentation](elasticsearch://reference/query-languages/query-dsl/query-dsl-term-query.md).
`1378`	`1378`
`1379`	`1379`	Note that `double.filtering`, available since elasticsearch-hadoop 2.2 for Spark 1.6 or higher, allows filters that are already pushed down to {{es}} to be processed/evaluated by Spark as well (default) or not. Turning this feature off, especially when dealing with large data sizes speed things up. However one should pay attention to the semantics as turning this off, might return different results (depending on how the data is indexed, `analyzed` vs `not_analyzed`). In general, when turning strict on, one can disable `double.filtering` as well.
`1380`	`1380`