[Groonga-commit] groonga/fluent-plugin-groonga at cc91d44 [master] Use `@type` instead of type in README

Back to archive index

Hiroshi Hatake null+****@clear*****
Thu Jan 28 11:40:56 JST 2016


Hiroshi Hatake	2016-01-28 11:40:56 +0900 (Thu, 28 Jan 2016)

  New Revision: cc91d440e9a32de5ee07cd6ebc9cfc1de45ffcec
  https://github.com/groonga/fluent-plugin-groonga/commit/cc91d440e9a32de5ee07cd6ebc9cfc1de45ffcec

  Merged 6870779: Merge pull request #5 from cosmo0920/use-at-type-in-README

  Message:
    Use `@type` instead of type in README

  Modified files:
    README.md

  Modified: README.md (+5 -5)
===================================================================
--- README.md    2016-01-24 22:47:18 +0900 (e185039)
+++ README.md    2016-01-28 11:40:56 +0900 (16a2ba3)
@@ -32,7 +32,7 @@ The following configuration stores all data in `/var/log/messages`
 into Groonga:
 
     <source>
-      type tail
+      @type tail
       format syslog
       path /var/log/syslog.1
       pos_file /tmp/messages.pos
@@ -41,7 +41,7 @@ into Groonga:
     </source>
 
     <match log.**>
-      type groonga
+      @type groonga
       store_table logs
 
       protocol http
@@ -93,7 +93,7 @@ There is one required parameter:
 Here is a minimum configuration:
 
     <match log.**>
-      type groonga
+      @type groonga
       store_table logs
     </match>
 
@@ -114,7 +114,7 @@ There are optional parameters:
 Here is a configuration that specifies optional parameters explicitly:
 
     <match log.**>
-      type groonga
+      @type groonga
       store_table logs
 
       protocol http
@@ -132,7 +132,7 @@ Note that there is special tag name. You can't use
 use the following configuration:
 
     <match groonga.command.*>
-      type groonga
+      @type groonga
       # ...
     </match>
 
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Back to archive index