You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check and update partitions list in metastore. There are three modes available:
@@ -1024,6 +1028,9 @@ The following procedures are available:
1024
1028
file system paths to use lowercase (e.g. ``col_x=SomeValue``). Partitions on the file system
1025
1029
not conforming to this convention are ignored, unless the argument is set to ``false``.
1026
1030
1031
+
Invalidate Directory List Cache
1032
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1033
+
1027
1034
* ``system.invalidate_directory_list_cache()``
1028
1035
1029
1036
Flush full directory list cache.
@@ -1032,6 +1039,9 @@ The following procedures are available:
1032
1039
1033
1040
Invalidate directory list cache for specified directory_path.
1034
1041
1042
+
Invalidate Metastore Cache
1043
+
^^^^^^^^^^^^^^^^^^^^^^^^^^
1044
+
1035
1045
* ``system.invalidate_metastore_cache()``
1036
1046
1037
1047
Invalidate all metastore caches.
@@ -1048,8 +1058,10 @@ The following procedures are available:
1048
1058
1049
1059
Invalidate all metastore cache entries linked to a specific partition.
1050
1060
1051
-
Note: To enable ``system.invalidate_metastore_cache`` procedure, please refer to the properties that
1052
-
apply to Hive Metastore and are listed in the `Metastore Configuration Properties`_ table.
1061
+
.. note::
1062
+
1063
+
To enable ``system.invalidate_metastore_cache`` procedure, ``hive.invalidate-metastore-cache-procedure-enabled`` must be set to ``true``.
1064
+
See the properties in `Metastore Configuration Properties`_ table for more information.
1053
1065
1054
1066
Extra Hidden Columns
1055
1067
--------------------
@@ -1064,22 +1076,22 @@ columns as a part of the query like any other columns of the table.
1064
1076
How to invalidate metastore cache?
1065
1077
----------------------------------
1066
1078
1067
-
The Hive connector exposes a procedure over JMX (``com.facebook.presto.hive.metastore.CachingHiveMetastore#flushCache``) to invalidate the metastore cache.
1068
-
You can call this procedure to invalidate the metastore cache by connecting via jconsole or jmxterm.
1079
+
Invalidating metastore cache is useful when the Hive metastore is updated outside of Presto and you want to make the changes visible to Presto immediately.
1080
+
There are a couple of ways for invalidating this cache and are listed below -
1069
1081
1070
-
This is useful when the Hive metastore is updated outside of Presto and you want to make the changes visible to Presto immediately.
1082
+
* The Hive connector exposes a procedure over JMX (``com.facebook.presto.hive.metastore.InMemoryCachingHiveMetastore#invalidateAll``) to invalidate the metastore cache. You can call this procedure to invalidate the metastore cache by connecting via jconsole or jmxterm. However, this procedure flushes the cache for all the tables in all the schemas.
1071
1083
1072
-
Currently, this procedure flushes the cache for all the tables in all the schemas. This is a known limitation and will be enhanced in the future.
1084
+
* The Hive connector exposes ``system.invalidate_metastore_cache`` procedure which enables users to invalidate the metastore cache completely or partially as per the requirement and can be invoked with various arguments. See `Invalidate Metastore Cache`_ for more information.
1073
1085
1074
1086
How to invalidate directory list cache?
1075
1087
---------------------------------------
1076
1088
1077
-
The Hive connector exposes a procedure over JMX (``com.facebook.presto.hive.HiveDirectoryLister#flushCache``) to invalidate the directory list cache.
1078
-
You can call this procedure to invalidate the directory list cache by connecting via jconsole or jmxterm.
1089
+
Invalidating directory list cache is useful when the files are added or deleted in the cache directory path and you want to make the changes visible to Presto immediately.
1090
+
There are a couple of ways for invalidating this cache and are listed below -
1079
1091
1080
-
This is useful when the files are added or deleted in the cache directory path and you want to make the changes visible to Presto immediately.
1092
+
* The Hive connector exposes a procedure over JMX (``com.facebook.presto.hive.CachingDirectoryLister#flushCache``) to invalidate the directory list cache. You can call this procedure to invalidate the directory list cache by connecting via jconsole or jmxterm. This procedure flushes all the cache entries.
1081
1093
1082
-
Currently, this procedure flushes all the cache entries. This is a known limitation and will be enhanced in the future.
1094
+
* The Hive connector exposes ``system.invalidate_directory_list_cache`` procedure which gives the flexibility to invalidate the list cache completely or partially as per the requirement and can be invoked in various ways. See `Invalidate Directory List Cache`_ for more information.
0 commit comments