CN107526746B

CN107526746B - Method and apparatus for managing document index

Info

Publication number: CN107526746B
Application number: CN201610457468.2A
Authority: CN
Inventors: 黄坤武; 张磊; 陈超; 刘晶晶; 代洪涛
Original assignee: EMC IP Holding Co LLC
Current assignee: EMC Corp
Priority date: 2016-06-22
Filing date: 2016-06-22
Publication date: 2020-11-24
Anticipated expiration: 2036-06-22
Also published as: CN107526746A; US20170371978A1; US11068536B2

Abstract

Embodiments of the present disclosure relate to a method and apparatus for managing document indexes. The method includes determining an independently updatable field in a plurality of documents, the independently updatable field including at least one item. The method also includes creating an index for the term in the independently updatable field, the index containing an identification of documents in the plurality of documents that include the term. In addition, the method includes chunking the identities of the documents in the index such that the index is updatable without modifying the identities of the documents.

Description

Method and apparatus for managing document index

Technical Field

Embodiments of the present disclosure generally relate to full-text indexing, and more particularly, to a method and apparatus for managing document indexing.

Background

In an enterprise search system, document content is always indexed along with other metadata fields of the document (attributes of the document such as topic, author, keywords, creation date, document category, comments, etc.). After a document has been added to the search system, the document may then be modified over and over again, e.g., the author may adjust the keywords, the reader will add comments, and the administrator may add tags. This type of frequent partial updates to a document is critical for applications that require a lot of collaboration like document review systems (the review state of a document can change frequently), like wikipedia (a lot of users can update different document properties).

Most current search systems are based on an inverted index (inverted index) architecture. The inverted index is used to store a mapping of where an item is stored in a document or collection of documents under the full-text index. Typically, in order to update an existing document, most search systems based on inverted indexes must delete old identifications corresponding to old versions of the document before adding new versions of the document. Further, after the new version of the document is added, a new identification is assigned to the new version of the document, and the item files corresponding to all items appearing in the new version of the document are modified, thereby rebuilding the inverted index. While from the end-user's perspective they make only a few subtle changes to the document, the underlying full-text index search system must perform much more complex operations to support subtle changes to the document. Sometimes frequent update operations on a document are much more heavily loaded than normal operations of adding a document, which causes the search system to be unable to handle the end user's operations while updating the document.

It is therefore very popular to enable an enterprise search system to quickly perform partial updates to a document. But limited by the inverted index, a number of attempts to partially update documents have not found application in the industry.

Disclosure of Invention

To address the above and other potential problems, embodiments of the present disclosure provide methods and apparatus for managing document indexes.

According to a first aspect of the present disclosure, a method of managing an index of documents is provided. The method includes determining an independently updatable field in a plurality of documents, the independently updatable field including at least one item. The method also includes creating an index for the term in the independently updatable field, the index containing an identification of documents in the plurality of documents that include the term. In addition, the method includes chunking the identities of the documents in the index such that the index is updatable without modifying the identities of the documents.

According to a second aspect of the present disclosure, there is provided an apparatus for managing document indexes. The apparatus comprises at least one processing unit and at least one memory. At least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. The instructions, when executed by the at least one processing unit, cause the apparatus to: determining an independently updatable field in a plurality of documents, the independently updatable field including at least one item; creating an index for the term in the independently updatable field, the index containing an identification of documents in the plurality of documents that include the term; and chunking the identities of the documents in the index such that the index is updateable without modifying the identities of the documents.

According to a third aspect of the present disclosure, a computer program product is provided. The computer program product is tangibly stored on a non-transitory computer-readable medium and includes machine-executable instructions. The machine executable instructions, when executed, cause the machine to perform any of the steps of the method described in accordance with the first aspect of the disclosure.

As will be understood from the following description, the present disclosure provides a solution for supporting independent updating of fields of documents in an index. The purpose of the present disclosure is to improve the speed and efficiency of partially updating documents, while keeping the normal indexing (adding and removing documents) and query capabilities the same as in conventional inverted indexes, thereby saving the indexing cost.

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the disclosure, nor is it intended to be used to limit the scope of the disclosure.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following more particular descriptions of exemplary embodiments of the disclosure as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts throughout the exemplary embodiments of the disclosure.

FIG. 1 shows a block diagram of an architecture 100 for managing an index of documents, according to an embodiment of the present disclosure;

FIG. 2A illustrates a schematic diagram of creating an index for items in two documents;

FIG. 2B illustrates a diagram of updating documents in the example shown in FIG. 2A according to a conventional inverted index;

FIG. 3 shows a flow diagram of a method 300 of managing an index of documents according to an embodiment of the present disclosure;

FIG. 4 illustrates an example of an index that organizes items using B-trees and file pointers;

FIG. 5A illustrates a schematic diagram of creating an index for items in two documents, according to an embodiment of the disclosure;

FIG. 5B illustrates a schematic diagram of updating a document in the example illustrated in FIG. 5A, according to an embodiment of the disclosure;

FIG. 6 shows a flow diagram of a method 600 of using an inverted index according to an embodiment of the present disclosure;

FIG. 7 shows a block diagram of an apparatus 700 for managing an index of documents according to an embodiment of the present disclosure; and

fig. 8 illustrates a schematic block diagram of an example device 800 that may be used to implement embodiments of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENT (S) OF INVENTION

Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

The term "include" and variations thereof as used herein is meant to be inclusive in an open-ended manner, i.e., "including but not limited to". Unless specifically stated otherwise, the term "or" means "and/or". The term "based on" means "based at least in part on". The terms "one example embodiment" and "one embodiment" mean "at least one example embodiment". The term "another embodiment" means "at least one additional embodiment". The terms "first," "second," and the like may refer to different or the same object. Other explicit and implicit definitions are also possible below.

In a search system, such as an enterprise search system, documents are automatically indexed, whether documents are added, removed, queried, or updated. In the case of having multiple metadata fields set for a document (attributes of the document such as topic, author, keyword, creation date, document category, comment, etc.), a large number of updates may be applied only to specified fields, i.e., only to a portion of the document, even to a very small portion of the document. In a search system, any update to a document requires the removal of the identity of the old document and the addition of the identity of the new document, although the new document differs only slightly from the old document. In the case where some metadata fields of a document are indexed to a full-text index, any update to the document triggers index reconstruction of the entire document (including all metadata fields of the document), which is wasteful in that the entire document (including all metadata fields of the document) needs to be processed over and over again, most of which is unnecessary.

To address, at least in part, the above problems, as well as other potential problems, example embodiments of the present disclosure propose a solution for managing document indexes. This scheme divides all fields of a document into two categories: independently updatable fields, and non-independently updatable fields, and storing an index of items in the independently updatable fields in a particular manner enables the index of items in the independently updatable fields to be updated without modifying the identity of the document.

FIG. 1 shows a block diagram of an architecture 100 for managing document indexing, according to an embodiment of the present disclosure. It should be understood that the description of the structure and function of the architecture 100 is for exemplary purposes only and is not intended to suggest any limitation as to the scope of the disclosure. Embodiments of the present disclosure may be embodied in different structures and/or functions.

As shown in fig. 1, the architecture 100 may include: search engine 110, application program interface 120, client 130, document index management module 140, document 150. Client 130 may send requests to search engine 110 to search (or query) for documents, add documents, remove documents, and update documents, among other things. The search engine 110 invokes the application program interface 120 to respond to requests from the client 130. For example, upon receiving a search request for a keyword from the client 130, the search engine 110 invokes the application program interface 120 to perform a search and provides the client 130 with search results that include a list of documents that contain the keyword.

The application program interface 120 implements functions of searching (or querying) documents, adding documents, removing documents, and updating documents, etc., by means of the document index management module 140. Document index management module 140 includes storage module 141, storage module 141 storing an index 1411 for a plurality of documents 150.

Document 150 of the plurality of documents indexed in architecture 100 is created to include field 151, and field 151 includes item 1511. Fields 151 are, for example, the content of the document, as well as metadata fields such as the subject matter, author, keywords, creation date, document category, comments, etc. of the document. Each entry 1511 in field 151 is, for example, each word contained by the field. By way of example, field 151 is the author of the document, "Li Ming", then this field 151 includes two items 1511: plum and Ming. In other words, an item may be understood as a single word.

The index 1411 stored in the storage module 141 includes a list of documents 150 in which each item 1511 appears. For example, the index 1411 may be represented as:

item- > list of document identifications

Wherein the document identification may be a number set for a document in the index, such as document 1, document 2, document 3, etc. For example, the index 1411 may be represented as:

term- > document 1, document 4, document 10, document 100, document 120

FIG. 2A shows a schematic diagram of creating an index 1411 for items in two documents. Therein, block 211 shows the contents of both documents, document 1 and document 2, i.e., the fields are the contents of the documents. Although only one field is shown here, in other embodiments, the document may include other fields such as subject matter, author, keywords, creation date, document category, comments, and the like. Block 215 shows an index 1411 created for the items in the content field that expresses the relationship of the items to the documents, where "document 1" and "document 2" are document identifications.

Alternatively, the index 1411 may be represented as:

list of term- > document identities (n)

Where n represents the frequency with which items appear in a particular document. Alternatively, the index 1411 may contain information about where items appear in the document. Where the index 1411 contains location information for terms, it may be extended from term queries to phrase queries.

Upon receiving a search (or query) request from the client 130 for a particular term 1511, the document index management module 140 provides the search engine 110 with a list of documents in which the particular term 1511 appears, according to the relationship of the terms and documents contained in the index 1411. In some embodiments, the searched documents may be ranked by the frequency with which the terms appear in the documents.

Upon receiving requests from the client 130 to add documents, remove documents, update documents, and the like, the document index management module 140 modifies the index 1411 stored in the storage module 141. In the conventional approach, the index 1411 is an inverted index. When a request to add a document is received, document index management module 140 assigns a document identification (e.g., document 100) to the document to be added and adds document 100 to index 1411. When a request to remove a document is received, the document index management module 140 deletes the identification of the document from the index 1411 or adds a deletion marker to the identification of the document in the index 1411.

FIG. 2B illustrates a diagram of updating documents in the example shown in FIG. 2A according to a conventional inverted index. Block 221 depicts making a partial modification to document 1, i.e., updating document 1; block 225 illustrates index 1411 after the document is updated. When a request to update a document (e.g., document 1) is received, in conventional approaches, document index management module 140 adds a delete marker to the identification of the old version of the document to be updated (e.g., document 1) in index 1411, assigns a new document identification (e.g., document 3) to the new version of the document to be updated, and adds document 3 to index 1411. In this case, as shown in fig. 2B, since the identification of the document changes (from document 1 to document 3), although only the document 1 is partially modified, the indexes of all items appearing in the documents 1 and 3 are modified, which seriously reduces the efficiency of updating the document. Moreover, if there are other fields than the content of the document, the index of the items in the other fields that have not changed all need to be modified due to the change in the identity of the document, which severely reduces the efficiency of updating the document.

The scheme for managing the document index according to the embodiment of the disclosure can improve the efficiency of updating the document under the condition of keeping the performances of searching (or querying), adding the document and removing the document.

Embodiments of the present disclosure will be described in further detail below with reference to fig. 3 to 7. FIG. 3 shows a flow diagram of a method 300 of managing an index of documents according to an embodiment of the present disclosure. For example, method 300 may be performed by document index management module 140 as shown in FIG. 1. It should be understood that method 300 may also include additional steps not shown and/or may omit steps shown, as the scope of the present disclosure is not limited in this respect.

The method 300 begins at step 310. In step 310, the document index management module 140 determines an independently updatable field in the plurality of documents 150, the independently updatable field including at least one term. In some embodiments, document index management module 140 may classify all fields 151 in plurality of documents 150 into two categories: independently updatable fields and non-independently updatable fields. In some embodiments, the independently updatable fields should be those that are relatively simple. For example, the contents of these fields should be rather short. That is, the number of entries of the independently updatable field is below a predetermined threshold number. For example, those fields for which the maximum possible number of entries does not exceed a few words may be determined to be independently updatable fields. As will be appreciated from the description below, this facilitates efficiency in the updating and maintenance of the index.

The document index management module 140 determines an independently updatable field from among a plurality of documents such that the number of items included in the independently updatable field is below a predetermined threshold, thereby ensuring efficiency in updating the documents. For example, the predetermined threshold is 10. As an example, a metadata field, such as an author of a document, may be determined to be an independently updatable field. Assuming the author of the document is "Li Ming," the independently updatable field includes two items: plum and Ming. Since the content of a document is typically long, the content of a document is generally classified as a non-independently updatable field. However, in the case where the content of the document includes only a few words (for example, 10 words or less), the content of the document may be determined as an independently updatable field.

Next, the method 300 proceeds to step 320. In step 320, the document index management module 140 creates an index 1411 for the items in the independently updatable fields. The index 1411 contains an identification of the documents in the plurality of documents that include the item. Thereafter, in step 330, the document index management module 140 chunks the identification of the documents in the index 1411 in the storage module 141 such that the index 1411 is updatable without modifying the identification of the documents. The identification of documents in the chunking store index 1411 may allow for rapid updates to the list of document identifications associated with the items. Several example implementations of the index 1411 and the manner in which it is stored are discussed below.

In some embodiments, document index management module 140 stores the identification of the documents in at least one node of the hierarchy, each node including an identification of at least a portion of the documents in the plurality of documents. For example, in some embodiments, the hierarchy includes an index tree. Examples of trees include, but are not limited to, B-trees, B + trees, B-trees, and B-trees, among others. The index 1411 for the items in the independently updatable fields may be organized in such a tree structure to enable fast location of the index 1411 and efficient updating of the independently updatable fields. In particular, in some embodiments, multiple levels of file pointers may be used to improve operating efficiency.

FIG. 4 illustrates an example of an index 1411 that uses B-trees and file pointers to organize items. Fig. 4 is based on document 1 and document 2 shown in block 211 in fig. 2A. Only three items in the B-tree organization are shown in fig. 4: "gold" 410, "bridge" 420, "is" 430, which are linked to the corresponding list of

document identifications

415, 425, and 435 using pointer 1411, pointer 2421, and pointer 3431, respectively.

Alternatively or additionally, in some embodiments, document index management module 140 stores the identification of the documents in at least one file chunk, each file chunk including an identification of at least a portion of the documents. Alternatively or additionally, in some embodiments, at least one file block is sequentially associated. The size of each file block may be predefined. The number of document identifications contained in each file block may be the same or different. The number of document identifications contained in each file block may be related to the storage space occupied by the document identification itself. For example, a document identification number 1 occupies fewer memory bits, while a document identification number 10000 occupies more memory. Thus, for a document identification with a smaller number, a file block may contain more such document identifications. For document identifications with larger numbers, a file block may contain fewer such document identifications. For example, the index 1411 of the entries in the independently updatable field is stored as:

the term- > [ document 1, document 4, document 10] - > [ document 100, document 120] wherein "[ ]" represents file chunks, each of which may store one or more document identifications; "- >" denotes a file pointer, and a plurality of file blocks are sequentially associated using the file pointer. In this way, it is possible to allow a certain document identification to be deleted from a certain file block or a certain document identification to be inserted into a certain file block. In addition, new file blocks may also be inserted into the list of file blocks. In the index 1411, the file blocks and the identification of the documents in the file blocks may be arranged in a particular order to facilitate quick location.

Further, it should be understood that the document index management module 140 creates an inverted index of multiple documents, i.e., an index as shown in FIGS. 2A and 2B, for items in fields other than independently updatable fields. The document index management module 140 creates an inverted index for the terms in the non-independently updatable fields in a conventional manner. In other words, the index of terms in the non-independently updatable fields is stored such that the identity of the documents in the index need to be modified in the event that the documents are updated.

FIG. 5A illustrates a schematic diagram of creating an index 1411 for items in two documents, according to an embodiment of the disclosure. Similar to block 211 in FIG. 2A, block 511 in FIG. 5A shows the contents of both document 1 and document 2, i.e., the fields are the contents of the documents. Although only one field is shown here, in other embodiments, the document may include other fields such as subject matter, author, keywords, creation date, document category, comments, and the like.

Block 515 in FIG. 5A is also similar to block 215 in FIG. 2A, the only difference being that block 515 in FIG. 5A illustrates the identification of the documents in the chunk store index 1411, where "[ ]" represents a file chunk. In fig. 5A, since there are only two documents, document 1 and document 2 are stored in one file block. Where a large number of documents are involved, there may be multiple file blocks.

The index 1411 of items in the independently updatable fields is not otherwise stored as a document level to ensure that the update application program interface 120 can update all occurrences of the index 1411. The solution can also be extended to support the ability to update all occurrences of the index 1411 in the event that the index 1411 is otherwise stored as a document level.

It is noted that while the index 1411 for items in independently updatable fields is stored differently than the inverted index for items in non-independently updatable fields, operations such as query fields, add fields, remove fields, update fields, etc. to the index 1411 are encapsulated by using the application program interface 120 such that the upper layer interface is the same as the application program interface of a traditional inverted index, and the search engine 110 can read and write to the index 1411 to keep the capabilities of other operations (e.g., query documents, add documents, remove documents, etc.) other than update documents the same as a traditional inverted index.

Specifically, the operation of updating the field is completed through an application program interface of a traditional reverse index; the operation of the independently updatable fields is accomplished by an application program interface 120 according to an embodiment of the present disclosure, the application program interface 120 encapsulating the operation of an index 1411 to the items in the independently updatable fields. Operations directed to independently updatable and non-independently updatable fields, respectively, may be controlled at the application program interface level.

A flow diagram of a method 600 of using an inverted index according to an embodiment of the present disclosure is described below with reference to fig. 6. It is understood that method 600 may be performed after method 300. At step 610, document index management module 140 receives a request from client 130 via search engine 110 to update an entry of an independently updatable field in a first document. In response to receiving such a request, document index management module 140 may modify the index of related items at step 620, while keeping the identity of the first document in the index unmodified. For purposes of example only, one specific example is considered below.

Assume that a user of client 130 enters a new author on the interface provided by search engine 110, where the author is determined to be an independently updatable field. In response to a request to update the "author" field, the document index management module 140 locates and modifies the index of the items in the "author" field, while keeping the identity of the document to which the "author" field belongs in the index unmodified, and keeping the inverted index of items other than the "author" field unmodified. The purpose of modifying the index of items is to delete old items in the index from the document identification and add to the index new items and document identifications relationships that did not exist before, instead of the traditional approach where new document identifications were added.

In some embodiments, the request involves removing an item from the independently updatable field, and modifying the index includes: the identity of the first document is deleted from the index of items. In some embodiments, deleting the identification of the first document from the index of items comprises deleting the index of items if only the identification of the first document is contained in the index of items. In some embodiments, the request involves adding an entry to the independently updatable field, and modifying the index includes: the identity of the first document is added to the corresponding block of the index. In some embodiments, adding the identification of the first document to the respective block of the index comprises creating an index of terms in the absence of an index of terms, wherein the index contains the identification of the first document.

FIG. 5B shows a schematic diagram of updating a document in the example shown in FIG. 5A, according to an embodiment of the disclosure. Block 521 depicts making a partial modification to document 1, i.e., updating document 1; block 525 shows index 1411 after the document is updated. It can be seen that in contrast to the example shown in FIG. 2B, when a request to update a document (e.g., document 1) is received, document index management module 140 keeps the identity of document 1 unmodified. Specifically, the identification of the updated document 1 is still "document 1". Thus, only the indexes of the deleted items (e.g., "marvelous") and added items (e.g., "falling" and "down") in the fields need to be modified.

For an item that is deleted (e.g., "marvelous"), modifying the index includes deleting the identity of document 1 from the index for the item "marvelous". For added terms (e.g., "falling" and "down"), modifying the index includes adding the identification of document 1 to the corresponding blocks of the index for the terms "falling" and "down". Also, the index of items other than the content field shown at block 521 need not be modified, e.g., the index of items in the author field need not be modified, benefiting from the identification of the document not being modified. Thus, the number of indexes of items that need to be modified is greatly reduced, thereby improving the efficiency of updating documents.

In the case where the index 1411 includes information of where the items appear in the document, modifying the index also includes modifying the location information of the items. In some embodiments, the items are associated with the corresponding location information by file pointers.

Furthermore, if there are a large number of documents in the system, the document identifications need to be compressed by storing a delta for each document identification. If a delta is stored for each document identification, the delta cannot be deleted when the document identification is deleted, but instead a deletion marker is added to it, indicating that the item's relationship to the document is removed and the document identification is still stored for later document identification references. When index merging is performed, actual deletion will occur. In this case, only the tag needs to be modified if an entry is first added to the field, then removed, and then added again.

FIG. 7 shows a block diagram of an apparatus 700 for managing document indexes according to an embodiment of the present disclosure. In some embodiments, apparatus 700 may be implemented at document index management module 140, for example. Alternatively, in some implementations, the apparatus 700 may be implemented directly as the document index management module 140 itself, i.e., the document index management module 140 may be implemented by the apparatus 700.

As shown in fig. 7, the apparatus 700 may include a determination module 710 configured to determine an independently updatable field in a plurality of documents, the independently updatable field including at least one item. The apparatus 700 may also include an index creation module 720 configured to create an index for an item in an independently updatable field, the index containing an identification of documents in the plurality of documents that include the item. Additionally, the apparatus 700 may also include a storage module 730 configured to store the identification of documents in the index in blocks such that the index is updatable without modifying the identification of documents.

In certain embodiments, the determination module 710 includes a determination unit configured to determine the independently updatable field from the plurality of documents such that a number of items included in the independently updatable field is below a predetermined threshold.

In certain embodiments, the storage module 730 includes a first storage unit configured to store an identification of a document in at least one file chunk, each file chunk including an identification of at least a portion of the document in the document. In certain embodiments, the storage module 730 further comprises an associating unit configured to sequentially associate at least one file block.

In certain embodiments, the storage module 730 includes a second storage unit configured to store an identification of a plurality of documents in at least one node of the hierarchy, each node including an identification of at least a portion of the plurality of documents. Wherein the hierarchical structure includes an index tree.

In some embodiments, apparatus 700 may also include other index creation modules configured to create an inverted index of a plurality of documents for items in fields other than independently updatable fields.

In some embodiments, the apparatus 700 may further comprise: a receiving module configured to receive a request to update an item of an independently updatable field in a first document; and an index modification module configured to modify the index of terms and to leave the identity of the first document in the index unmodified.

In some embodiments, the request involves removing an item from the independently updatable field, and the index modification module includes a deletion unit configured to delete the identification of the first document from the index of items.

In some embodiments, the request involves adding an entry to the independently updatable field, and the index modification module includes an adding unit configured to add the identification of the first document to a respective block of the index.

For clarity, certain optional modules of the apparatus 700 are not shown in fig. 7. However, it should be understood that the various features described above with reference to fig. 1, 3-6 apply equally to the apparatus 700. Furthermore, each module of the apparatus 700 may be a hardware module or a software module. For example, in some embodiments, apparatus 700 may be implemented in part or in whole using software and/or firmware, e.g., as a computer program product embodied on a computer-readable medium. Alternatively or additionally, the apparatus 700 may be implemented partly or entirely on hardware basis, e.g. as an Integrated Circuit (IC), an Application Specific Integrated Circuit (ASIC), a system on a chip (SOC), a Field Programmable Gate Array (FPGA), etc. The scope of the present disclosure is not limited in this respect.

Fig. 8 illustrates a schematic block diagram of an example device 800 that may be used to implement embodiments of the present disclosure. As shown, device 800 includes a Central Processing Unit (CPU)801 that may perform various appropriate actions and processes in accordance with computer program instructions stored in a Read Only Memory (ROM)802 or loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

A number of components in the device 800 are connected to the I/O interface 805, including: an input unit 806, such as a keyboard, a mouse, or the like; an output unit 807 such as various types of displays, speakers, and the like; a storage unit 808, such as a magnetic disk, optical disk, or the like; and a communication unit 809 such as a network card, modem, wireless communication transceiver, etc. The communication unit 809 allows the device 800 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

Various processes and processes described above, for example method 300, may be performed by processing unit 801. For example, in some embodiments, the method 300 may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 808. In some embodiments, part or all of the computer program can be loaded and/or installed onto device 800 via ROM 802 and/or communications unit 809. When the computer program is loaded into RAM 803 and executed by CPU 801, one or more steps of method 300 described above may be performed. Alternatively, the CPU 801 may also be configured to perform the method 300 described above in any other suitable manner (e.g., by means of firmware).

From the above description it can be seen that the solution of the present disclosure is applicable to the following applications: this application frequently updates documents partially (i.e., updates only a certain field of a document) and triggers indexing in a timely manner in a real-time full-text search system. Embodiments of the present disclosure improve the flexibility of updating simple metadata fields in large documents while keeping the ability to query, add, and remove documents unchanged by storing the identity of the documents in the index in blocks, so that the index is updateable without modifying the identity of the documents, for an index of items in independently updateable fields. With embodiments of the present disclosure, since the identity of the document need not be modified, only the index of the items in the independently updatable fields need to be modified (and only the index of the items in which changes occur, but not the index of the items in the independently updatable fields that do not change), without touching the index of the items in the fields that do not change. This will significantly reduce the indexing load, improve indexing performance, and in turn will improve system capacity.

The present disclosure may be methods, apparatus, systems, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for carrying out various aspects of the present disclosure.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry that can execute the computer-readable program instructions implements aspects of the present disclosure by utilizing the state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method of managing document indexing, comprising:

determining an independently updatable field in a plurality of documents, the independently updatable field comprising at least one item;

creating an index for an item in the independently updatable field, the index containing an identification of documents in the plurality of documents that include the item; and

chunking the identification of the documents in the index such that the index is updatable without modifying the identification of the documents,

wherein determining the independently updatable field comprises:

determining the independently updatable field from the plurality of documents such that a number of items included in the independently updatable field is below a predetermined threshold.

2. The method of claim 1, wherein chunking the identification of the documents in the index comprises:

storing the identification of the document in at least one file block, each file block including the identification of at least a portion of the document.

3. The method of claim 2, wherein chunking the identification of the documents in the index further comprises:

and sequentially associating the at least one file block.

4. The method of claim 1, wherein chunking the identification of the documents in the index comprises:

storing the identification of the document in at least one node of a hierarchy, each node comprising the identification of at least a portion of the plurality of documents.

5. The method of claim 4, wherein the hierarchy comprises an index tree.

6. The method of claim 1, further comprising:

creating an inverted index of the plurality of documents for items in fields other than the independently updatable fields.

7. The method of claim 1, further comprising:

receiving a request to update the item of the independently updatable field in a first document;

modifying the index of the items, keeping the identification of the first document in the index unmodified.

8. The method of claim 7, wherein the request involves removing the item from the independently updatable field, and modifying the index comprises:

deleting the identity of the first document from the index of items.

9. The method of claim 7, wherein the request involves adding the entry to the independently updatable field, and modifying the index comprises:

adding an identification of the first document to a corresponding block of the index.

10. An apparatus for managing document indexing, comprising:

at least one processing unit;

at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions when executed by the at least one processing unit, cause the apparatus to:

wherein determining the independently updatable field comprises:

11. The apparatus of claim 10, wherein chunking the identification of the documents in the index comprises:

12. The apparatus of claim 11, wherein chunking the identification of the documents in the index further comprises:

and sequentially associating the at least one file block.

13. The apparatus of claim 10, wherein chunking the identification of the documents in the index comprises:

14. The apparatus of claim 13, wherein the hierarchy comprises an index tree.

15. The apparatus of claim 10, the instructions, when executed by the at least one processing unit, further cause the apparatus to:

16. The apparatus of claim 10, the instructions, when executed by the at least one processing unit, further cause the apparatus to:

17. The apparatus of claim 16, wherein the request involves removing the item from the independently updatable field, and modifying the index comprises:

deleting the identity of the first document from the index of items.

18. The apparatus of claim 16, wherein the request involves adding the entry to the independently updatable field, and modifying the index comprises:

19. A computer-readable storage medium having stored thereon a computer program product, which when executed, causes a machine to perform the actions of the method of any of claims 1 to 9.