Skip to content

Commit f3d28b0

Browse files
committed
formatting
1 parent aeb0f83 commit f3d28b0

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

examples/gemfire/demo/README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -366,15 +366,17 @@ demo$
366366
</p>
367367
</details>
368368

369-
### More Complex Data Types
369+
-------------------------------
370+
371+
## More Complex Data Types
370372

371373
This demo also includes an example of using more complex Java types within Gemfire. The `extlib` folder contains 2 jar files:
372374
1. `gemfire-pojo-1.0.jar`
373375
2. `redis-connect-custom-stage-sample-*.jar`
374376

375377
The first contains the code for a `redis.gemfire.Customer` class, which is a very simple POJO containing a name and age, and the later is a build of [redis-connect-custom-stage](https://github.com/redis-field-engineering/redis-connect-custom-stage-sample) containing some custom staging code to transform whatever arbitrary data type (in this case a `Customer`) into a type redis-connect can serialize to `JSON`.
376378

377-
#### Configure Job
379+
### Configure Job
378380

379381
On [http://localhost:8282/swagger-ui/index.html]() go to:
380382

@@ -388,7 +390,7 @@ Or use `curl` to create the `customer-pojo-job` configuration
388390

389391
`$ curl -v -X POST "http://localhost:8282/connect/api/v1/job/config/customer-pojo-job" -H "accept: */*" -H "Content-Type: multipart/form-data" -F "file=@config/samples/payloads/customer-pojo-job.json;type=application/json"`
390392

391-
#### Start Load Job
393+
### Start Load Job
392394

393395
<details>
394396
<summary>INSERT customer records into gemfire</summary>
@@ -509,7 +511,7 @@ done
509511
**Or Use `curl` to start the initial load for `cdc-job`** <br>
510512
`$ curl -X POST "http://localhost:8282/connect/api/v1/job/transition/start/customer-pojo-job/load" -H "accept: */*"`
511513

512-
#### Query Data in Redis
514+
### Query Data in Redis
513515

514516
Your data is now available in Redis at the keys `{gemfireRegionName}:{gemfireKeyName}`, and be queried in redis using the redis-cli:
515517

0 commit comments

Comments
 (0)