JP6974665B1 - Search device, search method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To appropriately search information from two or more data sources and integrate the search results. SOLUTION: A source layer definition information having a source identifier and one or more source attribute definition information, a user layer definition information having a user table identifier and one or more user attribute definition information, and two or more each. A search device that searches for information by referring to a data dictionary 411 that has conversion rule definition information that is information for generating search instructions to be issued to a data source, acquiring search results, and creating integrated data. 4. With reference to the condition reception unit 121 that accepts the search condition and the data dictionary 411, a search command is generated for each of two or more data sources corresponding to the search condition, and the search result based on the search command is acquired. The above problem can be solved by the search device 4 including the search unit 432 that integrates the search results and acquires the integrated data, and the result output unit 441 that outputs the integrated data acquired by the search unit 432. [Selection diagram] FIG. 17

Description

The present invention relates to a search device or the like for retrieving information.

Conventionally, there has been a technique of a table join processing method in a relational database DBMS that executes a join operation of a plurality of tables at high speed with a small amount of resources (see Patent Document 1).

Japanese Unexamined Patent Publication No. 2000-172714

However, in the prior art, it has been difficult to appropriately search for information from two or more data sources and integrate the search results.

The search device of the first invention is information that defines each of two or more data sources including one or more records having one or more attribute values, and is a source identifier that is an identifier of the data source and an attribute of the data source. Source layer definition information that is information having one or more source attribute definition information including source attribute identifier that is an identifier, and one or more records that are search target tables based on search conditions and have one or more attribute values. Information that defines a user table, which is a table including Based on the layer definition information and the search condition, a search command to be issued to each of two or more data sources is generated, the search result corresponding to the search command is acquired, and the search condition is used using the two or more search results. It is a search device that searches for information by referring to the conversion rule definition information that is the information for creating the integrated data corresponding to the above, and the condition reception unit that accepts the search conditions for the user table, and the data. Refer to the dictionary to determine two or more data sources corresponding to the search conditions, generate a search command for each of the two or more data sources using the conversion rule definition information, and search results based on the search command. The search unit and the search unit that acquire the integrated data corresponding to the search conditions by integrating the search results corresponding to each of the two or more data sources by using the conversion rule definition information and the user layer definition information. It is a search device including a result output unit that outputs the acquired integrated data.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be integrated.

Further, the search device of the second invention defines a conversion view in which the conversion rule definition information is configured by using one or more data sources of two or more data sources with respect to the first invention. The transformation view information has one or more transformation view information, and the transformation view information is information that defines a transformation view that can include one or more records having one or more view attribute values, and includes a view attribute identifier corresponding to the view attribute value and a view attribute identifier. A user who has one or more view attribute definition information having a view attribute value source information for specifying a method of acquiring a view attribute value, and the user attribute definition information is a user who uses one or more view attribute values of one or more converted views. It has user attribute value source information that specifies the acquisition method of the attribute value, and the search unit acquires one or more user attribute identifiers included in the search condition, and the user attribute value source corresponding to each one or more user attribute identifiers. Source determination means and search conditions for acquiring information, acquiring one or more view attribute identifiers corresponding to user attribute value source information, and acquiring source identifiers corresponding to one or more view attribute identifiers from view attribute definition information. An instruction generation means that generates a search instruction for each data source identified by each of the two or more source identifiers acquired by the source determination means, and an instruction generation means for each of the two or more data sources, using the and view attribute value source information. Acquire integrated data that integrates the search results for each of two or more data sources acquired by the source search means using the source search means that acquires the search results based on the search command and the search conditions and user layer definition information. It is a search device provided with an integrated means for performing.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be integrated.

Further, in the search device of the third invention, with respect to the second invention, the view attribute value source information of any one or more view attribute value source information is of any of the two or more data sources. It has one or more attribute identifiers of the source attribute identifier or one or more of the view attribute identifiers of the conversion view, and an arithmetic expression or program identifier whose parameters are the attribute values corresponding to the one or more attribute identifiers. When the search unit acquires the view attribute value corresponding to the view attribute value source information, the search unit acquires the attribute value corresponding to each one or more attribute identifiers of the view attribute value source information from the data source or the transformed view. It is a search device that gives one or more acquired attribute values to a program identified by an arithmetic expression or a program identifier, executes the arithmetic expression or the program, and acquires a view attribute value.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be integrated.

Further, the search device of the fourth invention has two or more conversion view information and the conversion rule definition information is acquired based on two or more conversion view information with respect to the second or third invention. It has a join method identifier that specifies a method for combining two or more search results, and the integration means combines two or more search results according to the join method specified by the join method identifier and acquires integrated data. It is a search device.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be appropriately integrated.

Further, in the search device of the fifth invention, the conversion rule definition information is the combination method of two or more of the three or more combination method identifiers of "UNION", "CHOICE", and "LOOKUP" with respect to the fourth invention. Having one combination method identifier among the identifiers, "UNION" is one by grouping two or more search results by key items and aggregating two or more attribute values of non-key items. Information indicating that two or more search results are combined by the merge process constituting the record, and "CHOICE" is a key item included in one or more search results from two or more search results according to the priority order. "LOOKUP" is information indicating that two or more search results are combined by a selection process that selects an attribute value and aggregates two or more attribute values of non-key items to form one record. According to the reference condition, the attribute value of the key item of one of the two or more search results is the attribute value of the key item included in another search result different from the one search result, and one search. Information indicating that the attribute values of key items that are not included in the results are added, and two or more attribute values of non-key items are aggregated, and two or more search results are combined by the completion process that constitutes one record. It is a search device.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be appropriately integrated.

Further, in the search device of the sixth invention, for any one of the second to fifth inventions, the user attribute value source information of any one or more of the user attribute value source information is one or more. An arithmetic expression or program whose parameters are one or more attribute identifiers of the view attribute identifier of any of the transformed views or the source attribute identifier of any of two or more data sources and the attribute values corresponding to one or more attribute identifiers. When the search unit acquires the user attribute value corresponding to the user attribute value source information, the search unit converts the attribute value corresponding to one or more attribute identifiers possessed by the user attribute value source information into a conversion view or data. It is a search device that acquires a user attribute value by executing an arithmetic expression or program by giving one or more acquired attribute values obtained from a source to a program identified by an arithmetic expression or a program identifier.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be integrated.

Further, the search device of the seventh invention has, for any one of the first to sixth inventions, the source layer definition information has command source information for generating a search command for the data source, and 2 There are at least two or more different types of command source information in the command source information corresponding to each of the above data sources, and the search unit can use the command source information for each of the two or more data sources from two or more data sources. It is a search device that generates a search command for acquiring information, acquires a search result based on the search command, integrates two or more search results, and acquires integrated data.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be integrated.

Further, in the search device of the eighth invention, with respect to the seventh invention, two or more kinds of different command source information are used to generate information for generating a search command for an SQL statement and for generating a search module. The search unit generates a search command which is an SQL statement according to the instruction source information for the data source corresponding to the SQL statement according to the instruction source information for each of two or more data sources including the information, and the search module. For the data source corresponding to, the search instruction which is the interface of the search module according to the instruction source information is generated, and the search result based on the search instruction is acquired for each of 2 or more data sources, and 2 or more. It is a search device that integrates the search results of the above and acquires the integrated data.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be integrated.

Further, the search device of the ninth invention has connection information for accessing each of two or more data sources in the source layer definition information for any one of the first to eighth inventions, and searches. The department uses the connection information to access the data source corresponding to the connection information, obtains the search result based on the search command from the data source, integrates two or more search results, and acquires the integrated data. It is a device.

With such a configuration, information can be appropriately searched from two or more data sources, and the search results can be integrated.

Further, the search device of the tenth invention has two or more data sources for at least one data source among two or more data sources for any one of the first to ninth inventions. An array index having attribute position information for specifying the position where the attribute value exists is stored for each one or more records of the records and for each one or more attributes of each record. The attribute position information corresponding to the attribute identifier of the search condition is acquired from the array index, the attribute value corresponding to the attribute identifier of the search condition is acquired from the data source using the attribute position information, and the integration having the attribute value is obtained. It is a search device that composes data.

With such a configuration, information retrieval can be performed at high speed.

According to the search device according to the present invention, information can be appropriately searched from two or more data sources, and the search results can be integrated.

Conceptual diagram of the search system A in the first embodiment Block diagram of the search system A Block diagram of the search device 1 constituting the search system A A flowchart illustrating an operation example of the search device 1. A flowchart illustrating an example of the index generation process. Flowchart explaining an example of the source index generation process A flowchart illustrating an example of the same array label index generation process. A flowchart illustrating an example of the same array index generation process. A flowchart illustrating an example of the record index generation process. A flowchart illustrating an example of the secondary index generation process. A flowchart illustrating an example of the search process. Diagram showing an example of the same data source A diagram illustrating an example of index generation processing and an example of search processing. The figure explaining the search processing example Conceptual diagram of the search system B in the second embodiment Block diagram of the search system B Block diagram of the search device 4 A flowchart illustrating an operation example of the search device 4. A flowchart illustrating an example of the instruction generation process. A flowchart illustrating an example of the integrated process. A flowchart illustrating an example of the same join method identifier processing. A flowchart illustrating an example of the same join method identifier processing. Diagram showing an example of the same data source Diagram showing an example of the same source layer definition information Diagram showing an example of the same source layer definition information Diagram showing an example of the same source layer definition information Diagram showing an example of the data source specific information Diagram showing conversion view information of the same sales view Diagram showing conversion view information of the same purchase view The figure which shows the example of the same user layer definition information The figure explaining the operation example of the search apparatus 4. Overview of the computer system in the above embodiment Block diagram of the computer system

Hereinafter, embodiments of the search device and the like will be described with reference to the drawings. In addition, since the components with the same reference numerals perform the same operation in the embodiment, the description may be omitted again.

(Embodiment 1)
In the present embodiment, a search system including a search device for searching information on a data source using one or more types of indexes will be described. The one or more types of indexes are, for example, an array index described later, an array label index described later, a record index described later, a secondary index described later, and a source index described later.

Further, in the present embodiment, a search system including a search device for generating one or more types of indexes corresponding to the data source by using the data source will be described.

Further, in the present embodiment, a search system including a search device for automatically updating the index will be described.

FIG. 1 is a conceptual diagram of the search system A according to the present embodiment. The search system A includes, for example, a search device 1, 1 or 2 or more data source management devices 2, or 1 or 2 or more terminal devices 3.

The search device 1 is a device for searching information from a data source. The data source management device 2 is a device in which one or more data sources are stored. The terminal device 3 is a terminal used by a user who searches for information.

The search device 1 and the data source management device 2 are, for example, so-called servers, for example, a cloud server, an ASP server, and the like. The type of the search device 1 and the data source management device 2 does not matter. Further, the search device 1 may be a stand-alone device. In such a case, the search system A does not have to have the data source management device 2 and the terminal device 3. In such a case, the data source is stored in the search device 1.

Further, the search device 1 and the data source management device 2 of 1 or more can communicate with each other via a network such as the Internet or a LAN. Further, the search device 1 and the terminal device 3 can communicate with each other via a network such as the Internet or a LAN.

FIG. 2 is a block diagram of the search system A according to the present embodiment. FIG. 3 is a block diagram of the search device 1 constituting the search system A.

The search device 1 includes a storage unit 11, a reception unit 12, a processing unit 13, and an output unit 14. The storage unit 11 includes a data source storage unit 111 and an index storage unit 112. The index storage unit 112 includes an array index storage unit 1121, an array label index storage unit 1122, a record index storage unit 1123, a secondary index storage unit 1124, and a source index storage unit 1125. The reception unit 12 includes a condition reception unit 121. The processing unit 13 includes an index generation unit 131, a search unit 132, and an index update unit 133. The index generation unit 131 includes an array index generation unit 1311, an array label index generation unit 1312, a record index generation unit 1313, a secondary index generation unit 1314, and a source index generation unit 1315. The output unit 14 includes a result output unit 141.

The data source management device 2 includes a data source storage unit 111.

The terminal device 3 includes a terminal storage unit 31, a terminal reception unit 32, a terminal processing unit 33, a terminal transmission unit 34, a terminal reception unit 35, and a terminal output unit 36.

Various types of information are stored in the storage unit 11 that constitutes the search device 1. The various types of information are, for example, a data source described later and one or more types of indexes described later.

One or two or more data sources are stored in the data source storage unit 111. The search device 1 does not have to have the data source storage unit 111. In such a case, the data source to be searched is stored in the data source management device 2.

A data source is a set of data to be searched. Data can be called information. The data source is usually a single file. However, the data source may be, for example, one database, one table in the database, or the like. A data source usually has one or more records. A record may be called a line, a tuple, or the like, for example. The delimiter is recognizable, for example, the records are separated by the first delimiter. The first delimiter is, for example, a return code, a TAB code, a space, or the like, but it does not matter. The data source may have data other than the search target. The data other than the search target is, for example, an item label and an attribute identifier. The item label is an item label, but may be an item name. The item has, for example, a key item and a detailed item. The key item is an identifier for the key item value. Further, two or more key items may exist in one record. The item item is an item including a key item. It may be considered that the key item and the detail item are also attribute identifiers. That is, it may be considered that the key item value and the detail item value are also attribute values constituting the record. The attribute identifier is information that identifies the attribute. The attribute identifier is, for example, an attribute name or an attribute ID. Records usually have two or more attribute values. The record may also have key item values and item item values. However, the record may have one attribute value. The delimiters are recognizable, for example, separated by a second delimiter between the attribute values in the record. The second delimiter is, for example, a comma ",", a colon ":", a semicolon ";", a space, a TAB code, or the like, but it does not matter. The data source corresponds to the source identifier. The source identifier is information that identifies a data source, and is, for example, a file name or a file ID. The key item value is, for example, predetermined. It should be noted that what is predetermined means that it is usually determined at the time of index generation according to the user's specification.

Attribute values in data sources are usually variable length rather than fixed length. Also, the records in the data source are usually variable length rather than fixed length. However, the attribute values and records in the data source may have a fixed length.

It is preferable that the data source corresponds to one or more source attribute values. The source attribute value is the attribute value of the data source. The source attribute value is, for example, last update information, updater identifier, size, and type identifier. The information at the time of the last update is information for specifying the time of the last update of the data source, and is, for example, the year, month, day, hour, minute, second, and month, day, hour, and minute. The updater identifier is information that identifies the updater (usually the last updater) of the data source. The size is the data size of the data source, for example, the number of bytes and the number of bits. The type identifier is information that identifies the type of data source, and is, for example, a "file", "RDB", or "table". "File" indicates that the data source is a file. "RDB" indicates that the data source is an RDB (relational database). "Table" indicates that the data source is tabular information.

The index storage unit 112 stores one or two or more types of indexes. An index is information (usually an index) that is referenced to retrieve desired information from a data source. The index is, for example, an array index described later, an array label index described later, a record index described later, a secondary index described later, and a source index described later.

Each index of one or more types is, for example, a file. However, the index may be information in a database such as RDB, and its physical structure does not matter. The information in the database is, for example, a table.

It is preferable that the index is associated with the information at the time of generation. The generation time information is information that specifies the time when the index is generated, and is, for example, the year, month, day, hour, minute, second, and month, day, day, and minute.

The array index is stored in the array index storage unit 1121. The array index storage unit 1121 usually stores an array index for each data source. That is, the array index usually corresponds to a source identifier that identifies the data source. If there is only one data source to be searched, the array index does not need to correspond to the source identifier.

The array index is information for specifying the position of the attribute value in the record. The array index has one or more array index records that are record-by-record information that the data source has. The array index record has attribute position information for each attribute of each record. The attribute position information is information that identifies the position where the attribute value exists. The attribute position information is usually an offset within the record of the attribute value. However, the attribute position information may be an offset or the like in the data source. The attribute position information corresponds to, for example, a record identifier that identifies a record and an attribute identifier.

It is preferable that the array index has the attribute position information of some attribute values corresponding to all the records, but it has the attribute position information of all the attribute values corresponding to all the records of the data source. It may have the attribute position information of all the attribute values corresponding to some records, or may have the attribute position information of some attribute values corresponding to some records.

When the array index has only the attribute position information of some attribute values, the array index has the attribute position information in the order of the list of the attribute values in the record of the data source.

The array label index storage unit 1122 stores the array label index. The array label index storage unit 1122 usually stores an array label index for each data source. That is, the array label index usually corresponds to the source identifier. If there is only one data source to be searched, the array label index does not need to correspond to the source identifier.

The array label index is information for specifying the order of attributes in the records of the data source. The array label index has one or more array label index records that are record-by-record information that the data source has. The array label index record is information indicating the order of attributes in the record. An array label index record is, for example, a set of an attribute identifier and attribute order information. Each of the two or more array label index records may be, for example, an attribute identifier arranged in order in the record. It is preferable that the array label index is information that identifies the order of all attributes in the record. In the array label index, it is preferable that the attribute identifiers are sorted.

The record index is stored in the record index storage unit 1123. The record index storage unit 1123 normally stores a record index for each data source. That is, the record index usually corresponds to the source identifier. If there is only one data source to be searched, the record index does not need to correspond to the source identifier.

A record index is an index that corresponds to a record in the data source. The record index has one or more record index records for locating records in the data source. The record index record has a key item value or a combination of two or more key item values and record position information. The record index record may be a set of a key item value, a record position information, and a record index record position information.
It is also preferable to have a different record index with different key item values within the same record, or a combination of key item values and record position information.

The key item value is an attribute value included in the record and is a key attribute value. The key item value is preferably unique information that can identify the record, but does not have to be unique information.

The record position information is information that identifies the position of the record including the key item value. The record position information is, for example, an offset in the data source that identifies the position of the record. The record position information is, for example, the offset at the beginning of the record. The record position information may be, for example, an offset of the last information of the record.

The record index record position information is information that identifies the position of the record index record in the record index. The record index record position information is, for example, the offset of the record index record in the record index.

It is preferable that the key item values are sorted in the record index.

Further, it is preferable that the record index record and the array index record are associated with each other. The record index record and the array index record are associated with each other by, for example, a key item value.

The secondary index is stored in the secondary index storage unit 1124. The secondary index storage unit 1124 usually stores a secondary index for each data source. That is, the secondary index usually corresponds to the source identifier. When there is only one data source to be searched, the secondary index does not need to correspond to the source identifier.

The secondary index is an index for high-speed access to the record index. The quadratic index is information corresponding to each one or more records that is a part of the two or more records possessed by the data source. The secondary index has a secondary index record for each record. The secondary index record is a set of the key item value and the record index record position information. Record index The record position information is a place in the record index and is information for specifying a place where the record position information exists. The key item value is the key item value that the record has.

It is preferable that the key item values in the secondary index are sorted.

The source index is stored in the source index storage unit 1125. The source index is an index for each data source. A source index is, for example, a collection of source index records for each data source.

A source index record is, for example, a set of a source identifier, a minimum key item value, and a maximum key item value. The minimum key item value is the minimum key item value that the data source identified by the source identifier has. The maximum key item value is the maximum key item value possessed by the data source identified by the source identifier. In such cases, different records are usually stored in each of the two or more data sources.

A source index record is, for example, a set of a source identifier, a minimum attribute identifier, and a maximum attribute identifier. The minimum attribute identifier is the smallest attribute identifier of the data source identified by the source identifier. The maximum attribute identifier is the largest attribute identifier of the data source identified by the source identifier. In such a case, usually, attribute values of different attributes are stored in each of two or more data sources.

A source index record is, for example, a set of a source identifier, a minimum key item value, a maximum key item value, a minimum attribute identifier, and a maximum attribute identifier. In such a case, usually, the attribute values of some attributes of some records are stored in each of two or more data sources.

The reception unit 12 receives various instructions and information. The various instructions and information are, for example, search conditions, data sources, and some information constituting the data source, which will be described later.

Here, the reception is usually reception from the terminal device 3, but reception of information input from an input device such as a keyboard, mouse, or touch panel, and reading from a recording medium such as an optical disk, a magnetic disk, or a semiconductor memory. It may be a concept including acceptance of the provided information.

The condition reception unit 121 accepts search conditions. The search condition includes, for example, one or more attribute identifiers. The search condition includes, for example, one or more key item values. The search condition includes, for example, one or more attribute identifiers and one or more key item values.

The processing unit 13 performs various processes. The various processes are, for example, processes performed by the index generation unit 131, the search unit 132, and the index update unit 133.

When the receiving unit 12 receives the data source, the processing unit 13 stores the data source in the data source storage unit 111. At that time, the processing unit 13 acquires the last update information from a clock (not shown) and associates the last update information with the data source.

When the receiving unit 12 receives a part of the information constituting the data source, the processing unit 13 updates the data source by using the part of the information. At that time, the processing unit 13 acquires the last update information from a clock (not shown) and associates the last update information with the data source.

The index generator 131 generates an index from each of one or more data sources.

The array index generation unit 1311 generates an array index for each one or more data sources and stores it in the array index storage unit 1121.

The array index generation unit 1311 acquires the attribute position information for each record in the data source and for each attribute value of 1 or more.

The array index generation unit 1311 acquires an array index record having attribute position information of a part of each attribute value for each record in the data source, and constitutes an array index having one or more array index records. , It is preferable to store in the array index storage unit 1121. However, the array index generation unit 1311 acquires an array index record having attribute position information of all each attribute value for each record in the data source, and obtains an array index having one or more array index records. It may be configured and stored in the array index storage unit 1121.

It is preferable that the array index record is information having only the attribute position information of some of the attribute values among all the attribute values in the record. It does not matter how to select some of these attribute values. It is preferable that some attribute values are selected for each predetermined value (for example, every four such as the first, fifth, ninth, etc.), but even if a predetermined number are randomly selected. good.

The array index generation unit 1311 acquires the attribute position information for each one or more records of the two or more records in the data source and for each attribute value of one or more. Then, the array index generation unit 1311 generates an array index having attribute position information for each record and each attribute value, and stores the array index in the array index storage unit 1121.

The array index generation unit 1311 stores, for example, the acquired attribute position information in the array index storage unit 1121 so as to correspond to the record identifier or the key item value and the attribute value identifier.

The array index generation unit 1311 usually scans the data source, recognizes a record for each first delimiter, scans the record, recognizes an attribute value for each second delimiter, and for example, from the beginning of the record. The next position of each second delimiter is acquired as the attribute position information of each attribute value.

The array label index generation unit 1312 generates an array label index for each one or more data sources and stores it in the array label index storage unit 1122.

The array label index generation unit 1312 acquires, for example, an attribute value identifier and attribute order information for each of two or more attributes from a data source, and the array label is a set of the attribute value identifier and the attribute order information. -Acquires an index record, constitutes an array label index having two or more array label index records, and stores the array label index in the array label index storage unit 1122.

It is preferable that the array label index generation unit 1312 sorts the array label index records as the attribute value identifier key to form the array label index.

Also, if the array index record has attribute position information for all attribute values, then the array label index is not needed.

The record index generation unit 1313 refers to the data source and acquires a record index record having a key item value and record position information of each of two or more records of the data source for each record. Then, the record index generation unit 1313 generates a record index having a set of record index records for each record, and stores the record index in the record index storage unit 1123.

The record index generation unit 1313 acquires the record index record position information that specifies the position of the record index record in the record index for each one or more record index records, and obtains the record index record position information. It is preferable to construct a record index record having a record.

It is preferable that the record index generation unit 1313 sorts the record index records using the key item value as a key to form a record index.

The secondary index generation unit 1314 determines the record index record position information and the key item value of the record for each one or more records that are a part of the two or more records possessed by the data source for each data source. A set of secondary index records is acquired, a secondary index having one or more secondary index records is configured, and the secondary index records are stored in the secondary index storage unit 1124.

Further, when the attribute value position information of the array index is the information for specifying the position in the data source, the record index may be omitted.

The secondary index generation unit 1314 refers to, for example, the record index corresponding to the data source for each data source, is a part of the records possessed by the record index, and is a record index possessed by each of two or more records. A secondary index record, which is a set of record position information and a key item value, is acquired, a secondary index having two or more secondary index records is generated, and the secondary index is stored in the secondary index storage unit 1124.

The secondary index record corresponds to a part of the record index record, but the method of selecting the part of the record index record does not matter. It is preferable that some record index records are selected for each predetermined value (for example, every four such as the first, fifth, ninth, etc.), but a predetermined number are randomly selected. May be.

The secondary index speeds up the search for records, but it is not necessary.

The source index generation unit 1315 acquires a source index record for each of two or more data sources, generates a source index having two or more source index records, and stores the source index in the source index storage unit 1125. .. The source index record is, for example, a set of a source identifier, a minimum key item value, and a maximum key item value. A source index record is, for example, a set of a source identifier, a minimum attribute identifier, and a maximum attribute identifier. A source index record is, for example, a set of a source identifier, a minimum key item value, a maximum key item value, a minimum attribute identifier, and a maximum attribute identifier.

If there is only one data source, the source index generation unit 1315 is unnecessary.

The search unit 132 acquires the attribute position information corresponding to the attribute identifier of the search condition from the array index, and uses the attribute position information to set the attribute value corresponding to the attribute identifier of the search condition as the key item value. Obtained from a data source containing one or more records with two or more attribute values.

The search unit 132 has, for example, the first attribute position information corresponding to the attribute identifier that identifies the attribute value arranged before the attribute value identified by the attribute identifier of the search condition received by the condition reception unit 121. , The second attribute position information corresponding to the attribute identifier that identifies the attribute value arranged after the attribute value identified by the attribute identifier of the search condition is acquired from the array index. Next, the search unit 132 is an attribute value existing between the position specified by the first attribute position information and the position specified by the second attribute position information, and corresponds to the attribute identifier of the search condition. Get the attribute value to be used from the data source.

The search unit 132 acquires, for example, the attribute order information corresponding to the attribute identifier of the search condition received by the condition reception unit 121 from the array label index. Next, the search unit 132 acquires the attribute position information corresponding to the attribute identifier of the search condition from the array index by using the attribute order information. Next, the search unit 132 acquires the attribute value corresponding to the attribute identifier of the search condition from the data source by using the attribute position information.

The search unit 132 acquires, for example, the attribute order information corresponding to the attribute identifier of the search condition received by the condition reception unit 121 from the array label index. The search unit 132 is arranged after the first attribute position information corresponding to the attribute identifier that identifies the attribute value arranged before the order indicated by the attribute order information and the order indicated by the attribute order information. The second attribute position information corresponding to the attribute identifier that identifies the attribute value is acquired from the array index. Next, the search unit 132 is an attribute value existing between the position specified by the first attribute position information and the position specified by the second attribute position information, and corresponds to the attribute identifier of the search condition. Get the attribute value to be used from the data source.

The search unit 132 acquires, for example, the record position information paired with the key item value of the search condition from the record index. Next, the search unit 132 determines the record corresponding to the position specified by the record position information, and obtains the attribute value in the record and the attribute value corresponding to the attribute identifier of the search condition from the data source. get. If the attribute identifier is not shown in the search condition, it may be considered that the attribute identifier possessed by the search condition is all the attribute identifiers.

The search unit 132 acquires, for example, two key item values sandwiching the key item value of the search condition from the secondary index. Next, the search unit 132 acquires the first record index record position information and the second record index record position information paired with the acquired two key item values from the secondary index. Next, the search unit 132 searches for a record index record between the first record index record position information and the second record index record position information, and includes the key item value of the search condition. The record index record is determined, and the record position information in the record index record is acquired. Next, the search unit 132 acquires the attribute value corresponding to the attribute identifier of the search condition, which is the attribute value in the record corresponding to the position specified by the record position information, from the data source. The search unit 132 acquires the attribute position information of the attribute value corresponding to the attribute identifier of the search condition by using the array index, and acquires the attribute value of the position specified by the attribute position information from the data source. Is suitable.

Further, when the key item values are sorted in the record index, it is preferable that the search unit 132 determines the record index record including the key item value of the search condition by binary search, but sequentially. You can also search.

The search unit 132 acquires, for example, a source identifier that matches the key item value of the search condition or is paired with the minimum key item value and the maximum key item value with the key item value sandwiched between them from the source index. Next, the search unit 132 acquires the attribute position information corresponding to the attribute identifier of the search condition from the array index from the data source identified by the source identifier. Next, the search unit 132 acquires the attribute value corresponding to the attribute identifier of the search condition, which is the attribute value in the record, by using the attribute position information.

The search unit 132 acquires, for example, a source identifier that matches the attribute identifier of the search condition or that is paired with the minimum attribute identifier and the maximum attribute identifier with the attribute identifier sandwiched between them from the source index. The search unit 132 acquires the attribute position information corresponding to the attribute identifier of the search condition from the array index corresponding to the data source identified by the source identifier. The search unit 132 uses the attribute position information to acquire the attribute value in the record in the data source identified by the source identifier and the attribute value corresponding to the attribute identifier of the search condition.

The search unit 132 acquires, for example, a source identifier corresponding to the key item value of the search condition and the attribute identifier of the search condition from the source index. The search unit 132 acquires two key item values sandwiching the key item value of the search condition from the secondary index corresponding to the data source identified by the source identifier. Next, the search unit 132 acquires the first record index record position information and the second record index record position information paired with the acquired two key item values from the secondary index. Next, the search unit 132 searches for a record index record between the first record index record position information and the second record index record position information, and includes the key item value of the search condition. The record index record is determined, and the record position information in the record index record is acquired. Further, the search unit 132 acquires the attribute order information corresponding to the attribute identifier of the search condition from the array label index. Next, the search unit 132 acquires the attribute position information corresponding to the attribute identifier of the search condition from the array index by using the attribute order information. Next, the search unit 132 acquires the attribute value in the record specified by the acquired record position information from the data source.

When the index update unit 133 satisfies a predetermined condition, the last update time indicated by the last update time information acquired from the data source is the generation time indicated by the generation time information corresponding to one or more types of indexes. It is determined whether or not it is later, and if it is later, the index generation unit 131 is operated to form one or more types of indexes. Further, the index update unit 133 usually overwrites each of the configured indexes of one or more types with the old index of the index storage unit 112. Each type of index of 1 or more is one or more of an array index, an array label index, a record index, a secondary index, and a source index. Further, the predetermined conditions are, for example, that an instruction from the user has been received, that the time has reached a predetermined time, and that the data source has been updated.

The output unit 14 acquires various types of information. Various types of information are, for example, search results described later. The output here is usually transmission to the terminal device 3, but display on a display, projection using a projector, printing by a printer, storage on a recording medium, other processing devices and other devices. The concept may include delivery of the processing result to a program or the like.

The result output unit 141 outputs the search result including the attribute value acquired by the search unit 132. Search results usually have attribute values.

The data source management device 2 manages one or more data sources. The data source management device 2 includes a data source storage unit 111.

Various types of information are stored in the terminal storage unit 31 that constitutes the terminal device 3. Various types of information are, for example, search conditions and data sources.

The terminal reception unit 32 receives various instructions and information. Various instructions and information are, for example, search conditions, data sources, and information of a part of data sources.

The acceptance here means acceptance of information input from input devices such as keyboards, mice, and touch panels, reception of information transmitted via wired or wireless communication lines, optical disks, magnetic disks, semiconductor memories, etc. It is a concept including acceptance of information read from a recording medium of.

The terminal processing unit 33 performs various processes. The various processes are, for example, a process of converting an instruction or information received by the terminal reception unit 32 into an instruction or information of a data structure to be transmitted. The various processes are, for example, a process of converting the information received by the terminal receiving unit 35 into the information of the data structure to be output.

The terminal transmission unit 34 transmits various information and instructions. The terminal transmission unit 34 usually transmits various information and instructions to the search device 1. Various information and instructions are, for example, search conditions and data sources.

The terminal receiving unit 35 receives various types of information. The terminal receiving unit 35 receives various information from the search device 1. The various information is, for example, a search result.

The terminal output unit 36 outputs various information. The various information is, for example, a search result.

Storage unit 11, data source storage unit 111, index storage unit 112, array index storage unit 1121, array label index storage unit 1122, record index storage unit 1123, secondary index storage unit 1124, source index storage unit 1125, A non-volatile recording medium is suitable for the terminal storage unit 31, but a volatile recording medium can also be used.

The process of storing information in the storage unit 11 or the like does not matter. For example, the information may be stored in the storage unit 11 or the like via the recording medium, or the information transmitted via the communication line or the like may be stored in the storage unit 11 or the like. Alternatively, the information input via the input device may be stored in the storage unit 11 or the like.

The reception unit 12, the condition reception unit 121, and the terminal reception unit 35 are usually realized by wireless or wired communication means, but may be realized by means for receiving broadcasts.

Processing unit 13, index generation unit 131, search unit 132, index update unit 133, array index generation unit 1311, array label index generation unit 1312, record index generation unit 1313, secondary index generation unit 1314, source index generation. The unit 1315 and the terminal processing unit 33 can usually be realized from a processor, a memory, or the like. The processing procedure of the processing unit 13 and the like is usually realized by software, and the software is recorded in a recording medium such as ROM. However, it may be realized by hardware (dedicated circuit). The processor is a CPU, MPU, GPU, or the like, and the type thereof does not matter.

The output unit 14, the result output unit 141, and the terminal transmission unit 34 are usually realized by wireless or wired communication means, but may be realized by broadcasting means.

The terminal reception unit 32 can be realized by a device driver for input means such as a touch panel or a keyboard, control software for a menu screen, or the like.

The terminal output unit 36 may or may not include an output device such as a display or a speaker. The terminal output unit 36 can be realized by the driver software of the output device, the driver software of the output device, the output device, or the like.

Next, an operation example of the search system A will be described. First, an operation example of the search device 1 will be described with reference to the flowchart of FIG.

(Step S401) The index generation unit 131 determines whether or not it is time to generate an index. If it is the timing to generate an index, it goes to step S402, and if it is not the timing to generate an index, it goes to step S406.

(Step S402) The index generation unit 131 substitutes 1 for the counter i.

(Step S403) The index generation unit 131 determines whether or not the i-th data source for which the index is generated exists. If the i-th data source exists, the process goes to step S404, and if the i-th data source does not exist, the process returns to step S401.

(Step S404) The index generation unit 131 generates an index corresponding to the i-th data source. An example of the index generation process will be described with reference to the flowchart of FIG.

(Step S405) The index generation unit 131 increments the counter i by 1. Return to step S403.

(Step S406) The index update unit 133 determines whether or not it is time to update the index. If it is the timing to update the index, the process goes to step S407, and if it is not the timing to update the index, the process goes to step S414.

(Step S407) The index update unit 133 substitutes 1 for the counter i.

(Step S408) The index update unit 133 determines whether or not the i-th data source exists. If the i-th data source exists, the process goes to step S409, and if the i-th data source does not exist, the process returns to step S401.

(Step S409) The index update unit 133 acquires the last update information which is the attribute value of the i-th data source.

(Step S410) The index update unit 133 acquires information at the time of generation of an index (for example, an array index) corresponding to the i-th data source from the array index storage unit 1121.

(Step S411) The index update unit 133 determines whether or not the time indicated by the last update information acquired in step S409 is newer than the time indicated by the generation information acquired in step S410. If it is new, it goes to step S412, and if it is not new, it goes to step S413.

(Step S412) The index update unit 133 instructs the index generation unit 131 to operate. As a result, the index generation unit 131 generates an index, associates it with the i-th data source, and accumulates the index. By such processing, the index corresponding to the i-th data source is updated. An example of the index generation process is the flowchart of FIG.

(Step S413) The counter i is incremented by 1. Return to step S408.

(Step S414) The condition reception unit 121 determines whether or not the search condition has been accepted. If the search condition is accepted, the process goes to step S415, and if the search condition is not accepted, the process returns to step S401.

(Step S415) The search unit 132 performs a search using the search conditions. An example of such a search process will be described with reference to the flowchart of FIG.

(Step S416) The result output unit 141 outputs the search result acquired in step S415. Return to step S401.

In the flowchart of FIG. 4, the process ends when the power is turned off or an interrupt for the end of the process is interrupted.

Next, an example of the index generation process in step S404 will be described with reference to the flowchart of FIG.

(Step S501) The source index generation unit 1315 generates a source index. An example of such a source index generation process will be described with reference to the flowchart of FIG.

(Step S502) The array label index generation unit 1312 generates an array label index. An example of such an array label index generation process will be described with reference to the flowchart of FIG. 7.

(Step S503) The array index generation unit 1311 generates an array index. An example of such an array index generation process will be described with reference to the flowchart of FIG.

(Step S504) The record index generation unit 1313 generates a record index. An example of such a record index generation process will be described with reference to the flowchart of FIG.

(Step S505) The secondary index generation unit 1314 generates a secondary index. An example of such a secondary index generation process will be described with reference to the flowchart of FIG.

In the flowchart of FIG. 5, for example, the record index and the array index may be generated together for each record. That is, the procedure and order of generating various indexes are not limited.

Next, an example of the source index generation process in step S501 will be described with reference to the flowchart of FIG.

(Step S601) The source index generation unit 1315 determines whether or not different records exist in each of the two or more data sources. If there are different records, the process goes to step S602, and if there are no different records, the process goes to step S604.

(Step S602) The source index generation unit 1315 refers to the data source for which the index is generated, and acquires the minimum key item value of the data source.

(Step S603) The source index generation unit 1315 refers to the data source for which the index is generated, and acquires the maximum key item value of the data source.

(Step S604) The source index generation unit 1315 determines whether or not attribute values of different attributes exist in each of the two or more data sources. If the attribute values of different attributes exist, the process goes to step S605, and if the attribute values of different attributes do not exist, the process goes to step S607.

(Step S605) The source index generation unit 1315 refers to the data source for which the index is generated, and acquires the minimum attribute identifier of the data source.

(Step S606) The source index generation unit 1315 refers to the data source for which the index is generated, and acquires the maximum attribute identifier of the data source.

(Step S607) The source index generation unit 1315 acquires the source identifier of the data source for which the index is generated.

(Step S608) The source index generation unit 1315 constitutes a source index record. The source index record has, for example, a minimum key item value and a maximum key item value. The source index record has, for example, a minimum attribute identifier and a maximum attribute identifier. The source index record has, for example, a minimum key item value, a maximum key item value, a minimum attribute identifier, and a maximum attribute identifier. The source index record corresponds to the source identifier. Needless to say, corresponding to the source identifier may mean having the source identifier.

(Step S609) The source index generation unit 1315 adds the source index record configured in step S608 to the source index storage unit 1125. Return to higher-level processing.

Next, an example of the array label index generation process in step S502 will be described with reference to the flowchart of FIG. 7.

(Step S701) The array label index generation unit 1312 assigns 1 to the counter i.

(Step S702) The array label index generation unit 1312 acquires the attribute identifier of the i-th attribute of the data source for which the index is generated.

The array label index generation unit 1312 acquires, for example, the attribute identifier of the i-th attribute of the record in the first row in the data source for which the index is generated. The array label index generation unit 1312 may acquire the attribute identifier of the i-th attribute from the data source schema information stored in the storage unit 11, for example. The data source schema information is information that specifies the structure of the data source, and has, for example, two or more attribute identifiers.

(Step S703) The array label index generation unit 1312 determines whether or not the attribute identifier of the i-th attribute could be acquired in step S702. If it can be acquired, it goes to step S704, and if it cannot be acquired, it returns to the higher-level processing.

(Step S704) The array label index generation unit 1312 constitutes an array label index record having the attribute identifier of the i-th attribute acquired in step S702 and i (attribute order information). The array label index record is information that constitutes the array label index.

(Step S705) The array label index generation unit 1312 adds the array label index record configured in step S704 to the array label index storage unit 1122 in association with the data source for which the index is generated.

(Step S706) The array label index generation unit 1312 increments the counter i by 1. Return to step S702.

In the flowchart of FIG. 7, it is preferable to sort the array label index record using the attribute identifier as a key to form the array label index.

Next, an example of the array index generation process in step S503 will be described with reference to the flowchart of FIG.

(Step S801) The array index generation unit 1311 substitutes 1 for the counter i.

(Step S802) The array index generation unit 1311 determines whether or not the i-th record exists in the data source for which the index is generated. If the i-th record exists, the process proceeds to step S803, and if the i-th record does not exist, the process returns to higher processing.

(Step S803) The array index generation unit 1311 assigns 1 to the counter j.

(Step S804) The array index generation unit 1311 determines whether or not the j-th attribute exists in the data source for which the index is generated. If the j-th attribute exists, the process goes to step S805, and if the j-th attribute does not exist, the process goes to step S809.

(Step S805) The array index generation unit 1311 determines whether or not to use the j-th attribute for the array index. If the jth attribute is used for the array index, go to step S806, and if not, go to step S808.

(Step S806) The array index generation unit 1311 acquires the attribute position information of the attribute value of the j-th attribute of the i-th record from the data source for which the index is generated.

(Step S807) The array index generation unit 1311 adds the attribute position information acquired in step S806 to the buffer of the array index record.

(Step S808) The array index generation unit 1311 increments the counter j by 1. Return to step S804.

(Step S809) The array index generation unit 1311 adds the array index record of the buffer of the array index record to the array index storage unit 1121.

(Step S810) The array index generation unit 1311 increments the counter i by 1. Return to step S802.

Next, an example of the record index generation process in step S504 will be described with reference to the flowchart of FIG.

(Step S901) The record index generation unit 1313 assigns 1 to the counter i.

(Step S902) The record index generation unit 1313 determines whether or not the i-th record exists in the data source for which the index is generated. If the i-th record exists, the process proceeds to step S903, and if the i-th record does not exist, the process returns to higher processing.

(Step S903) The record index generation unit 1313 refers to the data source for which the index is generated, and acquires the record position information of the i-th record.

(Step S904) The record index generation unit 1313 refers to the data source for which the index is generated, and acquires the key item value of the i-th record.

(Step S905) The record index generation unit 1313 acquires the record index record position information which is the position information in the record index of the i-th record index record.

(Step S906) The record index generation unit 1313 has the record position information acquired in step S903, the key item value acquired in step S904, and the record index record position information acquired in step S905. Make up a record.

(Step S907) The record index generation unit 1313 adds the record index record configured in step S906 to the record index storage unit 1123.

(Step S908) The record index generation unit 1313 increments the counter i by 1. Return to step 902.

In the flowchart of FIG. 9, it is preferable that the record index generation unit 1313 sorts the record index records using the key item value as a key. In such a case, it goes without saying that the record index generation unit 1313 acquires the record index record position information in the sorted state for each record index record.

Next, an example of the secondary index generation process in step S505 will be described with reference to the flowchart of FIG.

(Step S1001) The secondary index generation unit 1314 substitutes 1 for the counter i.

(Step S1002) The secondary index generation unit 1314 determines whether or not the i-th record index record exists in the record index. If the i-th record / index record exists, the process goes to step S1003, and if it does not exist, the process returns to higher processing.

(Step S1003) The secondary index generation unit 1314 determines whether or not to use the i-th record index record for the secondary index. If it is used for the secondary index, it goes to step S1004, and if it is not used for the secondary index, it goes to step S1006.

The secondary index generation unit 1314 uses some record index records among all the record index records. In the secondary index generation unit 1314, for example, when the numbers of all records and index records are divided by N (N is a natural number of 2 or more), the remainder value is M (M is an integer, 0 <= M <N−). It is determined that the record index record corresponding to the number in 1) is used. Further, the secondary index generation unit 1314 determines that, for example, some predetermined record index records are used.

(Step S1004) The secondary index generation unit 1314 acquires the key item value and the record index record position information from the i-th record index record, and constitutes a secondary index record having the information.

(Step S1005) The secondary index generation unit 1314 adds the secondary index record configured in step S1004 to the secondary index storage unit 1124.

(Step S1006) The secondary index generation unit 1314 increments the counter i by 1. Return to step 1002.

In the flowchart of FIG. 10, it is preferable that the secondary index records are sorted using the key item value as a key.

Next, an example of the search process in step S415 will be described with reference to the flowchart of FIG.

(Step S1101) The search unit 132 acquires one or more attribute identifiers and one or more key item values corresponding to the accepted search conditions. In addition, one or more attribute identifiers specify an attribute value to be acquired as a search result. The key item value of 1 or more specifies the record for which information is acquired as a search result. That is, the search unit 132 is the attribute value in the record of one or more key item values acquired here, and acquires the attribute value identified by each of the one or more attribute identifiers acquired here.

(Step S1102) The search unit 132 refers to the source index and acquires one or more attribute identifiers acquired in step S1101 and one or more source identifiers corresponding to one or more key item values. Here, the search unit 132 uses the acquired one or more source identifiers as one or more attribute identifiers of the attribute values included in the data source identified by the source identifiers and the data source identified by the source identifiers. Corresponds to one or more key item values of the included record.

(Step S1103) The search unit 132 substitutes 1 for the counter i.

(Step S1104) The search unit 132 determines whether or not the i-th source identifier exists among the one or more source identifiers acquired in step S1102. If the i-th source identifier exists, the process goes to step S1105, and if it does not exist, the process goes to step S1118.

(Step S1105) The search unit 132 substitutes 1 for the counter j.

(Step S1106) The search unit 132 determines whether or not the j-th key item value exists among the one or more key item values associated with the i-th source identifier in step S1102. If the j-th key item value exists, the process goes to step S1107, and if it does not exist, the process goes to step S1117.

(Step S1107) The search unit 132 refers to the secondary index corresponding to the i-th source identifier, and the first record index record position information and the second record index record corresponding to the j-th key item value. Get location information. The first record index record position information is the record index record position information paired with the largest key item value among the key item values smaller than the jth key item value. The second record index record position information is the record index record position information paired with the smallest key item value among the key item values larger than the jth key item value. Further, here, the search unit 132 may acquire one record / index record position information paired with the j-th key item value from the secondary index.

(Step S1108) When the first record index record position information and the second record index record position information are acquired in step S1107, the search unit 132 uses the first record index record position information and the second record index record position information. The record index record between the record index record position information and the record index record of (for example, binary search or sequential search) is searched, and the jth key item value is detected. Next, the search unit 132 acquires the record position information paired with the j-th key item value from the record index.

Further, when one record index record position information is acquired in step S1107, the search unit 132 acquires the record position information paired with the record index record position information from the record index.

(Step S1109) The search unit 132 substitutes 1 for the counter k.

(Step S1110) The search unit 132 determines whether or not the k-th attribute identifier corresponding to the i-th source identifier exists. If the k-th attribute identifier exists, the process goes to step S1111. If the k-th attribute identifier does not exist, the process goes to step S1116.

(Step S1111) The search unit 132 refers to the array label index corresponding to the i-th source identifier, and acquires the attribute order information paired with the k-th attribute identifier from the array label index.

(Step S1112) The search unit 132 refers to the array index corresponding to the i-th source identifier, and determines whether or not the attribute order information matching the attribute order information acquired in step S1111 exists in the array index. to decide. When the attribute order information that matches the attribute order information exists, the search unit 132 acquires the attribute position information that is paired with the attribute order information and is paired with the jth key item value from the array index. ..

If there is no attribute order information that matches the attribute order information, the search unit 132 acquires two attribute order information sandwiching the attribute order information. That is, the search unit 132 acquires the first attribute order information having a value smaller than the attribute order information and having the smallest difference from the attribute order information. Further, the search unit 132 acquires the second attribute order information having a value larger than the attribute order information and having the smallest difference from the attribute order information. The first attribute order information and the second attribute order information are information sandwiching the attribute order information. Next, the search unit 132 acquires the attribute position information that is paired with the first attribute order information and is paired with the jth key item value from the array index. Further, the search unit 132 acquires the attribute position information that is paired with the second attribute order information and is paired with the jth key item value from the array index.

(Step S1113) When one attribute position information is acquired in step S1112, the search unit 132 selects the record at the position indicated by the record position information paired with the jth key item value acquired in step S1108. The attribute value of the position indicated by one attribute position information acquired in step S1112 is acquired from the data source identified by the i-th source identifier.

Further, when the two attribute position information is acquired in step S1112, the search unit 132 uses the two records at the positions indicated by the record position information paired with the j-th key item value acquired in step S1108. The attribute value of the position specified by each attribute position information is inspected by, for example, sequential search, and the attribute value existing in the order of the attribute order information paired with the kth attribute identifier is identified by the i-th source identifier. Obtained from a data source.

(Step S1114) The search unit 132 temporarily stores the attribute value acquired in step S1113 in a buffer (not shown) in association with the j-th key item value and the k-th attribute identifier.

(Step S1115) The search unit 132 increments the counter k by 1. Return to step 1110.

(Step S1116) The search unit 132 increments the counter j by 1. Return to step 1106.

(Step S1117) The search unit 132 increments the counter i by 1. Return to step 1104.

(Step S1118) The search unit 132 constitutes a search result including one or more attribute values temporarily stored in a buffer (not shown). Return to higher-level processing. The method of constructing the search results does not matter. It is preferable that the attribute identifier corresponding to the attribute value included in the search result is included in the search result in a manner in which it is clearly indicated that the attribute value corresponds to the attribute value. Further, it is preferable that the search result includes the j-th key item value.

Next, an operation example of the data source management device 2 will be described. The data source management device 2 reads out the data source of the data source storage unit 111 and transmits it to the search device 1 in response to the access from the search device 1. In such a case, the data source management device 2 may read and transmit only a part of the data source.

Next, an operation example of the terminal device 3 will be described. The terminal reception unit 32 of the terminal device 3 accepts search conditions. Next, the terminal processing unit 33 configures the search condition to be transmitted. Next, the terminal transmission unit 34 transmits the search condition to the search device 1. Then, in response to the transmission of the search condition, the terminal receiving unit 35 receives the search result. Next, the terminal processing unit 33 configures the search result to be output by using the received search result. Next, the terminal output unit 36 outputs the search result.

Hereinafter, a specific operation example of the search system A in the present embodiment will be described.

Now, three or more data sources including the three data sources (1201, 1202, 1203) shown in FIG. 12 are stored in the data source storage unit 111 of the search device 1 or the data source storage unit 111 of the data source management device 2. It is assumed that it has been done. It is assumed that each of the three data sources is one file here.

And the data source of FIG. 12 has a header record, a label record, and a large number of records. The label record and each record are separated by the first delimiter. Further, the first delimiter is, for example, a return code here.

A header record is a so-called header of a file and has one or more source attribute values. The source attribute value is, here, the source identifier, the report number, and the information at the time of the last update. The source identifier is File Name in FIG. 12, and the value is “File1”. The report number is a number for identifying the source of the data source, and the value is "A12345". The information at the time of the last update is Date in FIG. 12, and the value is "XXXX-XX-XX".

The label record is, for example, the first line of the file. If the header record is the first line of the file, the label record is the second line of the file. A label record is a set of item labels and a set of attribute identifiers. Item labels are key item labels or line item labels. The key item is an attribute that is a key of the record, and here, it is a "PID (personal ID)". The "PID" is an ID that identifies a user. The detail item is a user attribute value corresponding to "PID", and here, the detail item includes "No." and "Age". “No.” is a record ID, and its value is [1] [2] [3] of 1201 in FIG. Further, (Pos.) Under "No." is the record position information of each record (here, the offset at the beginning of the record in the data source). "Age" is the age of the user. In FIG. 12, the attribute identifier is “TestB”, “TestE”, “TestC”, or the like. In FIG. 12, the attribute order information is described under the attribute identifier. The attribute order information is [1] [2] [3] or the like under the attribute identifier.

Each record in FIG. 12 has a key item value, a detail item value, and an attribute value. The key item value is the value of the key item, and here, it is the PID (for example, 236,029) of each user. It is preferable that which value is used as the key item value can be specified as a parameter for index generation, and other values (for example, "Age" and "PID and Age pair") may be used, and two or more values may be used. It is also possible to have a key item value. Here, the item item value is, for example, a value of "No." or a value of "Age". Here, the value of "No." is [1], [2], or the like. The values (for example, (1), (121), (241), etc.) existing under the value of "No." ([1], [2], [3], etc.) are the record position information of each record.

The attribute values of the record corresponding to the record identifier [1] are 0.11, 0.4, 0.57, and the like. Further, in FIG. 12, the attribute value position information ((57) (62) (73), etc.) of each attribute value is written below the attribute value (0.11, 0.4, 0.57, etc.). ing.

It is assumed that the data source here includes a set of gene / genomic information. In addition, data dealing with general gene / genome information includes data such as a base sequence of a gene and an amino acid sequence of a protein, and the length of one record may be, for example, several GB. In addition, the number of attribute values in one record becomes enormous, and the data size often becomes enormous. In many cases, data dealing with gene / genome information is stored and distributed in a flat file (general text file) in a relatively simple layout, and the data source (see FIG. 12) in this specific example is This is an example.

In such a situation, the following three specific examples will be described. Specific example 1 is an example of index generation processing. Specific Example 2 is an example of the search process in the case where the source index has a set of the minimum key item value and the maximum key item value and does not have the set of the minimum attribute identifier and the maximum attribute identifier. Specific Example 3 is an example of the search process when the source index has a set of the minimum key item value, the maximum key item value, the minimum attribute identifier, and the maximum attribute identifier.

(Specific example 1)
An example of various index generation processes by the index generation unit 131 of the search device 1 will be described with reference to FIG. Here, it is assumed that the key item is "PID".
(1) Source index generation process

The source index generation unit 1315 accesses the file "data source 1301" and acquires the source identifier (here, the file name) "file1" of the data source 1301. Further, the source index generation unit 1315 opens the data source 1301. Next, the source index generation unit 1315 acquires the minimum key item value "029" which is the minimum PID and the maximum key item value "451" which is the maximum PID among the PIDs of the data source 1301. When the PIDs are sorted in the data source 1301, the source index generation unit 1315 acquires the first PID and the last PID. If the PIDs are not sorted, the source index generator 1315 sequentially inspects the PIDs and obtains the minimum key item value and the maximum key item value from the data source 1301.

Further, the source index generation unit 1315 acquires the minimum attribute identifier "TestA" and the maximum attribute identifier "TestE" among the attribute value identifiers of the label record of the data source 1301. When the attribute identifiers are sorted in the data source 1301, the source index generation unit 1315 acquires the first attribute identifier and the last attribute identifier from the label record. If the attribute identifiers are not sorted, the source index generator 1315 sequentially inspects the attribute identifiers and obtains the minimum attribute identifier and the maximum attribute identifier from the label record.

Next, the source index generation unit 1315 obtains the source index record “file1,029,451, TestA, TestE” from the acquired source identifier, minimum key item value, maximum key item value, minimum attribute identifier, and maximum attribute identifier. , And accumulates in the source index storage unit 1125.

Similarly, the source index generation unit 1315 constitutes a source index record for other data sources (files “file2”, “file3”, etc.) and stores them in the source index storage unit 1125.

By the above processing, the source index of 1302 of FIG. 13 is accumulated in the source index storage unit 1125.
(2) Array label index generation process

The array label index generation unit 1312 accesses the file "data source 1301" and acquires the source identifier (file name) "file1" of the data source 1301. Further, the source index generation unit 1315 opens the data source 1301.

Next, the array label index generation unit 1312 acquires the attribute identifiers in the order in which they are arranged in the label index of the data source 1301 together with the attribute order information in that order. Then, for each attribute identifier, an array label index record which is a set of the attribute identifier and the attribute order information is configured.

Next, the array label index generation unit 1312 sorts the array label index records using the attribute identifier as a key, for example, in ascending order. Then, the array label index generation unit 1312 stores the sorted array label index records in the array label index storage unit 1122.

The array label index generation unit 1312 similarly forms an array label index for other data sources (files “file2”, “file3”, etc.) and stores them in the array label index storage unit 1122.

By the above processing, the array label index of 1303 in FIG. 13 is accumulated in the array label index storage unit 1122.
(3) Array index generation process

The array index generation unit 1311 accesses the file "data source 1301" and acquires the source identifier (file name) "file1" of the data source 1301. Further, the source index generation unit 1315 opens the data source 1301.

The array index generation unit 1311 acquires the attribute order information of the data source 1301 by skipping a predetermined number (here, three), for example, the first, fourth, seventh, and so on. Further, the array index generation unit 1311 advances the file pointer to the attribute value in the order of each acquired attribute order information while detecting the second delimiter for each record, for example, the record of the attribute value in that order. Gets the attribute position information that is the offset within. Next, the array index generation unit 1311 concatenates the acquired attribute position information in the order indicated by the attribute order information in association with the PID of the record for each record of the data source 1301 to form an array index record.

Next, the array index generation unit 1311 sorts the array index records in ascending order, for example, using the corresponding PID as a key, constitutes an array index, and stores the array index records in the array index storage unit 1121.

Further, the array index generation unit 1311 similarly forms an array index for other data sources (files “file2”, “file3”, etc.) and stores them in the array index storage unit 1121.

By the above processing, the array index of 1304 in FIG. 13 is accumulated in the array index storage unit 1121.
(4) Record index generation process

The record index generation unit 1313 accesses the file “data source 1301” and acquires the source identifier (file name) “file1” of the data source 1301. Further, the source index generation unit 1315 opens the data source 1301.

The record index generation unit 1313 acquires the key item value and the record position information which is the offset of the record in the data source 1301 from the data source 1301 for each record in the data source 1301 and constitutes the record index record. do.

Then, the record index generation unit 1313 sorts the set of the key item value and the record position information in ascending order, for example, using the key item value as a key. Next, the record index generation unit 1313 acquires the position information (Pos.) Of each record index record in the record index. Such position information (Pos.) Is record index record position information.

Here, the record / index record position information (Pos.) Is the position information (Pos.) Of a record having the position information (Pos.), A set of a key item value and a record position information, and an array index record. Is preferable. That is, it is preferable that the record index record and the array index record are communicated for each record of the data source.

Next, the record index generation unit 1313 stores the record index record for each record in the data source 1301 in the record index storage unit 1123.

Further, the record index generation unit 1313 similarly forms a record index for other data sources (files “file2”, “file3”, etc.) and stores the record index in the record index storage unit 1123.

By the above processing, the record index of 1305 of FIG. 13 is accumulated in the record index storage unit 1123.
(5) Secondary index generation process

The secondary index generation unit 1314 reads the record index of the record index storage unit 1123.

Next, the secondary index generation unit 1314 skips a predetermined number (here, three), for example, the first, fourth, seventh, and so on, and the key item value (here, here) included in the record index record. , PID) and the record index record position information (Pos.) To acquire the secondary index record which is a set.

Next, the secondary index generation unit 1314 adds the acquired secondary index record to the secondary index storage unit 1124. In the secondary index, the secondary index records are sorted using the PID as a key.

Further, the secondary index generation unit 1314 similarly forms a secondary index for other data sources (files “file2”, “file3”, etc.) and stores them in the secondary index storage unit 1124.

By the above processing, the secondary index of 1306 in FIG. 13 is accumulated in the secondary index storage unit 1124.

(Specific example 2)
Now, it is assumed that the data source of 1401 of FIG. 14 is stored in the data source storage unit 111 of the data source management device 2 or the data source storage unit 111 of the search device 1.

In such a case, it is assumed that the user has input the search condition "Select PID, Age, Test, TestValue from data source where PID = 155 AND Test = TestC" in the terminal device 3. It is assumed that "Test" of "PID, Age, Test, TestValue" is an attribute value identifier, and "TestValue" is an attribute value.

Then, the terminal reception unit 32 of the terminal device 3 accepts such a search condition. Next, the terminal processing unit 33 configures the search condition to be transmitted. Next, the terminal transmission unit 34 transmits the search condition to the search device 1.

Next, the condition receiving unit 121 of the search device 1 receives the search condition "Select PID, Age, Test, TestValue from data source where PID = 155 AND Test = TestC".

Next, the search unit 132 of the search device 1 has the attributes of "PID", "Age", the attribute identifier "TestC", and the TestC in the record matching "PID = 155 AND Test = TestC" as follows. Get the value.

That is, first, the search unit 132 acquires "PID = 155" included in the search condition. Further, the search unit 132 acquires the attribute value identifier "TestC" included in the search condition (1406 in FIG. 14).

Next, the search unit 132 refers to the source index (1402) and sandwiches the acquired "PID = 155" between Min (minimum key item value) and Max (maximum key item value). The record is detected and the source identifier "File1" possessed by the source index record is acquired.

Further, the search unit 132 refers to the secondary index (1403) corresponding to the source identifier "File1", detects the PIDs "029" and "236" having "PID = 155" in between, and detects the PID "029" and "236". The record index record position information (1) and (151) paired with "029" and "236" are acquired from the secondary index (1403).

Next, the search unit 132 refers to the record index (1404) corresponding to the source identifier “File1”, and sets between the record index record position information (1) and (151), for example, “PID = 155”. Is used as a key for a binary search, and a record index record containing "PID = 155" is detected. Then, the search unit 132 acquires the record position information (241) paired with "PID = 155" from the record index record. The search unit 132 may detect a record index record including "PID = 155" by performing a sequential search instead of a binary search.

Next, the search unit 132 temporarily stores the acquired record position information (241) and the record index record position information (101) in a buffer (not shown).

Next, the search unit 132 refers to the array label index (1405) corresponding to the source identifier "File1", and uses the attribute identifier "TestC" included in the search condition as a key to perform a binary search for the array label index. , Detects the attribute identifier "TestC" and acquires the attribute order information (3) paired with the attribute identifier "TestC". Here, the search unit 132 may acquire the attribute order information (3) by performing a sequential search instead of a binary search.

Next, the search unit 132 refers to the array index corresponding to the source identifier "File1", and sandwiches the attribute order information (3) in the array index with the first attribute order information (1) and the first. Acquire the second attribute order information (4).

Next, the search unit 132 acquires the attribute value position information (54) corresponding to the first attribute order information (1) from the record index corresponding to the record index record position information (101) of the buffer (not shown). However, it is temporarily stored in a buffer (not shown). Further, the search unit 132 acquires the attribute value position information (84) corresponding to the record index record position information (101) and the second attribute order information (4) from the record index, and is not shown. Temporarily accumulate in the buffer.

Next, the search unit 132 accesses the data source identified by the source identifier "File1" and opens the file.

Next, the search unit 132 acquires the record position information (241), the attribute value position information (54), and the attribute value position information (84) from a buffer (not shown), and the record position information (241) specifies the record position information (241). The attribute value "0.381", which is an attribute value between the attribute value position information (54) and the attribute value position information (84) in the position record and corresponds to the attribute order information (3), is the relevant. Get from the file. Further, the search unit 132 acquires Age "62" from the file in the record at the position specified by the record position information (241).

Then, the search unit 132 constitutes a search result having a PID "155", an Age "62", an attribute value identifier "TestC", and an attribute value "0.381".

Next, the result output unit 141 transmits the configured search result to the terminal device 3. The search result is, for example, 1407 in FIG.

Next, the terminal receiving unit 35 of the terminal device 3 receives the search result. Next, the terminal processing unit 33 configures the search result to be output by using the received search result. Next, the terminal output unit 36 outputs the search result.

(Specific example 3)
Now, it is assumed that the data source of 1301 of FIG. 13 is stored in the data source storage unit 111 of the data source management device 2 or the data source storage unit 111 of the search device 1.

In such a case, it is assumed that the user has input the search condition "Select PID, Age, Test, TestValue from data source where PID = 155 AND Test = TestC" in the terminal device 3.

Then, the terminal reception unit 32 of the terminal device 3 accepts such a search condition. Next, the terminal processing unit 33 configures the search condition to be transmitted. Next, the terminal transmission unit 34 transmits the search condition to the search device 1.

Next, the condition receiving unit 121 of the search device 1 receives the search condition "Select PID, Age, Test, TestValue from data source where PID = 155 AND Test = TestC".

Next, the search unit 132 of the search device 1 has the attributes of "PID", "Age", the attribute identifier "TestC", and the TestC in the record matching "PID = 155 AND Test = TestC" as follows. Get the value.

That is, first, the search unit 132 acquires "PID = 155" included in the search condition. Further, the search unit 132 acquires the attribute value identifier "TestC" included in the search condition.

Next, the search unit 132 refers to the source index (1302) and acquires the source identifier “File1” corresponding to the acquired “PID = 155” and “TestC”.

After that, the search unit 132 obtains a search result by the same process as that described in the second embodiment.

Next, the result output unit 141 transmits the configured search result to the terminal device 3. The search result is, for example, 1307 in FIG.

Next, in response to the transmission of the search condition, the terminal receiving unit 35 receives the search result. Next, the terminal processing unit 33 configures the search result to be output by using the received search result. Next, the terminal output unit 36 outputs the search result.

As described above, according to the present embodiment, a desired attribute value can be searched at high speed from a data source having a large data size.

Further, according to the present embodiment, it is possible to search for a desired attribute value at high speed, particularly for a data source having a very long record length.

Further, according to the present embodiment, an index for high-speed information retrieval can be automatically generated.

Further, according to the present embodiment, it is possible to automatically generate an index for high-speed information retrieval, particularly for a data source having a very long record length.

Further, according to the present embodiment, the index in the latest state can be maintained.

Further, the processing in the present embodiment may be realized by software. Then, this software may be distributed by software download or the like. Further, this software may be recorded on a recording medium such as a CD-ROM and disseminated. It should be noted that this also applies to other embodiments herein. The software that realizes the search device 1 in the present embodiment is the following program. That is, this program has a data source storage unit that stores a data source containing two or more records having a key item value and two or more attribute values, and one or more records out of two or more records. And for each one or more attributes of each record, a search condition that includes an attribute identifier for a computer that can access the array index storage unit that stores the array index that has the attribute position information that identifies the position where the attribute value exists. And the attribute position information corresponding to the attribute identifier of the search condition are acquired from the array index, and the attribute value corresponding to the attribute identifier of the search condition is used by using the attribute position information. Is a program for functioning as a search unit acquired from the data source and a result output unit that outputs a search result including the attribute value acquired by the search unit.

(Embodiment 2)
In the present embodiment, a search system including a search device that acquires information from two or more data sources, integrates the information, and outputs the information by using a data dictionary having a three-layer schema structure will be described.

FIG. 15 is a conceptual diagram of the search system B according to the present embodiment. The search system B includes a search device 4, one or more data source management devices 2, and one or more terminal devices 3.

The search device 4 is a device for searching information from a data source. The search device 4 is, for example, a so-called server, for example, a cloud server, an ASP server, or the like. The type of the search device 4 does not matter.

In addition, each data source management device 2 of 1 or 2 or more is usually a device different from the search device 4.

Further, the search device 4 and the data source management device 2 of 1 or more can communicate with each other via a network such as the Internet or a LAN. Further, the search device 4 and the terminal device 3 can communicate with each other via a network such as the Internet or a LAN.

FIG. 16 is a block diagram of the search system B according to the present embodiment. FIG. 17 is a block diagram of the search device 4.

The search device 4 includes a storage unit 41, a reception unit 12, a processing unit 43, and an output unit 44. The storage unit 41 includes an index storage unit 112 and a dictionary storage unit 411. The processing unit 43 includes an index generation unit 131, a search unit 432, and an index update unit 133. The search unit 432 includes source determination means 4321, instruction generation means 4322, source search means 4323, and integration means 4324. The output unit 44 includes a result output unit 441.

The data source of the data source storage unit 111 constituting the data source management device 2 has one or more tables. The data source may be one file, but may be composed of two or more files. The table may be one file, but a plurality of tables may exist in one file. The structure of the data source and the table can be various and does not matter.

Data sources include, for example, relational databases, object-oriented databases, XML databases, NoSQL databases, file data sources, data warehouses, data marts, directory management systems, real-time measurement data, online data services, streaming data services. It is one of the above, and the type does not matter.

Various types of information are stored in the storage unit 41 that constitutes the search device 4. The various types of information are, for example, one or more types of indexes described above, and various types of information in a data dictionary described later.

A data dictionary is stored in the dictionary storage unit 411. A data dictionary is a set of information for acquiring information from two or more data sources and integrating the information by using a search condition input by a user. The data dictionary has source layer definition information, user layer definition information, and conversion rule definition information. That is, the data dictionary has three layers of information.

Source layer definition information is information that defines the schema of the data source. The source layer definition information includes, for example, a source identifier and one or more source attribute definition information. The source layer definition information includes, for example, a source identifier, a table identifier, and one or more source attribute definition information.

Source attribute definition information is information that defines the attributes of a table in a data source. The source attribute definition information has a source attribute identifier. The source attribute identifier is information that identifies an attribute of a table in a data source, and is, for example, an attribute name or an ID. The source attribute definition information may have one or more attribute values of the table attributes in the data source. One or more attribute values of the attribute are, for example, a data type and a size.

The source layer definition information is the information corresponding to the table. If there is only one table in the data source, the source layer definition information is the information corresponding to the data source.

It is preferable that the source layer definition information has data source specific information. Data source-specific information is information specific to each data source. The data source specific information includes, for example, instruction source information and connection information.

The instruction source information is information for generating a search instruction for a data source. The instruction source information is information for constructing a search instruction. It is preferable that the command source information corresponding to each of the two or more data sources is of a different type. Further, each of the two or more different instruction source information includes, for example, information for generating a search command of SQL statement, information for generating a search module, and URL syntax indicating a syntax including a search destination URL. Is suitable.

The instruction source information is, for example, information for constructing an SQL statement issued to a data source. The instruction source information is, for example, information that identifies the API of the module used when accessing the data source. The instruction source information is, for example, a URL syntax, for example, a character string having a URL and an endpoint (table identifier).

Connection information is information for accessing a data source. The connection information includes, for example, an IP address and a URL. The connection information includes, for example, login information for logging in to a data source. The login information includes, for example, a user identifier and a password. The connection information includes, for example, data source driver identification information and API key.

User layer definition information is information that defines the schema of the user table. The user table is the target of the search based on the search conditions entered by the user. A user table is usually a view, which contains one or more records. Further, such a record has one or more attribute values. It is preferable that the record has one or more key item values.

The user layer definition information includes, for example, a user table identifier and one or more user attribute definition information. The user table identifier is information that identifies the user table, and is, for example, a table name or an ID. User attribute definition information is information that defines the attributes of the user table. The user attribute definition information includes the user attribute identifier. The user attribute identifier is information that identifies the attribute of the user table. The user attribute identifier is, for example, an attribute name or an attribute ID.

The user attribute definition information usually has user attribute value source information. The user attribute value source information is information that specifies a method for acquiring a user attribute value. The user attribute value source information is information using one or more view attribute values of one or more converted views. The user attribute value source information has, for example, a view identifier and a view attribute identifier. The user attribute value source information may have, for example, a user table identifier and a user attribute identifier.

The user attribute value source information may have an arithmetic expression or the like. An arithmetic expression or the like is an arithmetic expression or a program identifier. When the user attribute value source information has an arithmetic expression or the like, the user attribute value source information is one or more of the view identifier of one or more of the transformed views or the source identifier of any of two or more data sources. It has an identifier of 1 and an attribute identifier paired with each of the 1 or 2 or more identifiers. The attribute identifier paired with each of one or more identifiers is one or more attribute identifiers of one or more of the view attribute identifiers of any of the transformed views or the source attribute identifiers of any of two or more data sources. .. The arithmetic expression or program identifier is an identifier of the arithmetic expression or program that accepts and executes one or more attribute values corresponding to one or more attribute identifiers as parameters. The program identifier is, for example, a module name, a function name, or a method name.

For the conversion rule definition information, the search unit 432 generates a search command to be issued to each of two or more data sources based on the accepted search conditions, acquires the search result corresponding to the search command, and obtains the search result. This is information for creating integrated data corresponding to the search conditions.

The conversion rule definition information has one or more conversion view information. The transformed view information is information that defines a transformed view configured by using one or more data sources out of two or more data sources. The conversion view is a view showing the correspondence between the user table and one or more data sources. The transformed view may contain one or more records with one or more view attribute values. It is preferable that the view attribute value of 1 or more includes the key item value. Transformed views are usually information that is not directly searched by the user. Also, one transform view information usually corresponds to one data source.

The transformed view information has one or more view attribute definition information. The transformed view information usually has a view identifier. View attribute definition information is information that defines the attributes of the transformed view. The view attribute definition information includes a view attribute identifier and view attribute definition information. The view attribute identifier is information that identifies the attribute of the transformed view. The view attribute identifier is, for example, an attribute name of the conversion view or an ID of the attribute of the conversion view.

The view attribute value source information is information that specifies the acquisition method of the view attribute value. The view attribute value source information has, for example, a source identifier and a source attribute identifier of the data source from which the view attribute value is acquired.

The view attribute value source information corresponds to one or more attribute identifiers of the source attribute identifier of any one or more data sources or the view attribute identifier of one or more transformation views and the one or more attribute identifiers. It has an arithmetic expression or the like whose parameter is the attribute value to be used. An arithmetic expression or the like is an arithmetic expression or a program identifier. The program identifier can be executed with an attribute value of 0 or 1 or more as a parameter, and is identification information of a program for acquiring a view attribute value. The program in which the attribute value to be given is 0 is, for example, "TODAY ()" for acquiring today's date and "TIME ()" for acquiring the current time.

The conversion rule definition information may have a join method identifier. The join method identifier is information that specifies a method for joining two or more search results acquired based on two or more conversion view information. The binding method identifier is, for example, "UNION", "CHOICE", and "LOOKUP". It is preferable that the two or more combination method identifiers that the conversion rule definition information can include are two or more of "UNION", "CHOICE", and "LOOKUP". Further, it is preferable that the combination method identifier that can be included in the conversion rule definition information is 3 or more including "UNION", "CHOICE", and "LOOKUP".

"UNION" is information that specifies the merge process. In the merge process, one record is composed by grouping two or more search results with one or two or more key items and aggregating two or more attribute values of each one or two or more non-key items. It is a process to do.

In addition, to aggregate two or more attribute values is to perform a predetermined operation on two or more attribute values and acquire one value. The predetermined calculation is, for example, calculation of total value (SUM), calculation of average value (Average), acquisition of maximum value (MAX), acquisition of minimum value (MIN), acquisition of median (MEDIAn), standard deviation. Calculation, etc.

"CHOICE" is information that specifies the selection process. In the selection process, one or more search results are selected from two or more search results according to the priority order, and two or more attribute values of each one or two or more non-key items are aggregated to obtain one record. It is a process to configure. The priority is a priority for search results from two or more conversion views or two or more data sources, and is stored in, for example, the storage unit 41. The conversion rule definition information may include a priority.

"LOOKUP" is information that specifies the complement processing. The completion process identifies one search result to be referenced and another search result to be referenced according to the reference condition, and refers to the attribute value of the key item of the one reference search result among the two or more search results. It is an attribute value of a key item included in other search results, and an attribute value of a key item not included in one search result is added, and two or more attribute values of one or two or more non-key items are added. Is a process that constitutes one record by aggregating. The reference condition is information for specifying one or more attribute values acquired from the search result, and is, for example, one or more attribute identifiers.

The processing unit 43 performs various processes. The various processes are, for example, processes performed by the index generation unit 131, the search unit 432, and the index update unit 133.

The search unit 432 refers to the dictionary storage unit 411 and determines two or more data sources corresponding to the search conditions accepted by the reception unit 12. To determine two or more data sources is to acquire two or more source identifiers. Also, the determination of two or more data sources does not have to be done together.

Then, the search unit 432 generates a search command for each of the two or more determined data sources using the conversion rule definition information, and acquires the search result based on the search command. Then, the search unit 432 integrates the search results corresponding to each of the two or more acquired data sources by using the conversion rule definition information and the user layer definition information, and acquires the integrated data corresponding to the search conditions.

For example, when the search unit 432 acquires the view attribute value corresponding to the view attribute value source information, the search unit 432 obtains the attribute value corresponding to each one or more attribute identifiers of the view attribute value source information as a data source or a conversion view. Get from. Next, the search unit 432 gives the acquired one or more attribute values to the program identified by the arithmetic expression or the program identifier, executes the arithmetic expression or the program, and acquires the view attribute value. Each one or more attribute identifiers of the view attribute value source information is a source attribute identifier or a view attribute identifier. Further, the attribute value corresponding to each one or more attribute identifiers of the view attribute value source information is a source attribute value or a view attribute value.

For example, when the search unit 432 acquires the user attribute value corresponding to the user attribute value source information, the search unit 432 obtains the attribute value corresponding to each one or more attribute identifiers of the user attribute value source information in a data source or conversion view. Get from. Next, the search unit 432 gives the acquired one or more attribute values to the program identified by the arithmetic expression or the program identifier, executes the arithmetic expression or the program, and acquires the user attribute value. In addition, each one or more attribute identifiers possessed by the user attribute value source information is a source attribute identifier or a view attribute identifier. Further, the attribute value corresponding to each one or more attribute identifiers of the user attribute value source information is a source attribute value or a view attribute value.

The search unit 432 generates, for example, a search command for acquiring information from two or more data sources according to the command source information for each of the two or more data sources. Next, the search unit 432 acquires the search result based on the search instruction for each of the two or more data sources from the corresponding data source. Next, the search unit 432 integrates the search results corresponding to each of the two or more data sources by using the conversion rule definition information and the user layer definition information, and acquires the integrated data corresponding to the search conditions.

The search unit 432 generates, for example, a search command which is an SQL statement according to the command source information for the data source corresponding to the SQL statement according to the command source information for each of two or more data sources. Further, the search unit 432 generates, for example, a search command which is an interface of the search module according to the command source information for the data source corresponding to the search module. Then, the search unit 432 acquires the search result based on each search command for each of the two or more data sources. Next, the search unit 432 integrates the search results corresponding to each of the two or more data sources by using the conversion rule definition information and the user layer definition information, and acquires the integrated data corresponding to the search conditions.

The search unit 432 accesses the data source corresponding to the connection information by using the connection information for each of two or more data sources, and acquires the search result based on the search command from the data source. Next, the search unit 432 integrates the search results corresponding to each of the two or more data sources by using the conversion rule definition information and the user layer definition information, and acquires the integrated data corresponding to the search conditions.

The search unit 432 acquires, for example, the join method identifier possessed by the conversion rule definition information, combines two or more search results according to the join method specified by the join method identifier, and acquires integrated data.

The search unit 432 acquires the attribute position information corresponding to the attribute identifier of the search condition from the array index, and uses the attribute position information to acquire the attribute value corresponding to the attribute identifier of the search condition from the data source. Configure integrated data with attribute values. When the data source to be searched is a data source having the structure described in the first embodiment, when the search unit 432 acquires information from the data source, the search unit 432 operates in the same manner as the search unit 132. do. That is, the search unit 432 acquires information from the data source by using one or more types of index information of the index storage unit 112. Since the search process of the search unit 432 has been described as the process of the search unit 132 in the first embodiment, the description thereof is omitted here.

The source determination means 4321 acquires one or more user attribute identifiers included in the search condition, and acquires the user attribute value source information corresponding to each of the one or more user attribute identifiers. Next, the source determination means 4321 acquires one or more view attribute identifiers corresponding to the one or more user attribute value source information. Next, the source determination means 4321 acquires the source identifier corresponding to each of the one or more view attribute identifiers from the view attribute definition information. It is preferable that the source determining means 4321 performs unique processing on the acquired source identifier to acquire one or more unique source identifiers.

The instruction generation means 4322 uses the search condition and the view attribute value source information to generate a search instruction for each data source identified by each of the two or more source identifiers acquired by the source determination means 4321.

The instruction generation means 4322 generates a search instruction for each data source according to the instruction source information for each of two or more data sources.

When the instruction source information includes the syntax information of the SQL statement, the instruction generation means 4322 generates the SQL statement according to the syntax information of the SQL statement based on the search condition.

When the instruction source information includes the syntax information of the interface of the search module, the instruction generation means 4322 is a character string for executing the search module according to the syntax information of the interface of the search module based on the search condition. Generate a search command.

When the instruction source information has a URL syntax, the instruction generation means 4322 is based on the search condition.
In addition to the URL and endpoint (table identifier) that the URL syntax has, a search command that is a character string having the condition part that the search condition has is generated.

The source search means 4323 acquires a search result based on the search instruction acquired by the instruction generation means 4322 for each of the two or more data sources. The source search means 4323, for example, executes each of two or more search commands and acquires search results from the corresponding data source.

The integration means 4324 acquires integrated data in which the search results for each of the two or more data sources acquired by the source search means 4323 are integrated by using the search conditions and the user layer definition information.

The integration means 4324 combines two or more search results and acquires integrated data according to the combination method specified by the combination method identifier of the conversion rule definition information stored in the dictionary storage unit 411, for example.

When the binding method identifier is "UNION", the integration means 4324 selects one or more search results from two or more search results according to the priority, and two or more of one or two or more non-key items. The attribute values of are aggregated and the merge process that constitutes one record is performed.

When the combination method identifier is "CHOICE", the integration means 4324 selects the attribute value of the key item included in one or more search results from two or more search results according to the priority, and the non-key item. The selection process that constitutes one record is performed by aggregating two or more attribute values. The priority is information that identifies one or more conversion views or one or more data sources that are prioritized from among two or more conversion views or two or more data sources. Further, the priority order is stored in the storage unit 41.

When the binding method identifier is "LOOKUP", the integration means 4324 identifies one search result to be referred to and another search result to be referred to according to a reference condition, and refers to two or more search results. To the attribute value of the key item of one search result, the attribute value of the key item that is the attribute value of the key item included in the other referenced search results and is not included in the one search result is added, and 1 or 1 or Complement processing that constitutes one record is performed by aggregating two or more attribute values of each of two or more non-key items. The reference condition is information that identifies one search result to be referred to and another search result to be referred to. The reference condition is, for example, "<reference view identifier> identifier 1 <non-reference view identifier> identifier 2". Further, the reference condition is stored in the storage unit 41.

The output unit 44 outputs various information. The various types of information are, for example, integrated data. Further, the output here is usually transmission to the terminal device 3, but display on a display, projection using a projector, printing by a printer, sound output, storage on a recording medium, and other processing devices. It may be a concept including delivery of the processing result to or other programs.

The result output unit 441 outputs the integrated data acquired by the search unit 432.

Next, an operation example of the search device 4 constituting the search system B will be described with reference to the flowchart of FIG. Here, among the processes of the search device 4, the process of generating an index has been described in the first embodiment, and thus the description thereof will be omitted here. Here, the search process performed by the search device 4 will be described.

(Step S1801) The condition reception unit 121 determines whether or not the search condition has been accepted. If the search condition is accepted, the process goes to step S1802, and if the search condition is not accepted, the process returns to step S1801.

(Step S1802) The source determination means 4321 acquires the user table identifier included in the search condition accepted in step S1801. This user table identifier is an identifier of the user table to be searched.

(Step S1803) The source determination means 4321 acquires one or more user attribute identifiers included in the search condition accepted in step S1801.

The user attribute identifier may exist in any of the condition part, the extraction part, the other part, and the like in the search condition. The condition part is a place where the condition in the search condition is described. The extraction unit is a place in the search condition in which the attribute values constituting the integrated data are described. The other parts are parts other than the condition part and the extraction part.

The search conditions are "SELECT product ID, product name, SUM (sales quantity), SUM (sales amount), SUM (purchase amount), SUM (sales profit) FROM sales profit by product WHERE product ID = 1103 GROUP BY product ID, In the case of "product name", the condition part is "product ID = 1103", and the extraction part is "product ID, product name, SUM (sales quantity), SUM (sales amount), SUM (purchase amount), SUM (sales profit)". ) ”, The other part is the“ product ID, product name ”in the“ GROUP BY ”phrase.

(Step S1804) The source determination means 4321 substitutes 1 for the counter i.

(Step S1805) The source determination means 4321 determines whether or not the i-th user attribute identifier exists among the user attribute identifiers acquired in step S1803. If the i-th user attribute identifier exists, the process goes to step S1806, and if the i-th user attribute identifier does not exist, the process goes to step S1808.

(Step S1806) The source determination means 4321 acquires the user attribute value source information paired with the i-th user attribute identifier from the source layer definition information.

(Step S1807) The source determination means 4321 increments the counter i by 1. Return to step S1805.

(Step S1808) The source determination means 4321 acquires the view identifier from all the user attribute value source information acquired in step S1806. Note that the one or more user attribute value source information may have a user table identifier instead of a view identifier.

(Step S1809) The source determination means 4321 performs unique processing on the view identifier acquired in step S1808, and acquires one or more view identifiers of each transformed view necessary for acquiring integrated data.

(Step S1810) The source determination means 4321 substitutes 1 for the counter j.

(Step S1811) The source determination means 4321 determines whether or not the j-th view identifier exists among the view identifiers acquired in step S1809. If the j-th view identifier exists, the process goes to step S1812, and if the j-th view identifier does not exist, the process goes to step S1819.

(Step S1812) The source determination means 4321 substitutes 1 for the counter k.

(Step S1813) The source determination means 4321 determines whether or not the k-th view attribute identifier paired with the j-th view identifier exists in the user attribute value source information acquired in step S1806. If the k-th view attribute identifier exists, the process goes to step S1814, and if the k-th view attribute identifier does not exist, the process goes to step S1818. The kth view attribute identifier here is a unique view attribute identifier. That is, the same view attribute identifier is not acquired in this step. Further, the k-th view attribute identifier may be a user attribute identifier.

(Step S1814) The source determination means 4321 acquires the k-th view attribute identifier paired with the j-th view identifier from the user attribute value source information acquired in step S1806. Next, the source determination means 4321 obtains the k-th view attribute value source information paired with the k-th view attribute identifier from the converted view information paired with the j-th view identifier in the conversion rule definition information. get.

The k-th view attribute identifier may be a user attribute identifier. In the case of a user attribute identifier, the source determination means 4321 acquires the user attribute value source information paired with the user attribute identifier, and the view paired with the view identifier and the view attribute identifier included in the user attribute value source information. Get the attribute value source information.

(Step S1815) The source determination means 4321 increments the counter k by 1. Return to step S1813.

(Step S1816) The source determination means 4321 uses the one or more view attribute value source information acquired in step S1814 to generate a search instruction corresponding to the jth view identifier. An example of such an instruction generation process will be described with reference to the flowchart of FIG.

(Step S1817) The source search means 4323 uses the search instruction generated in step S1816 to acquire a search result from the data source corresponding to the j-th view identifier.

(Step S1818) The source determination means 4321 increments the counter j by 1. Return to step S1811.

(Step S1819) The integration means 4324 integrates the search results acquired in step S1817 and acquires integrated data. An example of such integrated processing will be described with reference to the flowchart of FIG.

(Step S1820) The result output unit 441 outputs the integrated data acquired in step S1819. Return to step S1801.

In the flowchart of FIG. 18, the process is terminated by turning off the power or interrupting the end of the process.

Next, an example of the instruction generation process in step S1816 will be described with reference to the flowchart of FIG.

(Step S1901) The instruction generation means 4322 acquires the instruction source information from the data source specific information of the source layer definition information of the data source corresponding to the j-th view identifier of S1811.

(Step S1902) The instruction generation means 4322 analyzes the accepted search condition and acquires the information of the condition unit, the extraction unit, and the other unit of the search condition.

The process of analyzing the search condition can be realized by a known technique such as SQL statement processing software.

(Step S1903) The instruction generation means 4322 substitutes 1 for the counter i.

(Step S1904) The instruction generation means 4322 determines whether or not the i-th view attribute value source information corresponding to the condition unit acquired in step S1902 exists. If the i-th view attribute value source information corresponding to the condition unit exists, the process goes to step S1905, and if it does not exist, the process goes to step S1907.

(Step S1905) The instruction generation means 4322 acquires the source attribute identifier possessed by the i-th view attribute value source information corresponding to the condition unit acquired in step S1902.

(Step S1906) The instruction generation means 4322 increments the counter i by 1. Return to step S1904.

(Step S1907) The instruction generation means 4322 uses the one or more source attribute identifiers acquired in step S1905 and the condition unit in the accepted search conditions, and uses the search instruction according to the instruction source information acquired in step S1901. Get the information of the condition part of.

(Step S1908) The instruction generation means 4322 substitutes 1 for the counter j.

(Step S1909) The instruction generation means 4322 determines whether or not the j-th view attribute value source information corresponding to the extraction unit acquired in step S1902 exists. If the j-th view attribute value source information corresponding to the extraction unit exists, the process goes to step S1910, and if it does not exist, the process goes to step S1912.

(Step S1910) The instruction generation means 4322 acquires the source attribute identifier possessed by the j-th view attribute value source information corresponding to the extraction unit acquired in step S1902.

(Step S1911) The instruction generation means 4322 increments the counter j by 1. Return to step S1909.

(Step S1912) The instruction generation means 4322 uses the one or more source attribute identifiers acquired in step S1910 and the extraction unit in the accepted search conditions, and uses the search command according to the instruction source information acquired in step S1901. Get the information of the extraction part of.

(Step S1913) The instruction generation means 4322 substitutes 1 for the counter k.

(Step S1914) The instruction generation means 4322 determines whether or not the k-th view attribute value source information corresponding to the other part acquired in step S1902 exists. If the kth view attribute value source information corresponding to the other part exists, the process goes to step S1915, and if it does not exist, the process goes to step S1917.

(Step S1915) The instruction generation means 4322 acquires the source attribute identifier possessed by the k-th view attribute value source information corresponding to the other part acquired in step S1902.

(Step S1916) The instruction generation means 4322 increments the counter k by 1. Return to step S1914.

(Step S1917) The instruction generation means 4322 uses the one or more source attribute identifiers acquired in step S1915 and the other part in the accepted search conditions, and uses the search instruction according to the instruction source information acquired in step S1901. Get information about other parts of. In addition, here, the information of other parts may not be acquired.

(Step S1918) The instruction generation means 4322 uses the information of the condition unit acquired in step S1907, the information of the extraction unit acquired in step S1912, and the information of the other unit acquired in step S1917, and the instruction source acquired in step S1901. Configure search instructions based on the information. Return to higher-level processing.

If the information of the other part is not acquired in step S1917, the instruction generation means 4322 configures the search command by using the information of the condition part acquired in step S1907 and the information of the extraction unit acquired in step S1912. ..

Next, an example of the integration process in step S1819 will be described with reference to the flowchart of FIG.

(Step S2001) The integration means 4324 substitutes 1 for the counter i.

(Step S2002) The integration means 4324 determines whether or not each search result to be combined includes the i-th record. If the i-th record is included, the process goes to step S2003, and if the i-th record is not included, the process returns to higher-level processing.

(Step S2003) The integration means 4324 determines whether or not the conversion rule definition information includes the join method identifier. If the join method identifier is not included, the process goes to step S2004, and if the join method identifier is included, the process goes to step S2015.

(Step S2004) The integration means 4324 substitutes 1 for the counter j.

(Step S2005) The integration means 4324 determines whether or not the j-th user attribute identifier used for the integration data exists. If the j-th user attribute identifier exists, the process goes to step S2004, and if it does not exist, the process goes to step S2013.

(Step S2006) The integration means 4324 acquires the user attribute value source information paired with the jth user attribute identifier from the user layer definition information.

(Step S2007) The integration means 4324 determines whether or not an arithmetic expression or the like exists in the user attribute value source information acquired in step S2006. If an arithmetic expression or the like exists, it goes to step S2008, and if it does not exist, it goes to step S2011.

(Step S2008) The integration means 4324 acquires one or more view attribute identifiers in the user attribute value source information acquired in step S2006. Next, the integration means 4324 acquires the attribute value corresponding to one or more attribute identifiers from the i-th record of the search result acquired in S1817. It should be noted that each one or more attribute identifiers includes one or more view attribute identifiers. Each one or more attribute identifiers may include one or more user attribute identifiers.

(Step S2009) The integration means 4324 acquires an arithmetic expression or the like in the user attribute value source information acquired in step S2006.

(Step S2010) The integration means 4324 substitutes each one or more attribute values acquired in step S2008 into the arithmetic expression or the like acquired in step S2009, executes the arithmetic expression or the like, and acquires the user attribute value. Go to step S2010.

(Step S2011) The integration means 4324 acquires the user attribute value from the i-th record of the search result.

(Step S2012) The integration means 4324 increments the counter j by 1. Return to step S2005.

(Step S2013) The integration means 4324 acquires the view attribute identifier of the user attribute value source information acquired in step S2006. Next, the integration means 4324 acquires the view attribute value corresponding to the view attribute identifier from the i-th record of the search result acquired in S1817, and constitutes a record of the integrated data.

(Step S2014) The integration means 4324 increments the counter i by 1. Return to step S2002.

(Step S2015) The integration means 4324 performs the join method identifier processing and integrates the search results. An example of the combination method identifier processing will be described with reference to the flowcharts of FIGS. 21 and 22.

(Step S2016) The integration means 4324 increments the counter i by 1. Return to step S2002.

Next, an example of the combination method identifier processing in step S2012 will be described with reference to the flowcharts of FIGS. 21 and 22. The join method identifier process here is a process corresponding to the i-th record of interest (the i-th record of S2002).

(Step S2101) The integration means 4324 determines whether or not the join method identifier included in the conversion rule definition information is “UNION”. If it is "UNION", it goes to step S2102, and if it is not "UNION", it goes to step S2113.

(Step S2102) The integration means 4324 acquires a set of attribute values of one or more key items from the search result.

(Step S2103) The integration means 4324 substitutes 1 for the counter i.

(Step S2104) The integration means 4324 determines whether or not the i-th non-key item exists. If the i-th non-key item exists, the process goes to step S2105, and if it does not exist, the process goes to step S2108.

(Step S2105) The integration means 4324 acquires all attribute values for the i-th non-key item.

(Step S2106) The integration means 4324 aggregates all the attribute values acquired in step S2105 and acquires the attribute value for the i-th non-key item included in the integrated data.

(Step S2107) The integrating means 4324 increments the counter i by 1. Return to step S2104.

(Step S2108) The integration means 4324 is a record having the attribute value acquired in step S2102 and the attribute value acquired in step S2106, and constitutes a record constituting the integrated data. Return to higher-level processing.

(Step S2109) The integration means 4324 determines whether or not the join method identifier included in the conversion rule definition information is “CHOICE”. If it is "CHOICE", it goes to step S2110, and if it is not "CHOICE", it goes to step S2118.

(Step S2110) The integration means 4324 acquires the priority from the storage unit 41.

(Step S2111) The integration means 4324 determines the preferred conversion view using the priority order acquired in step S2110, and acquires the attribute values of one or more key items of the conversion view.

(Step S2112) The integration means 4324 substitutes 1 for the counter i.

(Step S2113) The integration means 4324 determines whether or not the i-th non-key item exists. If the i-th non-key item exists, the process goes to step S2114, and if it does not exist, the process goes to step S2117.

(Step S2114) The integration means 4324 acquires all attribute values for the i-th non-key item.

(Step S2115) The integration means 4324 aggregates all the attribute values acquired in step S2114 and acquires the attribute value for the i-th non-key item included in the integrated data.

(Step S2116) The integration means 4324 increments the counter i by 1. Return to step S2113.

(Step S2117) The integration means 4324 is a record having the attribute value acquired in step S2111 and the attribute value acquired in step S2115, and constitutes a record constituting the integrated data. Return to higher-level processing.

(Step S2118) The integration means 4324 determines whether or not the join method identifier included in the conversion rule definition information is “LOOKUP”. If it is "LOOKUP", it goes to step S2119, and if it is not "LOOKUP", it returns to the higher processing.

(Step S2119) The integration means 4324 acquires a reference condition from the storage unit 41.

(Step S2120) The integration means 4324 determines a conversion view on the side that refers to the reference condition. Then, the integration means 4324 acquires the attribute values of one or more key items of the conversion view.

(Step S2121) The integration means 4324 determines the conversion view on the side to which the reference condition is referenced. Then, the integration means 4324 acquires attribute values that are attribute values of one or more key items of the conversion view on the reference side and are not included in the set of attribute values of the conversion view on the reference side.

(Step S2122) The integration means 4324 substitutes 1 for the counter i.

(Step S2123) The integration means 4324 determines whether or not the i-th non-key item exists. If the i-th non-key item exists, the process goes to step S2124, and if it does not exist, the process goes to step S2127.

(Step S2124) The integration means 4324 acquires all attribute values for the i-th non-key item.

(Step S2125) The integration means 4324 aggregates all the attribute values acquired in step S2124 and acquires the attribute value for the i-th non-key item included in the integrated data.

(Step S2126) The integration means 4324 increments the counter i by 1. Return to step S2123.

(Step S2127) The integration means 4324 is a record having the attribute values acquired in step S2120, step S2121, and step S2125, and constitutes a record constituting the integrated data. Return to higher-level processing.

Hereinafter, a specific operation example of the search system B in the present embodiment will be described. The operation example here is an example of a process in which the search device 4 acquires search results from data sources stored in each of the two data source management devices 2, integrates the search results, and acquires integrated data. Is. Here, it is assumed that the two data source management devices 2 are different devices from the search device 4, and the two data source management devices 2 are different devices, respectively.

Then, it is assumed that the sales database shown in 2301 of FIG. 23 is stored in the data source storage unit 111 of the first data source management device 2. The sales database has a sales table (23011) and a product table (23012). The sales table (23011) manages one or more records having a "product ID", "customer ID", "sales unit price", and "sales quantity". The product table (23012) manages one or more records having a "product ID", a "product name", and a "product classification".

Further, it is assumed that the purchase database shown in 2302 of FIG. 23 is stored in the data source storage unit 111 of the second data source management device 2. The purchase database here has a purchase table (23021). The purchase table (23021) manages one or more records having a "product ID", a "supplier", and a "purchase unit price".

Further, the dictionary storage unit 411 of the search device 4 stores a data dictionary having three layers of definition information shown in FIGS. 24 to 30. Such a data dictionary is, for example, information input by an administrator who operates the search device 4.

FIG. 24 is information that defines the schema of the sales table (23011) included in the source layer definition information. FIG. 24 has a source identifier “sales database”, a table identifier “sales table”, and one or more source attribute definition information. The source attribute definition information is identified by the "ID" in the table of FIG. 24. Here, the source attribute definition information has a “source attribute identifier”, a “data type”, and a “size”. The sales database is, for example, a relational database.

FIG. 25 is information that defines the schema of the product table (23012) included in the source layer definition information. FIG. 25 has a source identifier “sales database”, a table identifier “product table”, and one or more source attribute definition information. The source attribute definition information is identified by the "ID" in the table of FIG. Here, the source attribute definition information has a “source attribute identifier”, a “data type”, and a “size”.

FIG. 26 is information that defines the schema of the purchase table (23021) included in the source layer definition information. FIG. 26 has a source identifier “purchase database”, a table identifier “purchase table”, and one or more source attribute definition information. The source attribute definition information is identified by the "ID" in the table of FIG. The source attribute definition information has a "source attribute identifier" here. The purchase database is, for example, the file described in the first embodiment.

FIG. 27 is data source specific information included in the source layer definition information. 2701 in FIG. 27 is data source specific information of the sales database. 2702 is the data source specific information of the purchase database.

FIG. 28 is the conversion view information of the sales view, which is one of the conversion views. The conversion view information is included in the conversion rule definition information. This converted view information has a view identifier "sales view" and one or more view attribute definition information. The view attribute definition information is identified by the "ID" in the table of FIG. 28.

The view attribute definition information of "ID = 1" in FIG. 28 can be obtained even if the attribute value of the source attribute identifier "product ID" of the source identifier "sales table" is acquired when the view attribute identifier "product ID" is acquired. It indicates that the attribute value of the source attribute identifier "product ID" of the source identifier "product table" may be acquired. That is, the information paired with the source attribute identifier "product ID" of the source identifier "sales table" and the source attribute identifier "product ID" of the source identifier "product table" which has the same attribute value as the "product ID". Indicates that the paired information is information about the same product.

The view attribute definition information of “ID = 6” in FIG. 28 is obtained by multiplying the parameter P1 and the parameter P2 as shown by the calculation formula “P1 × P2” when the view attribute value “sales amount” is acquired. Means that. Further, in "ID = 6" in FIG. 28, it is shown that the parameter P1 is the attribute value of the source attribute identifier "sales unit price" of the source identifier "sales table". Further, it is shown that the parameter P2 is an attribute value of the source attribute identifier "sales quantity" of the source identifier "sales table".

FIG. 29 is the conversion view information of the purchase view, which is one of the conversion views. The conversion view information is included in the conversion rule definition information. This transformed view information has a view identifier "purchased view" and one or more view attribute definition information. The view attribute definition information is identified by the "ID" in the table of FIG. 29.

FIG. 30 is information that defines the schema of the user table included in the user layer definition information. The user layer definition information has a user table identifier "product sales profit table" and one or more user attribute definition information. The user attribute definition information is identified by the "ID" in the table of FIG.

The user attribute definition information of "ID = 1" in FIG. 30 can be obtained even if the attribute value of the view attribute identifier "product ID" of the view identifier "sales view" is acquired when the user attribute identifier "product ID" is acquired. It indicates that the attribute value of the view attribute identifier "product ID" of the view identifier "purchasing view" may be acquired. That is, the information paired with the view attribute identifier "product ID" of the view identifier "sales view" and the view attribute identifier "product ID" of the view identifier "purchase view" which has the same attribute value as the "product ID". Indicates that the information paired with is information about the same product.

Further, in the calculation formula “P1 × P2” of the view attribute definition information of “ID = 7” in FIG. 30, the parameter P1 and the parameter P2 are multiplied to obtain the attribute value of the user attribute identifier “purchase amount”. Show that. Further, it is shown that the parameter P1 is an attribute value of the view attribute identifier "sales quantity" of the view identifier "sales view". Further, it is shown that the parameter P2 is an attribute value of the view attribute identifier “purchase unit price” of the view identifier “purchase view”.

Further, the arithmetic expression "sub (P1, P2)" of the view attribute definition information of "ID = 8" in FIG. 30 is added to the function "sub" (a function that returns the result of subtracting two parameters), P1 and P2. It is shown that the attribute value of the user attribute identifier "sales profit" is acquired by substituting the values of the two parameters of (1) and executing the function. Further, it is shown that the parameter P1 is an attribute value of the view attribute identifier "sales amount" of the view identifier "sales view". Further, it is shown that the parameter P2 is an attribute value of the view attribute identifier "purchase amount" of the user table identifier "commodity sales profit table".

In the above situation, an operation example of the search device 4 will be described with reference to FIG. 31. First, the user inputs the search condition "SELECT product ID, product name, SUM (sales quantity), SUM (sales amount), SUM (purchase amount), SUM (sales profit)" to the terminal device 3.

FROM Sales profit by product

WHERE product ID = 1103

GROUP BY Product ID, Product Name "
Is entered. Next, the terminal device 3 receives the search condition and transmits it to the search device 4.

Next, the condition receiving unit 121 of the search device 4 receives the above search condition (SQL statement).
Next, the source determination means 4321 acquires the user table identifier "sales profit by product" included in the search condition. Further, the source determination means 4321 acquires the user attribute identifier "product ID", "product name", "sales quantity", "sales amount", "purchase amount", and "sales profit" included in the search condition.

Next, the source determination means 4321 acquires the user attribute definition information paired with each acquired user attribute identifier from the user layer definition information of FIG. 30.

Next, the source determination means 4321 acquires the view identifier of each acquired user attribute definition information, performs unique processing on the view identifier, and obtains two view identifiers "sales view" and "purchase view". get.

Next, the source determination means 4321 acquires the user attribute identifier "product ID", "product name", "sales quantity", and "sales amount" corresponding to the view identifier "sales view" from the acquired user attribute definition information. .. Next, the source determination means 4321 acquires the view attribute identifier "product ID", "product name", "sales quantity", and "sales amount" corresponding to each acquired user attribute identifier and view identifier "sales view".

Next, the source determining means 4321 refers to the converted view information of FIG. 28, and acquires the view attribute value source information paired with each acquired view attribute identifier.

Next, the instruction generation means 4322 acquires the instruction source information (information paired with the tag <command source information> of 2701) corresponding to the view identifier "sales view" from the data source specific information of FIG. 27.

Next, the command generation means 4322 analyzes the accepted search condition, and the condition unit "product ID = 1103" of the search condition, the extraction unit "product ID, product name, SUM (sales quantity), SUM (sales amount)". ), SUM (purchase amount), SUM (sales profit) ”, and information“ GROUP BY product ID, product name ”of other departments.

Next, the instruction generation means 4322 acquires the "sales view. Product ID" from the user attribute identifier "product ID" of the condition unit "product ID = 1103" by using the acquired user attribute value source information. .. Further, the instruction generation means 4322 acquires the "sales table. Product ID" from the "sales view. Product ID" by using the acquired view attribute value source information. Then, the instruction generation means 4322 acquires the condition unit "sales table. Product ID" for configuring the search command to be issued to the data source from the condition unit "product ID = 1103" of the search instruction.

Next, the command generation means 4322 similarly uses the "product ID" of the extraction unit "product ID, product name, SUM (sales quantity), SUM (sales amount), SUM (purchase amount), SUM (sales profit)". , "Sales table. Product ID" is acquired. Further, the instruction generation means 4322 acquires the "product table. Product name" from the "product name" constituting the extraction unit. Further, the instruction generation means 4322 acquires "SUM (sales table. Sales quantity)" from "SUM (sales quantity)" constituting the extraction unit. Further, the command generation means 4322 acquires "SUM (sales table.sales unit price x sales amount.sales amount)" from "SUM (sales amount)" constituting the extraction unit.

Next, the command generation means 4322 acquires "GROUP BY sales table. Product ID, product table. Product name" from the information "GROUP BY product ID, product name" of the other part.

Next, the instruction generation means 4322 has a table identifier "sales table" and a variable corresponding to the variable "$ table identifier 1 $" included in the "FROM $ table identifier 1 $ INNER JOIN $ table identifier 2 $" of the instruction source information. Acquire the table identifier "product table" corresponding to "$ table identifier 2 $".

Next, the instruction generation means 4322 uses the variable "$ table attribute identifier" included in the instruction source information "ON $ table identifier 1 $. $ Table attribute identifier 1 $ = $ table identifier 2 $. $ Table attribute identifier 2 $". Acquire the table attribute name "product ID" corresponding to "1 $" and the table attribute name "product ID" corresponding to the variable "$ table attribute identifier 2 $".

Next, the instruction generation means 4322 uses the instruction source information "SELECT $ extraction unit $.

FROM $ Table identifier 1 $

INNER JOIN $ Table identifier 2 $

ON $ Table identifier 1 $. $ Table attribute identifier $ = $ Table identifier 2 $. $ Table attribute identifier $

Replace each variable of "WHERE $ Condition part $ $ Other part $" with the acquired character string.
Search command "SELECT sales table. Product ID, product table. Product name,

SUM (sales table. Sales quantity),

SUM (Sales table. Sales unit price x Sales table. Sales amount)
FROM sales table INNER JOIN product table

ON sales table. Product ID = product table. Product ID;
WHERE sales table. Product ID = 1103
GROUP BY sales table. Product ID, product table. Product name"
To configure.

Next, the source search means 4323 acquires the connection information "<JDBC connection URL> jdbc: oracle: thin: @localhost: 1521: AAA <driver class> oracle.jdbc.driver.OracleDriver" in FIG. 27. Then, the source search means 4323 uses the connection information to access the SQL database "sales database", and uses the generated search command from the data source "sales database" corresponding to the view identifier. , Get search results. Then, the source search means 4323 obtains the search result "<product ID> 1103 <product name> Ipoh Coffee <sales quantity> 70 <sales amount> 14000".

Next, the instruction generation means 4322 acquires the "purchase view. Product ID" from the user attribute identifier "product ID" of the condition unit "product ID = 1103" by using the acquired user attribute value source information. do. Further, the instruction generation means 4322 acquires the "purchase table. Product ID" from the "purchase view. Product ID" by using the acquired view attribute value source information. Then, the command generation means 4322 receives a condition unit "purchase table. Product ID" for configuring a search command to be issued to the data source "purchase database" from the condition unit "product ID = 1103" of the search command. To get.

Further, the instruction generation means 4322 acquires "SUM (sales table.sales quantity x purchase table.purchase unit price)" from "SUM (purchase amount)" constituting the extraction unit. Next, the instruction generation means 4322 uses the information "purchase table. Purchase" corresponding to the data source "purchase database" in the extraction unit "SUM (sales table. Sales quantity x purchase table. Purchase unit price)". Get the unit price.

Next, the command generation means 4322 follows the command source information "base URL +" / "+ endpoint" and the base URL "https://xxx.yyyy-portal.co.jp" (FIG. 27, 2702) of the connection information. , Constructs the search command "GET https://xxx.yyyy-portal.co.jp/purchase table? Product ID = 1103".

Next, the source search means 4323 uses the connection information "<API key> XXXXXXXX" in FIG. 271 and the search command "GET https://xxx.yyyy-portal.co.jp/purchase table? Product ID". = 1103 "is used to search the purchase table (23021) in the purchase database, and the search result" <product ID> 1103 <purchase unit price> 130 "is obtained.

Next, the integration means 4324 has the search result "<product ID> 1103 <product name> Ipoh Coffee <sales quantity> 70 <sales amount> 14000" and the search result "<product ID> 1103 <purchase unit price> 130". Using each attribute value, the integrated data " <Product ID> 1103 <Product name> Ipoh Coffee <Sales quantity> 70 <Sales amount> 14000 <Purchase amount> 9100 <Sales profit> 4900 "is obtained.

For <purchase amount> 9100, refer to the user attribute value source information of “ID = 7” in FIG. 30 and execute the calculation formula of “sales view.sales quantity × purchase view.purchase unit price”. The acquired attribute value.

Further, <Sales profit> 4900 refers to the user attribute value source information of "ID = 8" in FIG. 30, and sets "Sales view. Sales amount x Product sales profit table. Purchase amount" to the program "sub ()". It is an attribute value obtained by assigning to and executing.

Then, the result output unit 441 transmits the acquired integrated data to the terminal device 3.

Next, the terminal device 3 receives and outputs the integrated data. The integrated data is "<product ID> 1103 <product name> Ipoh Coffee <sales quantity> 70 <sales amount> 14000 <purchase amount> 9100 <sales profit> 4900".

As described above, according to the present embodiment, information is appropriately searched from two or more data sources based on the three-layer definition information of the source layer definition information, the conversion rule definition information, and the user layer definition information, and the search results are integrated. can.

Further, according to the present embodiment, information retrieval can be performed at high speed by using an index including an array index.

The software that realizes the search device 4 in this embodiment is the following program. That is, this program is information that defines each of two or more data sources including one or more records having one or more attribute values, a source identifier that is a data source identifier, and a source that is a data source attribute identifier. A source layer definition information that is information having one or more source attribute definition information including an attribute identifier, and a table that is a search target based on search conditions and includes one or more records having one or more attribute values. User layer definition information that is information that defines a certain user table and has one or more user attribute definition information including a user table identifier that identifies the user table and a user attribute identifier that is an attribute identifier of the user table. And, based on the search condition, a search command to be issued to each of the two or more data sources is generated, search results corresponding to the search command are acquired, and the search results of the two or more are used to describe the above. A condition reception unit that accepts search conditions for the user table of a computer that can access a data dictionary having conversion rule definition information that is information for creating integrated data corresponding to search conditions and two or more data sources. With reference to the data dictionary, two or more data sources corresponding to the search conditions are determined, and a search command is generated for each of the two or more data sources using the conversion rule definition information. The search results based on the search command are acquired, and the search results corresponding to the two or more data sources are integrated by using the conversion rule definition information and the user layer definition information to correspond to the search conditions. It is a program for functioning as a search unit for acquiring integrated data and a result output unit for outputting the integrated data acquired by the search unit.

Further, FIG. 32 shows the appearance of a computer that executes the program described in the present specification to realize the search device 4 and the like in the various embodiments described above. The above-described embodiment can be realized by computer hardware and a computer program executed on the computer hardware. 32 is an overview view of the computer system 300, and FIG. 33 is a block diagram of the system 300.

In FIG. 32, the computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

In FIG. 33, in addition to the CD-ROM drive 3012, the computer 301 includes an MPU 3013, a bus 3014 connected to the CD-ROM drive 3012, the ROM 3015 for storing a program such as a boot-up program, and the MPU 3013. It includes a RAM 3016 that is connected and for temporarily storing instructions of an application program and providing a temporary storage space, and a hard disk 3017 for storing an application program, a system program, and data. Although not shown here, the computer 301 may further include a network card that provides a connection to the LAN.

The program for causing the computer system 300 to execute the functions of the search device 4 and the like according to the above-described embodiment may be stored in the CD-ROM 3101, inserted into the CD-ROM drive 3012, and further transferred to the hard disk 3017. Alternatively, the program may be transmitted to the computer 301 via a network (not shown) and stored in the hard disk 3017. The program is loaded into RAM 3016 at run time. The program may be loaded directly from the CD-ROM3101 or the network.

The program does not necessarily have to include an operating system (OS), a third-party program, or the like that causes the computer 301 to execute the functions of the search device 4 or the like according to the above-described embodiment. The program only needs to include a part of instructions that call the appropriate function (module) in a controlled manner and obtain the desired result. It is well known how the computer system 300 works, and detailed description thereof will be omitted.

In the above program, in the step of transmitting information and the step of receiving information, the processing performed by the hardware, for example, the processing performed by the modem or the interface card in the transmission step (only performed by the hardware). Processing) is not included.

Further, the number of computers that execute the above program may be singular or plural. That is, centralized processing may be performed, or distributed processing may be performed.

Further, it goes without saying that in each of the above embodiments, the two or more communication means existing in one device may be physically realized by one medium.

Further, in each of the above embodiments, each process may be realized by centralized processing by a single device, or may be realized by distributed processing by a plurality of devices.

It goes without saying that the present invention is not limited to the above embodiments, and various modifications can be made, and these are also included in the scope of the present invention.

As described above, the search device according to the present invention has the effect of appropriately searching for information from two or more data sources and integrating the search results, and is useful as a search device or the like.

1, 4 Search device 2 Data source management device 3 Terminal device 11, 41 Storage unit 12 Reception unit 13, 43 Processing unit 14, 44 Output unit 31 Terminal storage unit 32 Terminal reception unit 33 Terminal processing unit 34 Terminal transmission unit 35 Terminal reception Section 36 Terminal output section 111 Data source storage section 112 Index storage section 121 Condition reception section 131 Index generation section 132, 432 Search section 133 Index update section 141, 441 Result output section 411 Dictionary storage section 1121 Array index storage section 1122 Array label Index storage 1123 Record index storage 1125 Source index storage 1301 Data source 1311 Array index generation 1312 Array label index generation 1313 Record index generation 1315 Source index generation 4321 Source determination means 4322 Instruction generation means 4323 Source search means 4324 Integration means

Claims (12)

Information that defines each of two or more data sources including one or more records having one or more attribute values, and one or more including a source identifier that is a data source identifier and a source attribute identifier that is a data source attribute identifier. Source layer definition information, which is information that has source attribute definition information of
Information that defines a user table that is a table to be searched based on search conditions and includes one or more records having one or more attribute values. A user table identifier that identifies the user table and a user table. User layer definition information, which is information having one or more user attribute definition information including a user attribute identifier, which is an attribute identifier of
Based on the search conditions, a search command to be issued to each of the two or more data sources is generated, search results corresponding to the search commands are acquired, and the search conditions are used using the two or more search results. It is a search device that searches for information by referring to a data dictionary having conversion rule definition information, which is information for creating integrated data corresponding to.
A condition reception unit that accepts search conditions for the user table,
With reference to the data dictionary, two or more data sources corresponding to the search conditions are determined, and using the conversion rule definition information, a search command is generated for each of the two or more data sources, and the search is performed. The search result based on the instruction is acquired, the search result corresponding to each of the two or more data sources is integrated by using the conversion rule definition information and the user layer definition information, and the integrated data corresponding to the search condition is integrated. With the search unit to get
A search device including a result output unit that outputs the integrated data acquired by the search unit. The conversion rule definition information is
It has one or more transform view information that defines a transform view configured using one or more data sources out of the two or more data sources.
The conversion view information is
Information that defines a transformed view that can include one or more records with one or more view attribute values, a view attribute identifier corresponding to the view attribute value, and view attribute value source information that specifies how to obtain the view attribute value. Has one or more view attribute definition information with
The user attribute definition information is
It has user attribute value source information that specifies a method for acquiring a user attribute value using one or more view attribute values of the one or more converted views.
The search unit
One or more user attribute identifiers included in the search condition are acquired, user attribute value source information corresponding to each one or more user attribute identifiers is acquired, and one or more view attributes corresponding to the user attribute value source information are acquired. A source determination means for acquiring an identifier and acquiring a source identifier corresponding to each of the one or more view attribute identifiers from the view attribute definition information.
An instruction generation means that generates a search instruction for each data source identified by two or more source identifiers acquired by the source determination means using the search condition and the view attribute value source information.
For each of the two or more data sources, a source search means for acquiring search results based on the search command, and
Claim 1 is provided with an integrated means for acquiring integrated data by integrating the search results for each of the two or more data sources acquired by the source search means by using the search conditions and the user layer definition information. The search device described. The view attribute value source information of any one of the above-mentioned one or more view attribute value source information is
The parameter is one or more attribute identifiers of the source attribute identifier of any one or more data sources or the view attribute identifier of one or more transformation views, and the attribute value corresponding to the one or more attribute identifiers. Has an arithmetic expression or program identifier,
The search unit
When acquiring the view attribute value corresponding to the view attribute value source information, the attribute value corresponding to each one or more attribute identifiers of the view attribute value source information is acquired from the data source or the conversion view, and the acquisition is performed. The search device according to claim 2, wherein one or more attribute values are given to the calculation formula or a program identified by the program identifier, the calculation formula or the program is executed, and the view attribute value is acquired. The conversion rule definition information is
It has two or more conversion view information, and has a combination method identifier that specifies a method for combining two or more search results acquired based on the two or more conversion view information.
The integrated means
The search device according to claim 2 or 3, wherein the two or more search results are combined and integrated data is acquired according to the combination method specified by the combination method identifier. The conversion rule definition information is
It has a join method identifier of one of two or more join method identifiers out of three or more join method identifiers of "UNION", "CHOICE", and "LOOKUP".
The "UNION" is grouped by key items for the two or more search results, and by aggregating two or more attribute values of non-key items, the two or more are merged to form one record. Information that indicates that the search results will be combined.
The "CHOICE" selects the attribute values of the key items included in one or more search results from the two or more search results according to the priority order, and aggregates the two or more attribute values of the non-key items. , Information indicating that the two or more search results are combined by the selection process constituting one record.
The "LOOKUP" is an attribute value of a key item of a search result of one of the two or more search results according to a reference condition, and an attribute of a key item included in another search result different from the one search result. The attribute values of key items that are values and are not included in the search result of one are added, and two or more attribute values of non-key items are aggregated to form one record. The search device according to claim 4, which is information indicating that the search results are combined. The user attribute value source information of any one of the above-mentioned one or more user attribute value source information is
The parameter is one or more attribute identifiers of the view attribute identifier of any one or more transformation views or the source attribute identifier of any two or more data sources, and the attribute value corresponding to the one or more attribute identifiers. Has an arithmetic expression or program identifier,
The search unit
When acquiring the user attribute value corresponding to the user attribute value source information, the attribute value corresponding to each one or more attribute identifiers of the user attribute value source information is acquired from the conversion view or the data source, and the acquisition is performed. Any one of claims 2 to 5 in which one or more attribute values are given to the arithmetic expression or the program identified by the program identifier, the arithmetic expression or the program is executed, and the user attribute value is acquired. The search device described in the section. The source layer definition information is
It has instruction source information for generating a search instruction for a data source,
At least two or more different types of instruction source information exist in the instruction source information corresponding to each of the two or more data sources.
The search unit
According to the instruction source information for each of the two or more data sources, a search instruction for acquiring information from each of the two or more data sources is generated, search results based on the search instruction are acquired, and the two or more searches are performed. The search device according to any one of claims 1 to 6, wherein the results are integrated and the integrated data is acquired. The two or more different types of instruction source information include information for generating a search instruction for an SQL statement and information for generating a search module.
The search unit
For the data source corresponding to the SQL statement according to the instruction source information for each of the two or more data sources, a search instruction which is an SQL statement according to the instruction source information is generated, and the data source corresponding to the search module is used. On the other hand, a search command which is an interface of the search module according to the command source information is generated, search results based on the search command are acquired for each of the two or more data sources, and the search results of the two or more are obtained. 7. The search device according to claim 7, wherein the integrated data is acquired. The source layer definition information is
It has connection information for accessing each of the above two or more data sources, and has connection information.
The search unit
Using the connection information, access the data source corresponding to the connection information, acquire the search result based on the search command from the data source, integrate the two or more search results, and acquire the integrated data. The search device according to any one of claims 1 to 8. Attribute for at least one data source among the two or more data sources, for each one or more records of the two or more records that the data source has, and for each one or more attributes of each record. Contains an array index with attribute position information that identifies where the value resides.
The search unit
The attribute position information corresponding to the attribute identifier of the search condition is acquired from the array index, and the attribute value corresponding to the attribute identifier of the search condition is acquired from the data source using the attribute position information. The search device according to any one of claims 1 to 9, which constitutes integrated data having the attribute value. Information that defines each of two or more data sources including one or more records having one or more attribute values, and one or more including a source identifier that is an identifier of a data source and a source attribute identifier that is an attribute identifier of a data source. Defines a user table that is a table to be searched based on search conditions and includes one or more records having one or more attribute values and source layer definition information that is information having source attribute definition information of. The user layer definition information that is information and has one or more user attribute definition information including a user table identifier that identifies the user table and a user attribute identifier that is an attribute identifier of the user table, and the search condition. Based on this, a search command to be issued for each of the two or more data sources is generated, a search result corresponding to the search command is acquired, and the search result corresponding to the search condition is used for integration corresponding to the search condition. It is a search method realized by a data dictionary having conversion rule definition information which is information for creating data, a condition reception unit, a search unit, and a result output unit.
A condition reception step in which the condition reception unit accepts search conditions for the user table, and
The search unit refers to the data dictionary to determine two or more data sources corresponding to the search conditions, and uses the conversion rule definition information to issue a search command for each of the two or more data sources. Generate, acquire the search result based on the search command, integrate the search results corresponding to each of the two or more data sources by using the conversion rule definition information and the user layer definition information, and the search condition. Search steps to get the corresponding integrated data and
A search method in which the result output unit includes a result output step for outputting the integrated data acquired in the search step. Information that defines each of two or more data sources including one or more records having one or more attribute values, and one or more including a source identifier that is an identifier of a data source and a source attribute identifier that is an attribute identifier of a data source. Defines a user table that is a table to be searched based on search conditions and includes one or more records having one or more attribute values and source layer definition information that is information having source attribute definition information of. The user layer definition information that is information and has one or more user attribute definition information including a user table identifier that identifies the user table and a user attribute identifier that is an attribute identifier of the user table, and the search condition. Based on this, a search command to be issued for each of the two or more data sources is generated, a search result corresponding to the search command is acquired, and the search result corresponding to the search condition is used for integration corresponding to the search condition. A computer that has access to a data dictionary with conversion rule definition information, which is information for creating data, and two or more data sources.
A condition reception unit that accepts search conditions for the user table,
With reference to the data dictionary, two or more data sources corresponding to the search conditions are determined, and using the conversion rule definition information, a search command is generated for each of the two or more data sources, and the search is performed. The search result based on the instruction is acquired, the search result corresponding to each of the two or more data sources is integrated by using the conversion rule definition information and the user layer definition information, and the integrated data corresponding to the search condition is integrated. With the search unit to get
A program for functioning as a result output unit that outputs the integrated data acquired by the search unit.

Images