You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2018/08/25 04:54:18 UTC
[GitHub] mistercrunch closed pull request #5720: Fix FAQ on filters
mistercrunch closed pull request #5720: Fix FAQ on filters
URL: https://github.com/apache/incubator-superset/pull/5720
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/docs/faq.rst b/docs/faq.rst
index 21e4e74905..63f4f72936 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -114,8 +114,8 @@ never be affected by any dashboard level filtering.
"filter_immune_slices": [324, 65, 92],
"expanded_slices": {},
"filter_immune_slice_fields": {
- "177": ["country_name", "__from", "__to"],
- "32": ["__from", "__to"]
+ "177": ["country_name", "__time_range"],
+ "32": ["__time_range"]
},
"timed_refresh_immune_slices": [324]
}
@@ -127,8 +127,8 @@ Now note the ``filter_immune_slice_fields`` key. This one allows you to
be more specific and define for a specific slice_id, which filter fields
should be disregarded.
-Note the use of the ``__from`` and ``__to`` keywords, those are reserved
-for dealing with the time boundary filtering mentioned above.
+Note the use of the ``__time_range`` keyword, which is reserved for dealing
+with the time boundary filtering mentioned above.
But what happens with filtering when dealing with slices coming from
different tables or databases? If the column name is shared, the filter will
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org