From d2b150144d31a3ed9874354641d0d608c93a0943 Mon Sep 17 00:00:00 2001
From: Markus Makela <markus.makela@mariadb.com>
Date: Wed, 22 Jul 2015 17:34:19 +0300
Subject: [PATCH] Added example to Hint-Syntax.md

---
 Reference/Hint-Syntax.md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/Reference/Hint-Syntax.md b/Reference/Hint-Syntax.md
index b84bb85fd..a037365e0 100644
--- a/Reference/Hint-Syntax.md
+++ b/Reference/Hint-Syntax.md
@@ -95,3 +95,32 @@ You can also push anonymous hints onto the stack which are only used as long as
 ```
 -- maxscale begin <hint content>
 ```
+
+## Examples
+
+### Example 1 - Routing SELECT queries to master
+
+In this example, MaxScale is configured with the readwritesplit router and the hint filter.
+
+```
+[ReadWriteService]
+type=service
+router=readwritesplit
+servers=server1,server2
+user=maxuser
+passwd=maxpwd
+filters=Hint
+
+[Hint]
+type=filter
+module=hintfilter
+```
+
+Behind MaxScale is a master server and a slave server. If there is replication lag between the master and the slave, read queries sent to the slave might return old data. To guarantee up-to-date data, we can add a routing hint to the query.
+
+```
+INSERT INTO table1 VALUES ("John","Doe",1);
+SELECT * from table1; -- maxscale route to master
+```
+
+The first INSERT query will be routed to the master. The following SELECT query would normally be routed to the slave but with the added routing hint it will be routed to the master. This way we can do an INSERT and a SELECT right after it and still get up-to-date data.