From null+groonga at clear-code.com Sat Dec 1 18:21:16 2012
From: null+groonga at clear-code.com (susumu.yata)
Date: Sat, 01 Dec 2012 18:21:16 +0900
Subject: [Groonga-commit] groonga/grnxx [master] Remove README.textile
Message-ID: <20121201092140.C8CD2940528@jenkins.clear-code.com>
susumu.yata 2012-12-01 18:21:16 +0900 (Sat, 01 Dec 2012)
New Revision: d1fc0161b3a263a3c9b7ab13f749e97f318978e8
https://github.com/groonga/grnxx/commit/d1fc0161b3a263a3c9b7ab13f749e97f318978e8
Log:
Remove README.textile
Removed files:
README.textile
Deleted: README.textile (+0 -0) 100644
===================================================================
--- README.textile 2012-11-30 22:45:44 +0900 (e69de29)
+++ /dev/null
-------------- next part --------------
HTML????????????????????????????...
URL: http://lists.sourceforge.jp/mailman/archives/groonga-commit/attachments/20121201/a38e9675/attachment.htm
From notifications at travis-ci.org Sun Dec 2 17:48:26 2012
From: notifications at travis-ci.org (Travis-CI)
Date: Sun, 02 Dec 2012 03:48:26 -0500
Subject: [Groonga-commit] [Still Failing] mroonga/mroonga#284 (master -
8f74e0c)
Message-ID: <50bb15eadf6a_2164e4605639e8@5590fc60-c5e0-4947-8a96-f4c7194efd69.mail>
Build Update for mroonga/mroonga
-------------------------------------
Build: #284
Status: Still Failing
Duration: 7 minutes and 4 seconds
Commit: 8f74e0c (master)
Author: Kouhei Sutou
Message: Show more details on duplicated key
View the changeset: https://github.com/mroonga/mroonga/compare/c28db210de4e...8f74e0ceaa39
View the full build log and details: https://travis-ci.org/mroonga/mroonga/builds/3458653
--
You can configure recipients for build notifications in your .travis.yml file. See http://bit.ly/lCybCJ
The delivery of this notification was kindly sponsored by Postmark. Send transactional email confidently using http://postmarkapp.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sourceforge.jp/mailman/archives/groonga-commit/attachments/20121202/4a615fd2/attachment.htm
From null+groonga at clear-code.com Mon Dec 3 11:16:43 2012
From: null+groonga at clear-code.com (Daijiro MORI)
Date: Mon, 03 Dec 2012 11:16:43 +0900
Subject: [Groonga-commit] groonga/groonga.github.com [master] Add
groonga-night-3 info
Message-ID: <20121203021755.EE57F940C68@jenkins.clear-code.com>
Daijiro MORI 2012-12-03 11:16:43 +0900 (Mon, 03 Dec 2012)
New Revision: 04c30257e9da767e15749fb58a3f1386be4814c5
https://github.com/groonga/groonga.github.com/commit/04c30257e9da767e15749fb58a3f1386be4814c5
Log:
Add groonga-night-3 info
Added files:
ja/publication/presentation/groonga-night-3-newyear-harvest.pdf
Modified files:
ja/publication/index.html
Modified: ja/publication/index.html (+8 -0)
===================================================================
--- ja/publication/index.html 2012-11-30 18:01:57 +0900 (8aaf79d)
+++ ja/publication/index.html 2012-12-03 11:16:43 +0900 (135a9bf)
@@ -2,6 +2,14 @@
layout: ja
title: ??
---
+
+
-------------- next part --------------
HTML????????????????????????????...
URL: http://lists.sourceforge.jp/mailman/archives/groonga-commit/attachments/20121204/7101542b/attachment.htm
From null+groonga at clear-code.com Tue Dec 4 11:13:47 2012
From: null+groonga at clear-code.com (Haruka Yoshihara)
Date: Tue, 04 Dec 2012 11:13:47 +0900
Subject: [Groonga-commit] groonga/groonga.github.com [master] Add the info
of reactions with twitter in groonga-night-3
Message-ID: <20121204021407.8AC81940C82@jenkins.clear-code.com>
Haruka Yoshihara 2012-12-04 11:13:47 +0900 (Tue, 04 Dec 2012)
New Revision: 175663eb123deafc728c64fbeab66b0a5e21ee9c
https://github.com/groonga/groonga.github.com/commit/175663eb123deafc728c64fbeab66b0a5e21ee9c
Log:
Add the info of reactions with twitter in groonga-night-3
Modified files:
ja/publication/index.html
Modified: ja/publication/index.html (+1 -0)
===================================================================
--- ja/publication/index.html 2012-12-04 11:11:59 +0900 (e626305)
+++ ja/publication/index.html 2012-12-04 11:13:47 +0900 (5fb4e0d)
@@ -7,6 +7,7 @@ title: ??
-------------- next part --------------
HTML????????????????????????????...
URL: http://lists.sourceforge.jp/mailman/archives/groonga-commit/attachments/20121204/fc59ad4d/attachment.htm
From null+groonga at clear-code.com Tue Dec 4 11:47:46 2012
From: null+groonga at clear-code.com (Haruka Yoshihara)
Date: Tue, 04 Dec 2012 11:47:46 +0900
Subject: [Groonga-commit] groonga/groonga.github.com [master] Use links of
user's blogs instead of presentaion only
Message-ID: <20121204024758.0F76A94062A@jenkins.clear-code.com>
Haruka Yoshihara 2012-12-04 11:47:46 +0900 (Tue, 04 Dec 2012)
New Revision: 67b0aa8cd8bf270867299acbacb431946050bf92
https://github.com/groonga/groonga.github.com/commit/67b0aa8cd8bf270867299acbacb431946050bf92
Log:
Use links of user's blogs instead of presentaion only
User's blogs includes presentation links and more infomation by them.
Modified files:
ja/publication/index.html
Modified: ja/publication/index.html (+2 -2)
===================================================================
--- ja/publication/index.html 2012-12-04 11:13:47 +0900 (5fb4e0d)
+++ ja/publication/index.html 2012-12-04 11:47:46 +0900 (0a48472)
@@ -14,8 +14,8 @@ title: ??
Groonga uses GNU build system. So the following is the simplest build
steps:
-
% wget http://packages.groonga.org/source/groonga/groonga-2.0.9.tar.gz
-% tar xvzf groonga-2.0.9.tar.gz
-% cd groonga-2.0.9
+
% wget http://packages.groonga.org/source/groonga/groonga-2.1.0.tar.gz
+% tar xvzf groonga-2.1.0.tar.gz
+% cd groonga-2.1.0
% ./configure
% make
% sudo make install
@@ -396,7 +396,7 @@ option. If you have 4 cores CPU, it's good for using previous |
-
This release has backward incompatible changes against table_list and
+column_list commands. If you use own program which depends on the output
+results above commands, you need to support null instead of "null" string.
+
This release has supported --normalizer option, but there is side effect for
+this feature. If you open old version of groonga database at least once,
+you can not open its database by old version of groonga.
+
There is also another backward incompatible change agaist plugin API for
+tokenizer. The argument of grn_tokenizer_query_open API has changed.
+This API change affects developer of tokenizer plugin.
Supported the expression as snippet_html arguments.
+This change enables you to use snippet_html("STRING"+"STRING") for example.
+You can specify column name or literal for "STRING". [Reported by Tomoatsu Shimada]
+
Supported to create own normalizer as a plugin.
+
Moved groonga-query-log-analyzer as
+groonga-query-log RubyGems.
+It enables you to analyze query logs without installing groonga package.
+
Supported --normalizer option for table_create command.
+This change enables you to specify normalizer plugin.
+
Changed "null" string to null value as meaning for "No Object".
+This is backward incompatible change and affects output results of introspection
+related commands such as table_list and column_list.
+
Added a flag which controls behavior about normalizer as the last argument
+of grn_tokenizer_query_open API.
[windows] Added missing O_BINARY flag to open file correctly.
+This change fixes the infinite loop problem about groonga HTTP server.
+[GitHub#47] [Patch by Shimomura Tatsuya]
+
Fixed a bug that --default-match-escalation-threshold doesn't accept
+negative value to disable functionality.
+This fix enable you to disable search escalation.
+see --default-match-escalation-threshold about details.
+
Fixed a bug that _score after "*" is ignored in --output_columns.
Fixed to use network byte order for status code of GQTP header to follow
the normal network protocol convention.
@@ -128,8 +186,8 @@ referenced by select
This change not to contain such a metadata as search results.
Fixed a problem that display of command prompt changes to not intended state
by using batch mode on Mac OS X.
@@ -352,8 +410,8 @@ by using batch mode on Mac OS X.
Fixed a problem that '=R' is treated as 'OR' in --query syntax. [#1393]
The table_create command creates a table that is named Logs
+and is TABLE_NO_KEY type.
+
If your records aren't searched by key, TABLE_NO_KEY type table is
+suitable. Because TABLE_NO_KEY doesn't support key but it is fast
+and small table. Storing logs into groonga database is the case.
+
If your records are search by key or referenced by one or more
+columns, TABLE_NO_KEY type isn't suitable. Lexicon for fulltext
+search is the case.
The table_create command creates the following table:
+
+
The table is named Lexicon.
+
The table is TABLE_PAT_KEY type table.
+
The table's key is ShortText type.
+
The table uses TokenBigram tokenizer to extract tokens from a
+normalized text.
+
The table uses NormalizerAuto normalizer to normalize a text.
+
+
TABLE_PAT_KEY is suitable table type for lexicon table. Lexicon
+table is used for fulltext search.
+
In fulltext search, predictive search may be used for fuzzy
+search. Predictive search is supported by TABLE_PAT_KEY and
+TABLE_DAT_KEY. Lexicon table has many keys because a fulltext
+target text has many tokens.
+
Table that has many keys should consider table size because large
+table requires large memory. Requiring large memory causes disk
+I/O. It blocks fast search. So table size is important for a table
+that has many keys. TABLE_PAT_KEY is less table size than
+TABLE_DAT_KEY.
+
Because of the above reasons, TABLE_PAT_KEY is suitable table type
+for lexicon table.
The table_create command creates a table that is named Tags,
+is TABLE_HASH_KEY type and has ShortText type key.
+
TABLE_HASH_KEY or TABLE_DAT_KEY are suitable table types for
+tag index table.
+
If you need only exact match tag search feature, TABLE_HASH_KEY is
+suitable. It is the common case.
+
If you also need predictive tag search feature (for example, searching
+"groonga" by "gr" keyword.), TABLE_DAT_KEY is suitable.
+TABLE_DAT_KEY is large table size but it is not important because
+the number of tags will not be large.
You can use TABLE_PAT_KEY and TABLE_DAT_KEY table types for
+range index table. Range index table needs range search support but
+TABLE_NO_KEY and TABLE_HASH_KEY don't support it.
table_create Term --flags TABLE_PAT_KEY|KEY_NORMALIZE --key_type ShortText --default_tokenizer TokenBigram
-[true]
+
The table_create command creates a table that is named Ages,
+is TABLE_DAT_KEY type and has UInt32 type key.
+
TABLE_PAT_KEY or TABLE_DAT_KEY are suitable table types for
+range index table.
+
If you don't have many indexed items, TABLE_DAT_KEY is
+suitable. Index for age is the case in the above example. Index for
+age will have only 0-100 items because human doesn't live so long.
+
If you have many indexed items, TABLE_PAT_KEY is suitable. Because
+TABLE_PAT_KEY is smaller than TABLE_DAT_KEY.
You can use value when you specify TABLE_NO_KEY,
+TABLE_HASH_KEY or TABLE_PAT_KEY. Value type must be a fixed
+size type. For example, UInt32 can be used but ShortText
+cannot be used. Use columns instead of value.
geo_distance function calculates the value of distance (approximate value)
@@ -128,7 +128,7 @@ Those samples show how to calculate the value of distance between New York City
Using the explicitly specified coordinates for calculating the distance (Geo table)
Here are a schema definition of Cities table and sample data to show usage.
table_create Cities TABLE_HASH_KEY ShortText
column_create Cities location COLUMN_SCALAR WGS84GeoPoint
@@ -196,7 +196,7 @@ and the value of coordinate to calculate distance.
the coordinate of London.
-
8.9.2.3.2. Using the explicitly specified value of location?
+
8.11.2.3.2. Using the explicitly specified value of location?
Here are a schema definition of Geo table and sample data to show usage.
table_create Geo TABLE_HASH_KEY ShortText
column_create Geo distance COLUMN_SCALAR Int32
@@ -256,31 +256,31 @@ and the coordinate of New York to calculate distance.
snippet_html extracts snippets of target text around search
keywords (KWIC. KeyWordInContext). The snippets are prepared
for embedding HTML. Special characters such as < and > are
@@ -103,7 +103,7 @@ escapsed as <class="keyword">groonga</span>user.<3.
Grn_expr is an object that searches records with specified conditions
and manipulates a database. It's pronounced as gurunexpression.
Conditions for searching records from a database can be represented by
@@ -126,12 +126,12 @@ of groonga. Rroonga can create a grn_expr by Ruby's syntax instead of
parsing string.
Query syntax is a syntax to specify search condition for common Web
search form. It is similar to the syntax of Google's search form. For
example, word1word2 means that groonga searches records that
@@ -104,7 +104,7 @@ options.
combinedexpression or assignmentexpression. Assignmentexpression can assigns a column to a value.
There are special characters in query syntax. To use a special
character as itself, it should be escaped by prepending \. For
example, " is a special character. It is escaped as \".
@@ -174,10 +174,10 @@ example, Alice's(Bob)" or 'Alice\'sbrother(Bob)'.
Fulltextsearchcondition specifies a full text search condition
against the default match columns. Match columns are full text search
@@ -246,7 +246,7 @@ specifies a keyword that contains one or more spaces, you can use
Phrasesearchcondition specifies a phrase search condition
against the default match columns.
@@ -309,7 +309,7 @@ aren't matched.
content column is the default match column.
-
8.8.1.3.3. Full text search condition (with explicit match column)?
+
8.10.1.3.3. Full text search condition (with explicit match column)?
Its syntax is column:@keyword.
It's similar to fulltextsearchcondition but it doesn't require
the default match columns. You need to specify match column for the
@@ -388,7 +388,7 @@ the following features:
content column value.
-
8.8.1.3.4. Phrase search condition (with explicit match column)?
+
8.10.1.3.4. Phrase search condition (with explicit match column)?
Its syntax is column:@"searchkeyword".
It's similar to phrasesearchcondition but it doesn't require the
default match columns. You need to specify match column for the phrase
@@ -449,7 +449,7 @@ advanced match columns but phrase
I and started aren't adjacent.
This section is for advanced users. Because assignment expression is
disabled in --query option of select by
default. You need to specify ALLOW_COLUMN|ALLOW_UPDATE as
@@ -1296,42 +1296,42 @@ doesn't support column:=
Script syntax is a syntax to specify complex search condition. It is
similar to ECMAScript. For example, _key=="book" means that
groonga searches records that _key value is "book". All values
@@ -101,7 +101,7 @@ statement. Function definion is not supported too. But script syntax
addes the original additional operators. They are described after
ECMAScript syntax is described.
Integer literal is sequence of 0 to 9 such as
1234567890. + or - can be prepended as sign such as
+29 and -29. Integer literal must be decimal. Octal notation,
@@ -159,7 +159,7 @@ hex and so on can't be used.
Float literal is sequence of 0 to 9, . and 0 to 9
such as 3.14. + or - can be prepended as sign such as
+3.14 and -3.14. ${RADIX}e${EXPORNENTIAL} and
@@ -167,7 +167,7 @@ such as 3.14. 314e-2 is the same as 3.14.
String literal is "...". You need to escape " in literal by
prepending \\''suchas``\". For example, "Say\"Hello!\"." is
a literal for Say"Hello!". string.
Its syntax is (...). ... is comma separated expression list.
(...) groups one ore more expressions and they can be processed as
an expression. a&&b||c means that a and b are matched
@@ -411,11 +411,11 @@ select Entries --filter 'n_likes < 5 && (content @ "senna&qu
matched.
The operator searches value by inverted index of column.
Normally, full text search is operated but tag search can be operated.
@@ -1541,7 +1541,7 @@ Because tag search is also implemented by inverted index.
The operator does near search with words word1word2.... Near
search searches records that contain the words and the words are
@@ -1758,7 +1758,7 @@ the record that its content is I<
also and Really is 10.
The operator does similar search with document document. Similar
search searches records that have similar content to
@@ -1801,7 +1801,7 @@ search searches records that have similar content to
migratedallXXXsystem! content are matched.