Update JSONPath documentation to reflect changes (#397)

in version 1.3.4

Author: zoltanbedi

website/docs/jsonpath.md

@@ -23,6 +23,16 @@ For more information on the supported syntax, refer to the [project page](https:
 
 ## Filters
 
+:::note From version 1.3.4 filters are not supported anymore.
+
+If your dashboards currently rely on JSONPath queries containing subexpressions, there are a few potential migration paths:
+
+1. For simple queries that use subexpressions for indexing/slicing, it may be possible to rewrite the query without a subexpressions for instance `[(@.length-1)]` can also be represented as `[:-1]`.
+2. For more complex queries, we suggest switching to the [`jsonata` language](http://docs.jsonata.org/simple), which the plugin also supports. This language has similar features to JSONPath, including support for filter expressions (called “predicates” in the documentation).
+3. If changing your existing queries isn’t feasible, the community plugin [“Infinity”](https://grafana.com/grafana/plugins/yesoreyeram-infinity-datasource/) supports JSONPath expressions, including filters and subexpressions if used with the `backend` parser option. Please note that Infinity is community supported plugin.
+
+:::
+
 Filters let you query elements based on a logical expression.
 
 For example, to query the titles of the books that cost more than 10:

website/docs/query-editor.md

@@ -42,16 +42,10 @@ In the following example, the `name` property is present in both objects, but `v
 In the example below, you can see a couple of expressions and their results for the JSON structure in the previous example. Since JSONPath expressions are evaluated individually, Grafana can't tell which version that was missing.
 
 | Expression              | Result                         |
-|-------------------------|--------------------------------|
+| ----------------------- | ------------------------------ |
 | `$.services[*].name`    | `["order-api", "billing-api"]` |
 | `$.services[*].version` | `["1"]`                        |
 
-Depending on your use case, you can use a filter expression to only return items that contain a version:
-
-```json
-$.services[?(@.version)].name
-```
-
 ### Path
 
 ![Path](../static/img/editor-path.png)