The output table has the default columns and any custom columns specified by the OutputColumns argument. The following table lists and describes the default and custom columns. In the following table, column name aliases are in parentheses (for example, the alias of the message_id column name is id). The function treats aliases as unique column names and processes them independently. Column names are case-insensitive.
The function creates the output table in memory, but you can direct it to a database table on disk or operate on it directly within the SQL-MapReduce framework.
SELECT sender, id, "to" FROM PSTParserAFS (ON ...)
Status | Column Name | Data Type | Description |
---|---|---|---|
Default | message_id (id) | VARCHAR | Unique identifier (ID) of the message (email), if assigned by the exchange server; blank otherwise. The exchange server does not assign IDs to messages in the Draft, Output, and Sent Items folders. To assign a unique global ID to each email message in the output table, concatenate the fields input_path and node_id. |
Default | sender (sender_name) | VARCHAR | Display name of the sender. |
Default | sender_email_address | VARCHAR | Email address of the sender. |
Default | recipients (recipient, recipient_name, recipients_name, recipient_names, recipients_names) | VARCHAR | Recipient names (from the message fields TO, CC, and BCC). |
Default | recipients_email_addresses (recipient_email_address) | VARCHAR | Recipient email addresses. |
Default | received_date (receive_date, date) | TIMESTAMP | Date and time when the message arrived at the recipient’s mailbox, in this format: yyyy-mm-dd hh:mm:ss For example, 2014-02-17 22:34:58. The date reflects the recipient’s time zone but does not contain time zone information. Time zone information is in the custom column received_date_timezone. |
Default | subject | VARCHAR | Subject of the message. |
Default | contents (body) | VARCHAR | Contents of the message (text). |
Custom | node_id (nodeid) | BIGINT | Node ID of the message, (unique within a PST file). (Within each PST file, each message is represented as a node.) |
Custom | input_path | VARCHAR | Input path location of this PST File on AFS. |
Custom | importance | INTEGER | Level of importance assigned to the Message object by the end user—0 (Low), 1 (Normal), or 2 (High). |
Custom | priority | INTEGER | Priority at which the client requested the message to be sent—0 (Normal) or 1 (Urgent). |
Custom | message_size | BIGINT | Message size on the server, in bytes. |
Custom | has_replied | VARCHAR | Whether the recipient replied to the message—'true' or 'false'. |
Custom | has_forwarded | VARCHAR | Whether the recipient forwarded the message—'true' or 'false'. |
Custom | is_flagged | VARCHAR | Whether the message has a due date—'true' or 'false'. |
Custom | received_date_timezone (timezone, receive_date_timezone, date_timezone) | VARCHAR | Time zone of the received_date value, displayed as an offset from GMT. For example, -0800 is 8 hours behind GMT. |
Custom | sent_date (send_date) | TIMESTAMP | Date and time when the sender sent the message, in this format:yyyy-mm-dd hh:mm:ss For example, 2014-02-17 22:34:58. The date reflects the sender’s time zone but does not contain time zone information. Time zone information is in the custom column sent_date_timezone. |
Custom | sent_date_timezone (send_date_timezone) | VARCHAR | Time zone of the sent_date value, displayed as an offset from GMT. For example, -0800 is 8 hours behind GMT. |
Custom | action_date | TIMESTAMP | Date and time when the recipient acted on the message, in this format:yyyy-mm-dd hh:mm:ss For example, 2014-02-17 22:34:58. The date reflects the recipient’s time zone but does not contain time zone information. Time zone information is in the custom column action_date_timezone. |
Custom | action_date_timezone | VARCHAR | Time zone of the action_date value, displayed as an offset from GMT. For example, -0800 is 8 hours behind GMT. |
Custom | folder (folder_name) | VARCHAR | Name of folder that contains the message (for example, 'Inbox' or 'Sent/2014/February'). |
Custom | sender_ip_address | VARCHAR | IP address of the sender system (for example, 10.10.143.10). |
Custom | to | VARCHAR | Names of the recipients in the message field TO. |
Custom | cc | VARCHAR | Names of the recipients in the message field CC. |
Custom | bcc | VARCHAR | Names of the recipients in the message field BCC. |
Custom | conversation_thread (thread) | VARCHAR | Conversation thread of the message—the subject of the first email in the thread, minus the strings 'Re:' and 'Fwd:'. |
Custom | number_of_attachments | INTEGER | Number of files attached to the message. |
Custom | attachment_size | BIGINT | Total size of files attached to the message, in bytes. |
Custom | list_of_attachments (attachments) | VARCHAR | Names of files attached to the message. |
Custom | message_type | VARCHAR | Type of the message (MessageClass). A Normal message has type IPM. Some other qualified types are:
For a list of all qualified message classes, and more information, see the Microsoft website. |