hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Avrorouter-Tutorial.md

Browse Source 
Fixed field names.
This commit is contained in:
Markus Mäkelä
2017-05-15 08:42:05 +03:00
parent 7ee96c411b
commit a7b919e8e7
1 changed files with 15 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
Documentation/Tutorials/Avrorouter-Tutorial.md
View File

@ -29,7 +29,8 @@ binlog_format=row
binlog_row_image=full binlog_row_image=full
``` ```
_You can find out more about replication formats from the [MariaDB Knowledge Base](https://mariadb.com/kb/en/mariadb/binary-log-formats/)_ _You can find out more about replication formats from the
[MariaDB Knowledge Base](https://mariadb.com/kb/en/mariadb/binary-log-formats/)_
## Configuring MaxScale ## Configuring MaxScale
@ -77,7 +78,8 @@ You can see that the `source` parameter in the _avro-service_ points to the
_replication-service_ we defined before. This service will be the data source _replication-service_ we defined before. This service will be the data source
for the avrorouter. The _filestem_ is the prefix in the binlog files and the for the avrorouter. The _filestem_ is the prefix in the binlog files and the
additional _avrodir_ router_option is where the converted Avro files are stored. additional _avrodir_ router_option is where the converted Avro files are stored.
For more information on the avrorouter options, read the [Avrorouter Documentation](../Routers/Avrorouter.md). For more information on the avrorouter options, read the
[Avrorouter Documentation](../Routers/Avrorouter.md).
After the services were defined, we added the listeners for the After the services were defined, we added the listeners for the
_replication-service_ and the _avro-service_. The _CDC_ protocol is a new _replication-service_ and the _avro-service_. The _CDC_ protocol is a new
@ -103,29 +105,29 @@ the following format:
``` ```
{ {
"Namespace": "MaxScaleChangeDataSchema.avro", "namespace": "MaxScaleChangeDataSchema.avro",
"Type": "record", "type": "record",
"Name": "ChangeRecord", "name": "ChangeRecord",
"Fields": "fields":
[ [
{ {
"Name": "name", "name": "name",
"Type": "string" "type": "string"
}, },
{ {
"Name":"address", "name":"address",
"Type":"string" "type":"string"
}, },
{ {
"Name":"age", "name":"age",
"Type":"int" "type":"int"
} }
] ]
} }
``` ```
The avrorouter uses the schema file to identify the columns, their names and The avrorouter uses the schema file to identify the columns, their names and
what type they are. The Name fields contains the name of the column and the Type what type they are. The _name_ field contains the name of the column and the _type_
contains the Avro type. Read the [Avro specification](https://avro.apache.org/docs/1.8.1/spec.html) contains the Avro type. Read the [Avro specification](https://avro.apache.org/docs/1.8.1/spec.html)
for details on the layout of the schema files. for details on the layout of the schema files.