DIRECTED_QUERIES
Returns information about directed queries.
	Returns information about directed queries.
| Column Name | Data Type | Description | 
|---|---|---|
| QUERY_NAME | VARCHAR | Directed query's unique identifier, used by statements such as ACTIVATE DIRECTED QUERY. How this identifier is set depends on how it was created: 
 where: 
 | 
| IS_ACTIVE | BOOLEAN | Whether the directed query is active | 
| VERTICA_VERSION | VARCHAR | Vertica version installed when this directed query was created. | 
| COMMENT | VARCHAR | User-supplied or optimizer-generated comment on a directed query, up to 128 characters. | 
| SAVE_PLANS_VERSION | INTEGER | One of the following: 
 | 
| USERNAME | VARCHAR | User that created this directed query. | 
| CREATION_DATE | VARCHAR | When the directed query was created. | 
| SINCE_DATE | VARCHAR | Populated by SAVE_PLANS-generated directed queries, the earliest timestamp of input queries eligible to be saved as directed queries. | 
| INPUT_QUERY | VARCHAR | Input query associated with this directed query. Multiple directed queries can map to the same input query. | 
| ANNOTATED_QUERY | VARCHAR | Query with embedded hints that was paired with the input query of this directed query, where the hints encapsulated the query plan saved with CREATE DIRECTED QUERY. | 
| DIGEST | INTEGER | Hash of saved query plan data, used by the optimizer to map identical input queries to the same active directed query. | 
Privileges
SuperuserTruncated query results
Query results for the fields INPUT_QUERY and ANNOTATED_QUERY are truncated after ~32K characters. You can get the full content of both fields in two ways:
- 
Use the statement GET DIRECTED QUERY. 
- 
Use EXPORT_CATALOG to export directed queries.