Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 New Initial Availability 6/27/2008 1.0 Major Revised and edited the technical content 12/12/2008 1.01 Editorial Revised and edited the technical content 7/13/2009 1.02 Major Revised and edited the technical content 8/28/2009 1.03 Editorial Revised and edited the technical content 11/6/2009 1.04 Editorial Revised and edited the technical content 2/19/2010 2.0 Editorial Revised and edited the technical content 3/31/2010 2.01 Editorial Revised and edited the technical content 4/30/2010 2.02 Editorial Revised and edited the technical content 6/7/2010 2.03 Editorial Revised and edited the technical content 6/29/2010 2.04 Editorial Changed language
and formatting in the technical content. 7/23/2010 2.05 Minor Clarified the meaning of the technical content. 9/27/2010 2.05 None No changes to the meaning, language, or formatting of the technical content. 11/15/2010 2.05 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 2.05 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 2.05 None No changes to the meaning, language, or formatting of the technical content. 6/10/2011 2.6 Minor Clarified the meaning of the technical content. 1/20/2012 2.7 Minor Clarified the
technical content. 11/18/2013 2.7 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 2.7 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 2.7 None No changes to the meaning, language, or formatting of the technical content. 7/31/2014 2.7 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 2.7 None No changes to the meaning, language, or formatting of the technical content. 6/23/2016 2.7 None No changes to the meaning, language, or formatting of the technical content.
... cTerms ... PID (4 bytes): A 32-bit unsigned integer that specifies the property identifier of the property whose statistics are enumerated in this structure. cDocIDs (4 A 32-bit unsigned integer that specifies the number of items that contain the property. cMinOcc (4 bytes): A 32-bit unsigned integer that specifies the lowest number of tokens in the property value across all items that contain the property. cMaxOcc (4 A 32-bit unsigned integer that specifies the highest number of tokens in the property value across all items that contain the property. cAvgOcc (4 bytes): A 32-bit unsigned integer that specifies the average number of tokens (rounded down) in the property value across all items that contain the property. Padding (4 The value for these 4 bytes is arbitrary, and MUST be ignored. cOcc (8 bytes): A 64-bit unsigned integer that specifies the total number of tokens in the property values across all items. cTerms (8 bytes): A 64-bit unsigned integer that specifies the number of distinct tokens in the property values across all items. Merge Process A merge process combines data from several source full-text index components into one target index component. There are two types of merge processes: shadow merge process and master merge process. The result of a shadow merge process is a shadow index component. The result of a master merge process is a new master index component and its corresponding AVDL backup file. If a master merge process is in progress and there is a master index component in the catalog, it MUST be one of the source full-text index components for the master merge. If a master index component participates in a merge process, it MUST be a master merge process. Merge Log File Format The merge log file format is an extension of the recoverable storage file format, as specified in section , and is used to store merge process information, as specified in section . A file that implements the merge log file format identifies the type of the merge process and the index components participating in the merge process: a master merge process creates and uses a master merge log file, and a shadow merge process creates and uses a shadow merge log file. It also identifies the AVDL files participating in the merge, if any.
Index A Active anchor text catalog 81 28 Anchor text catalog 80 11 66 101 B 86 88 25 19 62 18 19 19 22 22 23 17 17 18 25 C 66 203 121 31 31 113 75 70 115 57 83 85 27 Constants 12 12 Content index 58 Content index extension 57 59 55 57 54 56 90 Content file format ( 34, 54) 25 92 95 36 D Data file format 30 Details 18 17 18 72 104 76 113 58 117 22 59 95 E 59 116 25 Examples 101 88 86 113 115 85 83 90 92 95 104 113 117 95 116 114 116 82 92 113 109 118 116 115 114 106 114 55 116 57 F 11 File content 69 Full-text index