rroonga 7.0.2-x64-mingw32 → 7.1.1-x64-mingw32

data/vendor/local/share/doc/groonga/ja/html/_sources/tutorial/introduction.txt

@@ -1,294 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: tutorial
-
-Basic operations
-================
-
-A Groonga package provides a C library (libgroonga) and a command line tool (groonga). This tutorial explains how to use the command line tool, with which you can create/operate databases, start a server, establish a connection with a server, etc.
-
-Create a database
------------------
-
-The first step to using Groonga is to create a new database. The following shows how to do it.
-
-Form::
-
-  groonga -n DB_PATH
-
-The ``-n`` option specifies to create a new database and DB_PATH specifies the path of the new database. Actually, a database consists of a series of files and DB_PATH specifies the file which will be the entrance to the new database. DB_PATH also specifies the path prefix for other files. Note that database creation fails if DB_PATH points to an existing file (For example, ``db open failed (DB_PATH): syscall error 'DB_PATH' (File exists)``. You can operate an existing database in a way that is in the next chapter).
-
-This command creates a new database and then enters into interactive mode in which Groonga prompts you to enter commands for operating that database. You can terminate this mode with Ctrl-d.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-1.log
-.. .. % groonga -n /tmp/groonga-databases/introduction.db
-
-After this database creation, you can find a series of files in /tmp/groonga-databases.
-
-Operate a database
-------------------
-
-The following shows how to operate an existing database.
-
-Form::
-
-  groonga DB_PATH [COMMAND]
-
-DB_PATH specifies the path of a target database. This command fails if the specified database does not exist.
-
-If COMMAND is specified, Groonga executes COMMAND and returns the result. Otherwise, Groonga starts in interactive mode that reads commands from the standard input and executes them one by one. This tutorial focuses on the interactive mode.
-
-Let's see the status of a Groonga process by using a :doc:`/reference/commands/status` command.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-2.log
-.. .. % groonga /tmp/groonga-databases/introduction.db
-.. status
-
-As shown in the above example, a command returns a JSON array. The first element contains an error code, execution time, etc. The second element is the result of an operation.
-
-.. note::
-
-   You can format a JSON using additional tools. For example, `grnwrap <https://github.com/michisu/grnwrap>`_, `Grnline <https://github.com/yoshihara/grnline>`_, `jq <http://stedolan.github.io/jq/>`_ and so on.
-
-Command format
---------------
-
-Commands for operating a database accept arguments as follows::
-
- Form_1: COMMAND VALUE_1 VALUE_2 ..
-
- Form_2: COMMAND --NAME_1 VALUE_1 --NAME_2 VALUE_2 ..
-
-In the first form, arguments must be passed in order. This kind of arguments are called positional arguments because the position of each argument determines its meaning.
-
-In the second form, you can specify a parameter name with its value. So, the order of arguments is not defined. This kind of arguments are known as named parameters or keyword arguments.
-
-If you want to specify a value which contains white-spaces or special characters, such as quotes and parentheses, please enclose the value with single-quotes or double-quotes.
-
-For details, see also the paragraph of "command" in :doc:`/reference/executables/groonga`.
-
-Basic commands
---------------
-
- :doc:`/reference/commands/status`
-  shows status of a Groonga process.
- :doc:`/reference/commands/table_list`
-  shows a list of tables in a database.
- :doc:`/reference/commands/column_list`
-  shows a list of columns in a table.
- :doc:`/reference/commands/table_create`
-  adds a table to a database.
- :doc:`/reference/commands/column_create`
-  adds a column to a table.
- :doc:`/reference/commands/select`
-  searches records from a table and shows the result.
- :doc:`/reference/commands/load`
-  inserts records to a table.
-
-.. _tutorial-introduction-create-table:
-
-Create a table
---------------
-
-A :doc:`/reference/commands/table_create` command creates a new table.
-
-In most cases, a table has a primary key which must be specified with its data type and index type.
-
-There are various data types such as integers, strings, etc. See also :doc:`/reference/types` for more details. The index type determines the search performance and the availability of prefix searches. The details will be described later.
-
-Let's create a table. The following example creates a table with a primary key. The ``name`` parameter specifies the name of the table. The ``flags`` parameter specifies the index type for the primary key. The ``key_type`` parameter specifies the data type of the primary key.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-3.log
-.. table_create --name Site --flags TABLE_HASH_KEY --key_type ShortText
-
-The second element of the result indicates that the operation succeeded.
-
-View a table
-------------
-
-A :doc:`/reference/commands/select` command can enumerate records in a table.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-4.log
-.. select --table Site
-
-When only a table name is specified with a ``table`` parameter, a :doc:`/reference/commands/select` command returns the first (at most) 10 records in the table. [0] in the result shows the number of records in the table. The next array is a list of columns. ["_id","Uint32"] is a column of UInt32, named _id. ["_key","ShortText"] is a column of ShortText, named _key.
-
-The above two columns, _id and _key, are the necessary columns. The _id column stores IDs those are automatically allocated by Groonga. The _key column is associated with the primary key. You are not allowed to rename these columns.
-
-Create a column
----------------
-
-A :doc:`/reference/commands/column_create` command creates a new column.
-
-Let's add a column. The following example adds a column to the Site table. The ``table`` parameter specifies the target table. The ``name`` parameter specifies the name of the column. The ``type`` parameter specifies the data type of the column.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-5.log
-.. column_create --table Site --name title --type ShortText
-.. select --table Site
-
-Load records
-------------
-
-A :doc:`/reference/commands/load` command loads JSON-formatted records into a table.
-
-The following example loads nine records into the Site table.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-6.log
-.. load --table Site
-.. [
-.. {"_key":"http://example.org/","title":"This is test record 1!"},
-.. {"_key":"http://example.net/","title":"test record 2."},
-.. {"_key":"http://example.com/","title":"test test record three."},
-.. {"_key":"http://example.net/afr","title":"test record four."},
-.. {"_key":"http://example.org/aba","title":"test test test record five."},
-.. {"_key":"http://example.com/rab","title":"test test test test record six."},
-.. {"_key":"http://example.net/atv","title":"test test test record seven."},
-.. {"_key":"http://example.org/gat","title":"test test record eight."},
-.. {"_key":"http://example.com/vdw","title":"test test record nine."},
-.. ]
-
-The second element of the result indicates how many records were successfully loaded. In this case, all the records are successfully loaded.
-
-Let's make sure that these records are correctly stored.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-7.log
-.. select --table Site
-
-Get a record
-------------
-
-A :doc:`/reference/commands/select` command can search records in a table.
-
-If a search condition is specified with a ``query`` parameter, a :doc:`/reference/commands/select` command searches records matching the search condition and returns the matched records.
-
-Let's get a record having a specified record ID. The following example gets the first record in the Site table. More precisely, the ``query`` parameter specifies a record whose _id column stores 1.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-8.log
-.. select --table Site --query _id:1
-
-Next, let's get a record having a specified key. The following example gets the record whose primary key is "http://example.org/". More precisely, the ``query`` parameter specifies a record whose _key column stores "http://example.org/".
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-9.log
-.. select --table Site --query '_key:"http://example.org/"'
-
-Create a lexicon table for full text search
--------------------------------------------
-
-Let's go on to how to make full text search.
-
-Groonga uses an inverted index to provide fast full text search. So, the first step is to create a lexicon table which stores an inverted index, also known as postings lists. The primary key of this table is associated with a vocabulary made up of index terms and each record stores postings lists for one index term.
-
-The following shows a command which creates a lexicon table named Terms. The data type of its primary key is ShortText.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-10.log
-.. table_create --name Terms --flags TABLE_PAT_KEY --key_type ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
-
-The :doc:`/reference/commands/table_create` command takes many parameters but you don't need to understand all of them. Please skip the next paragraph if you are not interested in how it works.
-
-The TABLE_PAT_KEY flag specifies to store index terms in a patricia trie. The ``default_tokenizer`` parameter specifies the method for tokenizing text. This example uses TokenBigram that is generally called N-gram.
-
-The ``normalizer`` parameter specifies to normalize index terms.
-
-Create an index column for full text search
--------------------------------------------
-
-The second step is to create an index column, which allows you to search records from its associated column. That is to say this step specifies which column needs an index.
-
-Let's create an index column. The following example creates an index column for a column in the Site table.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-11.log
-.. column_create --table Terms --name blog_title --flags COLUMN_INDEX|WITH_POSITION --type Site --source title
-
-The ``table`` parameter specifies the index table and the ``name`` parameter specifies the index column. The ``type`` parameter specifies the target table and the ``source`` parameter specifies the target column. The COLUMN_INDEX flag specifies to create an index column and the WITH_POSITION flag specifies to create a full inverted index, which contains the positions of each index term. This combination, COLUMN_INDEX|WITH_POSITION, is recommended for the general purpose.
-
-.. note::
-
-   You can create a lexicon table and index columns before/during/after loading records. If a target column already has records, Groonga creates an inverted index in a static manner. In contrast, if you load records into an already indexed column, Groonga updates the inverted index in a dynamic manner.
-
-Full text search
-----------------
-
-It's time. You can make full text search with a :doc:`/reference/commands/select` command.
-
-A query for full text search is specified with a ``query`` parameter. The following example searches records whose "title" column contains "this". The '@' specifies to make full text search. Note that a lower case query matches upper case and capitalized terms in a record if NormalizerAuto was specified when creating a lexcon table.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-12.log
-.. select --table Site --query title:@this
-
-In this example, the first record matches the query because its title contains "This", that is the capitalized form of the query.
-
-A :doc:`/reference/commands/select` command accepts an optional parameter, named `match_columns`, that specifies the default target columns. This parameter is used if target columns are not specified in a query. [#]_
-
-The combination of "`--match_columns` title" and "`--query` this" brings you the same result that "`--query` title:@this" does.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-13.log
-.. select --table Site --match_columns title --query this
-
-Specify output columns
-----------------------
-
-An ``output_columns`` parameter of a :doc:`/reference/commands/select` command specifies columns to appear in the search result. If you want to specify more than one columns, please separate column names by commas (',').
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-14.log
-.. select --table Site --output_columns _key,title,_score --query title:@test
-
-This example specifies three output columns including the _score column, which stores the relevance score of each record.
-
-Specify output ranges
----------------------
-
-A :doc:`/reference/commands/select` command returns a part of its search result if ``offset`` and/or ``limit`` parameters are specified. These parameters are useful to paginate a search result, a widely-used interface which shows a search result on a page by page basis.
-
-An ``offset`` parameter specifies the starting point and a ``limit`` parameter specifies the maximum number of records to be returned. If you need the first record in a search result, the offset parameter must be 0 or omitted.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-15.log
-.. select --table Site --offset 0 --limit 3
-.. select --table Site --offset 3 --limit 3
-.. select --table Site --offset 7 --limit 3
-
-Sort a search result
---------------------
-
-A :doc:`/reference/commands/select` command sorts its result when used with a ``sortby`` parameter.
-
-A ``sortby`` parameter specifies a column as a sorting creteria. A search result is arranged in ascending order of the column values. If you want to sort a search result in reverse order, please add a leading hyphen ('-') to the column name in a parameter.
-
-The following example shows records in the Site table in reverse order.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-16.log
-.. select --table Site --sortby -_id
-
-The next example uses the _score column as the sorting criteria for ranking the search result. The result is sorted in relevance order.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-17.log
-.. select --table Site --query title:@test --output_columns _id,_score,title --sortby -_score
-
-If you want to specify more than one columns, please separate column names by commas (','). In such a case, a search result is sorted in order of the values in the first column, and then records having the same values in the first column are sorted in order of the second column values.
-
-.. groonga-command
-.. include:: ../example/tutorial/introduction-18.log
-.. select --table Site --query title:@test --output_columns _id,_score,title --sortby -_score,_id
-
-.. rubric:: footnote
-
-.. [#] Currently, a ``match_columns`` parameter is available iff there exists an inverted index for full text search. A ``match_columns`` parameter for a regular column is not supported.

data/vendor/local/share/doc/groonga/ja/html/_sources/tutorial/lexicon.txt

@@ -1,12 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-Additional information about lexicon for full text search
-=========================================================
-
-Groonga uses lexicon for full text search as a table. Thus, Groonga can hold multiple information each lexicon.
-For example, Groonga holds frequency of word, flags for stop word, importance of word and so on.
-
-TODO: Write document.
-

data/vendor/local/share/doc/groonga/ja/html/_sources/tutorial/match_columns.txt

@@ -1,234 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: tutorial-match-columns
-
-match_columns parameter
-=======================
-
-Full-text search against multiple columns
------------------------------------------
-
-Groonga supports full-text search against multiple columns. Let's consider blog site. Usually, blog site has a table which contains title column and content column. How do you search the blog entry which contains specified keywords in title or content?
-
-In such a case, there are two ways to create indexes. One way is creating column index against each column. The other way is creating one column index against multiple columns. Either way, Groonga supports similar full-text search syntax.
-
-Creating column index against each column
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Here is the example which create column index against each column.
-
-First, create ``Blog1`` table, add ``title`` column which stores title string, ``message`` column which stores content of blog entry.
-
-Then create ``IndexBlog1`` table for column indexes, add ``index_title`` column for ``title`` column, ``index_message`` column for ``message`` column.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-1.log
-.. table_create --name Blog1 --flags TABLE_HASH_KEY --key_type ShortText
-.. column_create --table Blog1 --name title --flags COLUMN_SCALAR --type ShortText
-.. column_create --table Blog1 --name message --flags COLUMN_SCALAR --type ShortText
-.. table_create --name IndexBlog1 --flags TABLE_PAT_KEY --key_type ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
-.. column_create --table IndexBlog1 --name index_title --flags COLUMN_INDEX|WITH_POSITION --type Blog1 --source title
-.. column_create --table IndexBlog1 --name index_message --flags COLUMN_INDEX|WITH_POSITION --type Blog1 --source message
-.. load --table Blog1
-.. [
-.. {"_key":"grn1","title":"Groonga test","message":"Groonga message"},
-.. {"_key":"grn2","title":"baseball result","message":"rakutan eggs 4 - 4 Groonga moritars"},
-.. {"_key":"grn3","title":"Groonga message","message":"none"}
-.. ]
-
-``match_columns`` option of ``select`` command accepts multiple columns as search target.
-Specify query string to ``query`` option. Then you can do full-text search title and content of blog entries.
-
-Let's try to search blog entries.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-2.log
-.. select --table Blog1 --match_columns title||message --query groonga
-.. select --table Blog1 --match_columns title||message --query message
-.. select --table Blog1 --match_columns title --query message
-
-Creating one column index against multiple columns
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Groonga also supports one column index against multiple columns.
-
-The difference for previous example is only one column index exists. Thus, There is one common column index against title and message column.
-
-Even though same column index is used, Groonga supports to search against title column only, message column only and title or message column.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-3.log
-.. table_create --name Blog2 --flags TABLE_HASH_KEY --key_type ShortText
-.. column_create --table Blog2 --name title --flags COLUMN_SCALAR --type ShortText
-.. column_create --table Blog2 --name message --flags COLUMN_SCALAR --type ShortText
-.. table_create --name IndexBlog2 --flags TABLE_PAT_KEY --key_type ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
-.. column_create --table IndexBlog2 --name index_blog --flags COLUMN_INDEX|WITH_POSITION|WITH_SECTION --type Blog2 --source title,message
-.. load --table Blog2
-.. [
-.. {"_key":"grn1","title":"Groonga test","message":"Groonga message"},
-.. {"_key":"grn2","title":"baseball result","message":"rakutan eggs 4 - 4 Groonga moritars"},
-.. {"_key":"grn3","title":"Groonga message","message":"none"}
-.. ]
-
-Let's search same query in previous section. You can get same search results.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-4.log
-.. select --table Blog2 --match_columns title||message --query groonga
-.. select --table Blog2 --match_columns title||message --query message
-.. select --table Blog2 --match_columns title --query message
-
-.. note::
-
-   There may be a question that "which is the better solution for indexing."
-   It depends on the case.
-
-   * Indexes for each column - The update performance tends to be better than multiple colum index because there is enough buffer for updating. On the other hand, the efficiency of disk usage is not so good.
-   * Indexes for multiple column - It saves disk usage because it shares common buffer. On the other hand, the update performance is not so good.
-
-
-Full text search with specific index name
------------------------------------------
-
-TODO
-
-.. TODO: match_columnsにインデックス名を指定しての検索についても触れる。
-
-
-.. _nested-index-search:
-
-Nested index search among related table by column index
---------------------------------------------------------
-
-If there are relationships among multiple table with column index,
-you can search multiple table by specifying reference column name.
-
-Here is the concrete example.
-
-There are tables which store blog articles, comments for articles.
-The table which stores articles has columns for article and comment.
-And the comment column refers Comments table.
-The table which stores comments has columns for comment and column index to article table.
-
-if you want to search the articles which contain specified keyword in comment,
-you need to execute fulltext search for table of comment, then search the records which contains fulltext search results.
-
-But, you can search the records by specifying the reference column index at once.
-
-Here is the sample schema.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-nested-index-schema.log
-.. table_create Comments TABLE_HASH_KEY UInt32
-.. column_create Comments content COLUMN_SCALAR ShortText
-.. table_create Articles TABLE_NO_KEY
-.. column_create Articles content COLUMN_SCALAR Text
-.. column_create Articles comment COLUMN_SCALAR Comments
-.. table_create Lexicon TABLE_PAT_KEY ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
-.. column_create Lexicon articles_content COLUMN_INDEX|WITH_POSITION Articles content
-.. column_create Lexicon comments_content COLUMN_INDEX|WITH_POSITION Comments content
-.. column_create Comments article COLUMN_INDEX Articles comment
-
-Here is the sample data.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-nested-index-data.log
-.. load --table Comments
-.. [
-.. {"_key": 1, "content": "I'm using Groonga too!"},
-.. {"_key": 2, "content": "I'm using Groonga and Mroonga!"},
-.. {"_key": 3, "content": "I'm using Mroonga too!"}
-.. ]
-.. load --table Articles
-.. [
-.. {"content": "Groonga is fast!", "comment": 1},
-.. {"content": "Groonga is useful!"},
-.. {"content": "Mroonga is fast!", "comment": 3}
-.. ]
-
-You can write the query that search the records which contains specified keyword as a comment, then fetch the articles which refers to it.
-
-Query for searching the records described above::
-
-  select Articles --match_columns comment.content --query groonga --output_columns "_id, _score, *"
-
-You need to concatenate comment column of Articles table and content column of Comments table with period( ``.`` ) as ``--match_columns`` arguments.
-
-At first, this query execute fulltext search from content of Comments table, then fetch the records of Articles table which refers to already searched records of Comments table.
-(Because of this, if you comment out the query which creates index column ``article`` of Comments table, you can't get intended search results.)
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-nested-index-select.log
-.. select Articles --match_columns comment.content --query groonga --output_columns "_id, _score, *"
-
-Now, you can search articles which contains specific keywords as a comment.
-
-The feature of nested index search is not limited to the relationship between two table only.
-
-Here is the sample schema similar to previous one. The difference is added table which express 'Reply' and relationship is extended to three tables.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-nested-index-schema-with-three-relationship.log
-.. table_create Replies2 TABLE_HASH_KEY UInt32
-.. column_create Replies2 content COLUMN_SCALAR ShortText
-.. table_create Comments2 TABLE_HASH_KEY UInt32
-.. column_create Comments2 content COLUMN_SCALAR ShortText
-.. column_create Comments2 comment COLUMN_SCALAR Replies2
-.. table_create Articles2 TABLE_NO_KEY
-.. column_create Articles2 content COLUMN_SCALAR Text
-.. column_create Articles2 comment COLUMN_SCALAR Comments2
-.. table_create Lexicon2 TABLE_PAT_KEY ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
-.. column_create Lexicon2 articles_content COLUMN_INDEX|WITH_POSITION Articles2 content
-.. column_create Lexicon2 comments_content COLUMN_INDEX|WITH_POSITION Comments2 content
-.. column_create Lexicon2 replies_content COLUMN_INDEX|WITH_POSITION Replies2 content
-.. column_create Comments2 article COLUMN_INDEX Articles2 comment
-.. column_create Replies2 reply_to COLUMN_INDEX Comments2 comment
-
-Here is the sample data.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-nested-index-data-with-three-relationship.log
-.. load --table Replies2
-.. [
-.. {"_key": 1, "content": "I'm using Rroonga too!"},
-.. {"_key": 2, "content": "I'm using Groonga and Mroonga and Rroonga!"},
-.. {"_key": 3, "content": "I'm using Nroonga too!"}
-.. ]
-.. load --table Comments2
-.. [
-.. {"_key": 1, "content": "I'm using Groonga too!", "comment": 1},
-.. {"_key": 2, "content": "I'm using Groonga and Mroonga!", "comment": 2},
-.. {"_key": 3, "content": "I'm using Mroonga too!"}
-.. ]
-.. load --table Articles2
-.. [
-.. {"content": "Groonga is fast!", "comment": 1},
-.. {"content": "Groonga is useful!", "comment": 2},
-.. {"content": "Mroonga is fast!", "comment": 3}
-.. ]
-
-Query for searching the records described above::
-
-  select Articles2 --match_columns comment.content --query mroonga --output_columns "_id, _score, *"
-  select Articles2 --match_columns comment.comment.content --query mroonga --output_columns "_id, _score, *"
-
-The first query searches ``mroonga`` from ``Comments2`` table, the second one searches ``mroonga`` from ``Replies2`` and ``Comments2`` table by using reference column index.
-
-.. groonga-command
-.. include:: ../example/tutorial/match_columns-nested-index-select-with-three-relationship.log
-.. select Articles2 --match_columns comment.content --query mroonga --output_columns "_id, _score, *"
-.. select Articles2 --match_columns comment.comment.content --query mroonga --output_columns "_id, _score, *"
-
-As a result, the first query matches two article because of ``Comments2`` table has two records which contains ``mroonga`` as keyword.
-
-On the other hand, the second one matches one article only because of ``Replies2`` table has only one record which contains ``mroonga`` as keyword, and there is one record which contains same keyword and refers to the record in ``Comments2`` table.
-
-Indexes with Weight
--------------------
-
-TODO
-
-.. TODO: match_columnsの重み指定機能についても触れる。